Privacy Policy

Who we are

Sleep on Call is operated by Pradeep Kumar, an individual developer based in Uttarakhand, India, who is the data controller for the information described here. You can reach us about anything in this policy at support@sleeponcall.com.

This policy covers the Sleep on Call mobile app and the service behind it. It does not cover what other users do with what you choose to tell them.

What you give us

• When you create an account. You sign in with Google or Apple. From that we receive your name and email address, and we create a username and an internal account ID for you. With Apple you may hide your email, in which case we receive a private relay address instead of your real one.
• Your profile. A display name, an avatar chosen from the illustrations we provide, your gender, age, the languages you speak and your level in each, your interests, an optional bio, optionally what you do (chosen from a short list — for example student, employed or retired), and a profile background chosen from the ones the app provides. If you chose a relationship status in an early version of the app, we still hold that answer; it is not shown to anyone, and it is erased when you delete your account. There is no profile photo, and the app never asks for camera or photo-library permission.
• What you say and send. Your voice during calls and live rooms, and the text you send in chats and room comments. In a 1:1 chat you can also send a GIF: one you choose from your phone (through the system’s photo picker, which shares only the GIF you pick) or from your keyboard. It is stored on our server and only the two people in that chat can open it.
• Your settings. Your timezone, your interface language, and your privacy and call settings — whether your city, country, what you do, online status, total calls, sign-up date and background on calls and rooms are shown, and whether direct calls ring your phone.

What we collect automatically

• Approximate location. We estimate your country and city from your IP address when you connect: our API is served through Cloudflare, which works out an approximate country and city for each connection and passes that estimate to our servers. We do this so your profile is not empty and we can show you people in a sensible region. The app does not ask for a city. You can see both in Profile Settings. Other users see your country unless you hide it, and your city only if you turn on “Show my city” — it starts off. Showing or hiding either is always available, instantly. We do not collect precise location.
• Your timezone, sent each time the app opens.
• Online status, so people can see whether you are around. You can turn this off.
• Crash reports and diagnostic logs. The app and our servers send technical records to Sentry, a service provider, so we can find and fix bugs. A crash report holds the error, the app's state at the time and technical details about your device (model, operating system, app version). Diagnostic logs record which screens you open, when the app moves to the background or foreground, requests that fail or are slow, and errors the app recovers from; our servers also log each request they handle (which feature, the result and how long it took). These records are linked to your account ID when you are signed in, and to a random ID for this installation before you sign in. They are designed to exclude call audio and message text, and email addresses, phone numbers and sign-in tokens are filtered out before anything is sent. Sentry is set not to record your IP address or location, and session recording, screenshots and performance tracing are switched off. Google Play's Data safety section lists this under “Analytics”, which is Google's term for monitoring app health and fixing bugs; we do not use it for advertising or marketing.
• A push notification token, issued by Expo, so notifications can reach your device. Expo delivers the notification through Apple (APNs) or Google (FCM); a message notification carries a short preview of the message text.
• Interaction records. Who called whom and for how long, calls you liked or disliked, people you follow or block, and reports you file — so the service works and we can act on abuse.
• Sign-in and network records. When you sign in, we record your IP address and the app’s technical description of itself (its “user agent”: app version and phone operating system) with that sign-in. We record the same when you sign out and when you ask to delete your account, and your IP address when you change your name, gender, age or native language. We keep these to protect your account and investigate misuse. Separately, our servers’ access logs record the IP address and user agent of each request, and our call relay logs the network addresses it connects. We do not collect your phone’s advertising ID or any hardware identifier such as its serial number or IMEI.

We do not use advertising identifiers, we run no advertising or marketing-analytics SDK, and we do not track you across other apps or websites. The crash reports and diagnostic logs described above are used only to keep the app working. If advertising is ever introduced, this policy will be updated and you will be told before any ads appear.

Your voice

How we use what we collect

• To run the service — create your account, match you with speakers of the languages you are learning, connect calls and rooms, deliver messages and notifications.
• To keep people safe — enforce blocks, review reports, act on abuse.
• To fix things — diagnose crashes, errors, and features that fail or are slow.
• To meet our obligations — respond to lawful requests and enforce our terms.

We do not sell your personal information, and we do not share it for advertising.

What we share, and with whom

• With other users, because that is the product. Your display name, avatar, age, gender, spoken languages, interests, bio and — unless you hide them — your country and online status are visible to other users, and so is your city if you choose to show it. Your email address is never shown to other users. When you speak, the people in the call or room hear you; when you send a message, its recipients see it.
• Service providers processing data for us. Those that can read your data act on our instructions and are contractually bound to use the data only to provide their service to us:
• Hostinger rents us the servers, in India, that we run the service on: the app’s back end, the database, the call relay, and the logs and backups described in this policy. Calls and live rooms are relayed by software we run on those servers, not by a third-party calling service.
• Cloudflare sits in front of our API. Every request the app makes passes through it, so it handles your IP address and the request on its way to us, and it estimates your approximate location as described above. It also receives email sent to support@sleeponcall.com and forwards it to us.
• Resend delivers the emails we send you, such as a welcome email after you sign up. It receives your email address, your name and the message.
• Sentry (crash reports and diagnostic logs) and Expo (push notification delivery).
• OpenAI. Its moderation tool automatically scans text you submit — live-room topics and comments, and parts of your profile such as your name, bio and city — purely to catch profanity and abusive content before it is shown; it is not used for anything else.
• Google Drive stores our offsite backups. They are encrypted on our own server before they are uploaded, with a key Google does not hold, so Google stores them but cannot read them.
• Legal requirements. If we are legally required to disclose information, or need to in order to protect someone's safety or our legal rights. Where we are permitted to, we will tell you.

