Privacy Policy
Effective: 12 October 2026 · Contact: privacy@blipcall.com
Who we are
Blipcall (blipcall.com and the Blipcall iOS app) is run by Siroj Kasemrut, an individual developer based in Thailand (“we”, “us”), who is the controller of the data described here. Contact: privacy@blipcall.com.
The short version
No accounts, no call recording, no ads and no analytics. We keep only what is needed to connect calls and stop abuse, and we delete it on the schedule below.
What we process, why, and for how long
| Data | Why | Legal basis | Kept for |
|---|---|---|---|
| Link details: purpose preset, the label you type (if any), creation and expiry time, call status, pause and quiet-hours settings, and your time-zone offset | To run your link. The offset lets quiet hours follow your local clock. | Providing the service you asked for (GDPR Art. 6(1)(b); PDPA s.24(3)) | Until the link expires or you delete it (at most 30 days), then removed from our server's disk within 24 hours. |
| Push token for your iPhone, and whether it is a production or test (sandbox) token — iOS app only | To ring your iPhone when someone calls one of your links. | Providing the service you asked for (GDPR Art. 6(1)(b); PDPA s.24(3)) | Same as the link. Deleted sooner if Apple reports the token invalid or you stop calls on that iPhone. |
| Report flag on a link | To keep a reported link disabled. | Legitimate interest in keeping the service safe (GDPR Art. 6(1)(f); PDPA s.24(5)) | Until the link would have expired. The push token is deleted at once. |
| Call set-up messages, including the network (IP) addresses of both devices | To connect the call. | Providing the service you asked for (GDPR Art. 6(1)(b); PDPA s.24(3)) | Not stored — passed through in memory only. |
| Anti-abuse counters derived from your IP address, stored as a keyed hash that changes every day | To limit link creation, repeated ringing and relay use. | Legitimate interest in keeping the service safe (GDPR Art. 6(1)(f); PDPA s.24(5)) | Up to 1 hour. |
| Server logs: IP address, time, request type and status. Link ids are masked (a rare server fault may log a full request address) | Security, troubleshooting and abuse investigations. | Legitimate interest in keeping the service safe (GDPR Art. 6(1)(f); PDPA s.24(5)) | Up to 15 days. |
| Emails you send us | To answer you. | Legitimate interest in answering your message (GDPR Art. 6(1)(f); PDPA s.24(5)) | Up to 12 months. |
Call audio
Calls are peer-to-peer WebRTC, encrypted end to end with DTLS-SRTP. When a direct connection is not possible, our relay server forwards encrypted packets it cannot decrypt. We never record, store, transcribe or analyse call audio. The optional voice mask runs on your device. During a call both screens can show a five-emoji security code: if the codes match, nobody is intercepting the call. A match does not tell you who the other person is.
What the other person sees
The label you set, if any. Anyone who has your link — including someone who scans a QR code you put up — can also see its purpose, how long it has left, whether it is paused, whether quiet hours are on right now, and whether a call is in progress. Checked repeatedly, that can show when you tend to be on calls and when your quiet hours start and end. Deleting the link ends that.
During a call, your device’s IP address is sent to the other person’s device so the audio can flow directly between you — that is how internet calls work — and theirs is sent to yours. An IP address can reveal an approximate location and your internet provider. Neither of you sees the other’s phone number.
On your device
On the web, your language choice and your links with their secret owner keys are kept in your browser’s storage; the home page lists your live links from it. A link’s record is removed when its page sees it end or you delete it; otherwise the next time you open Blipcall in that browser once a day has passed since it ended (the wait covers a device clock that runs fast). Clearing this site’s data removes them at once. While a link’s page is taking calls it also keeps the time there, so that the home page in another tab can show the link is ringing; that note is removed when the page stops. The list of recent calls on a link’s page is kept only in that page’s memory and is gone when you close it.
In the iOS app, your links, their settings and your confirmation that you are 18 or older stay on your iPhone. The app keeps a short record of missed and answered calls per link (at most 20) on your iPhone only, and deletes it with the link. Blipcall calls are not added to your iPhone’s Recents, and Live Activities run on your device. We use no cookies or tracking technologies; this storage is strictly necessary for the service.
Nearby Talk
Nearby Talk in the iOS app connects directly to iPhones near you over your local network. It is local only: nothing about it passes through or is stored on our servers.
Who else receives data
OVHcloud (France) hosts our servers as our processor under its data processing agreement. If you use the iOS app, when someone calls one of your links, Apple Push Notification service receives your push token, the link id and the link’s preset — never its label — so iOS can show the call. We do not sell or share personal information, and we use no analytics or advertising SDKs. We respond to Do Not Track by not tracking anyone.
Where data is processed
Our servers are in France (EU). We operate the service from Thailand, and Apple may process push data in the United States. We transfer data only as needed to provide the service you asked for, with the safeguards described here.
Your rights
Depending on where you live (for example under the EU or UK GDPR, Thailand’s PDPA, Brazil’s LGPD, India’s DPDP Act or US state laws), you can ask to access, correct, delete, restrict or object to the use of your data, and to receive a copy. There are no accounts, so we can usually find your data only if you give us the link address, or your IP address and the approximate time. You can delete any of your links yourself at any time with “Delete link”. Email privacy@blipcall.com to make a request. You may also complain to your data protection authority — in the EU your national authority, in the UK the ICO, in Thailand the PDPC, in Brazil the ANPD.
Legal requests
We disclose only what we hold, and only in response to valid legal process. Because links and their data expire, there is usually very little to disclose.
Children
Blipcall is for adults (18+) and is not directed to children. We do not knowingly collect personal data from anyone under 18. If you believe someone under 18 has used Blipcall, email privacy@blipcall.com and we will delete the related links and data.
Security and breaches
Access to our servers is limited to the operator. If a breach is likely to put you at risk, we will notify the relevant authorities, and you where required, within the time the law requires (72 hours under the GDPR and PDPA).
Changes
We will post changes here with a new effective date. If a change matters, we will also show a notice in the app.
Contact
- Support: support@blipcall.com
- Abuse reports: abuse@blipcall.com
- Privacy requests: privacy@blipcall.com
- Legal: legal@blipcall.com