If we are ever acquired or merge with another company, your information may transfer as part of that — we will tell you before your data becomes subject to a different policy.

How long we keep it

• Account and profile information — while your account exists.
• Voice — not at all. Discarded when the call or room ends.
• Messages — while your account exists. Deleting a conversation removes it from your own view; a message you sent stays in the other person’s copy of the conversation, the way an email you send stays in the recipient’s inbox, even after your account is deleted. A GIF is deleted from our server 7 days after the other person first sees it, or 30 days after it was sent if they never do; the message stays and shows that the GIF has expired. A GIF in a reported message is kept until we have closed the report. If a chat message is reported as a child safety concern, we also keep every GIF in that chat and every GIF the reported person sent, unless we find the report unfounded; if we report it to the National Center for Missing and Exploited Children (NCMEC), we keep them for at least one year after that report, as US law requires.
• Crash reports — up to 90 days, then deleted. Diagnostic logs — up to 30 days in Sentry, and 5 days on our own servers.
• Sign-in and network records — the records kept with your sign-ins, sign-outs, deletion request and identity changes stay while your account exists. When the account is erased, the sign-in records and the identity-change history are deleted, and the rest keep no IP address, user agent or device details. Server access logs and call-relay logs are deleted after 5 days.
• Backups — we copy our database every day so the service can be recovered after a failure. Each copy is deleted after at most two years. A backup cannot be edited, so information from an account deleted after a copy was made stays in that copy until the copy is deleted. Backups are used only to recover the service, access to them is restricted, and the copies kept away from our server are encrypted.
• Push tokens — deleted when you sign out, when the token stops working, or as soon as you ask to delete your account. If your phone is offline when you sign out, the token is deleted when it stops working, and it stops being linked to you as soon as someone else signs in on that phone.

Your choices and rights

Deleting your account. Settings → Profile Settings → Delete Account. Your profile stops being visible to other people straight away, and your bio, city and interests are cleared at once. The account itself is then permanently removed 12 days later. That gap exists so an accidental deletion can be undone: if you sign back in during those 12 days, the deletion is cancelled and your account continues.

After the 12 days it is a real deletion, not a deactivation: your name, avatar, gender, country, languages and the rest of your account information are erased. Two things are kept, deliberately. First, safety records — for example a record that an account was banned, and reports filed about it — with identifying details removed. Second, messages you sent to other people: deleting your account removes your profile and your own copy, but a message you sent stays in the conversation on the other person’s side, as described above. Copies of the account in our backups are deleted with those backups, within two years (see How long we keep it).

What you can change at any time. Your languages and level, your interests, your bio, what you do, your avatar and your background — edit or clear them as often as you like. You can also hide your city, country, what you do or your online status, block anyone, delete individual messages from your own view, and turn calls off so nobody can ring you.

What can only be changed once. Your name, gender, age and native language are your identity here, so they are deliberately hard to change. Filling one in for the first time is free and immediate. After that, each can be changed once, and only once 18 days have passed since it was set — then it is fixed. Your country and city are different: the app never lets you change either yourself, at any time — both are estimated automatically from your connection each time you open the app, so they follow you when you travel, and the app does not ask for a city. The only control you have over both is whether other users see them.

Depending on where you live, you may also have the right to access a copy of your data, correct it, restrict or object to how we use it, or receive it in a portable format. Email support@sleeponcall.com and we will respond within the period the law allows. If you are in the EEA or UK, our legal bases are performing our contract with you, our legitimate interests in running and protecting the service, and your consent where we ask for it.

Security

Everything the app sends travels over encrypted connections — HTTPS for the API, WSS for the live connection, and encrypted media for calls. Access to production data is limited to those who need it to operate the service.

No system is perfectly secure. If a breach ever affects your rights, we will tell you and the relevant authorities as the law requires.

Children

You need to be 18 or over to use Sleep on Call. It puts you in live voice conversations with adults you have not met, so it is built for grown-ups — not because of the content, but because of who you are talking to. We ask for your age when you sign up. We do not knowingly collect information from anyone under 18, and if we learn that we have, we delete the account.

Where your information is processed

Our servers are in India. Cloudflare, Sentry, Resend, Expo, OpenAI and Google are based in the United States and may process your information there or in other countries where they operate; Cloudflare handles traffic in data centres around the world. This means your information may be processed in countries other than your own, including outside the EEA and the UK. Where that happens we rely on appropriate safeguards, such as standard contractual clauses.

Changes to this policy

If we make a material change, we will tell you in the app or by email before it takes effect, and update the date at the top. Continuing to use Sleep on Call after that means you accept the change.

Contact

Questions, requests or complaints: support@sleeponcall.com

If you are in the EEA or UK and are not satisfied with our response, you have the right to complain to your national data protection authority.