This policy explains what personal data Callagram (“Callagram”, “the app”, “we”) collects, why we collect it, what we do with it, who else sees it, how long we keep it, and the rights you have over it. It is written to meet Articles 12 to 14 of Regulation (EU) 2016/679 (the General Data Protection Regulation, “GDPR”), and it describes the app as it actually behaves rather than as a general category of app.
We have tried to keep it readable. Where a section matters more than the others, it is because the underlying processing is unusual, and we would rather you read it than skip it.
The controller of your personal data, within the meaning of Article 4(7) GDPR, is:
| Controller | Deniz Kalender, trading as Callagram |
|---|---|
| Postal address | 1032 BG Amsterdam, Netherlands |
| Contact | callagram.support@gmail.com |
| Data protection officer | None appointed. The criteria in Article 37(1) GDPR do not apply: Callagram is not a public authority, does not monitor data subjects on a large scale, and does not process special categories of data on a large scale. Privacy enquiries are handled at the email address above. |
If you believe we are processing your data unlawfully you may contact us directly, and you may also complain to a supervisory authority — see section 12.
This policy covers the Callagram mobile application for iOS and Android, the backend services that support it, and this website. It does not cover the third-party applications that Callagram can open on your device — WhatsApp, Telegram, Signal, Instagram, Facebook Messenger, your telephone dialler, your SMS app, and similar. When Callagram hands you over to one of those, that provider's own privacy policy governs what happens next, and we have no visibility into it. Section 8 explains this handover in detail, because it is the single most commonly misunderstood thing about how this app works.
Callagram exists to answer one question between people who already know each other: is now a good time to call? You mark yourself available, the people you have chosen are told in an order you control, and whoever wants to talk opens their own calling app. Understanding that shape makes the rest of this policy easier to follow, because almost everything we store exists to serve it.
Two consequences are worth stating plainly at the outset:
The table below is the complete picture, organised by purpose. Each row states the legal basis under Article 6(1) GDPR on which we rely.
| Data | Why | Legal basis |
|---|---|---|
| Email address and password (stored only as a salted cryptographic hash, never in readable form) | To create and secure your account and let you sign back in | Art. 6(1)(b) — performance of the contract between you and us |
| Apple or Google account identifier, if you sign in with Apple or Google instead of a password | To authenticate you through that provider. If you use Sign in with Apple and choose to hide your email, we receive only Apple's relay address and never your real one | Art. 6(1)(b) |
Display name, unique handle (for example @deniz), optional profile photo, optional short “about” line (maximum 139 characters) | So the people you connect with can recognise you and find you | Art. 6(1)(b) |
| Phone number in international format, where you provide one | Historically used to match accounts. It is optional and may be absent from your account entirely | Art. 6(1)(b) |
| Account creation timestamp and last-seen timestamp | Account administration, abuse investigation, and deciding whether an account is dormant | Art. 6(1)(f) — our legitimate interest in operating a secure and accurate service |
You choose which ways you are willing to be reached — telephone, SMS, WhatsApp, Telegram, Signal, Instagram, Facebook Messenger and similar — and for each you supply the number or handle at which you accept contact. We store each method and its value so it can be offered to the people you are connected with.
These are published to your connections by design: that is the entire point of adding one. A method you have not added is never shown to anyone. Legal basis: Article 6(1)(b), since offering these to your connections is the service you signed up for.
| Data | Why | Legal basis |
|---|---|---|
| Who you are connected to, and the date you became connected | To maintain your contact list and show each connection's card | Art. 6(1)(b) |
| Your list of connections, shown to each of your connections as names and handles only — never tiers, groups, names you saved, or anything else about how you organise people | So your contacts can see who else they know on Callagram and send them a connection request. A connection who has turned on “Keep my handle private” is left off this list for anyone who is not already connected to them, and anyone blocked is never shown. Turning on “Keep my contact list private” hides your whole list from everyone | Art. 6(1)(b) |
| Connection requests you have sent or received, their outcome, and when they were answered | To operate the request flow, and to restore the original “friends since” date if two people reconnect after disconnecting. Please read section 9.2, which explains the retention consequence of this | Art. 6(1)(b) |
| The name you have saved for each person, which may differ from the name they use | So your contact list reads the way you wrote it | Art. 6(1)(b) |
| The priority tier you assign a person (1–10), the groups you place them in, and the names you give those groups | To decide who is notified, and in what order, when you become available | Art. 6(1)(b) |
| A birthday you record for a contact and how many days ahead you want reminding | To remind you, on your own device, at the time you asked | Art. 6(1)(b) |
| Per-connection preferences: whether you have muted their notifications, hidden your availability from them, or blocked them | To respect those choices every time they would otherwise apply | Art. 6(1)(b), and Art. 6(1)(f) for blocks, being our and your legitimate interest in preventing unwanted contact |
| Data | Why | Legal basis |
|---|---|---|
| Each availability session: when it started, when it expires, which groups it was limited to, the optional note you attached, how it ended | To run the session and to show you your own history of what you sent | Art. 6(1)(b) |
| The queue of notifications a session generates: who is due to be told, in which tier, at what minute, and whether it was sent, cancelled or answered | To deliver notifications in the staggered order the feature depends on, and to stop sending once somebody answers | Art. 6(1)(b) |
| Your current status (available / offline) and, while you are available, until when | To show the people permitted to see it whether now is a good time | Art. 6(1)(b) |
| Snoozes you set, and until when | To stop notifying you when you have asked not to be notified | Art. 6(1)(b) |
| Data | Why | Legal basis |
|---|---|---|
| A record that you opened a calling app for a given person, which app it was, and when — not whether a call connected, how long it lasted, or anything said | To order your notification queue fairly so the same people are not always reached first, to end an availability session once somebody has responded to it, and to show “last connected” on a contact card | Art. 6(1)(f) — our legitimate interest in making the queue fair and the app coherent. We have weighed this against your interests and consider it proportionate: the record is minimal, visible to both people in the pair and to nobody else, and deleted when either of you removes the connection |
| Reminders you schedule: the people or group they are for, the note you write, the time, the repeat pattern, your device's timezone, and each invitee's acceptance | To deliver the reminder at the right local moment to the right people | Art. 6(1)(b) |
Reminder notes are free text, and other people read them. A reminder you address to somebody is shown to them. Please do not put anything in a reminder note that you would not want that person — or anyone who picks up their unlocked phone — to read. In particular, avoid health details, political or religious views, trade-union membership, information about someone's sex life or sexual orientation, and similar sensitive categories. Callagram does not ask for special-category data under Article 9 GDPR, does not want it, and has no feature that requires it.
| Data | Why | Legal basis |
|---|---|---|
| Push notification token and platform (iOS or Android) | To deliver push notifications to your device. The token identifies the device installation, not you personally, but we hold it against your account so we know where to send | Art. 6(1)(a) — your consent, given through the operating system permission prompt, which you may withdraw at any time in your device settings |
| Your notification preferences: whether availability notifications are on, the highest tier you accept, whether tiers are enabled at all | To send only what you have asked for | Art. 6(1)(b) |
| Your device timezone | So a reminder set for 18:00 arrives at 18:00 where you are | Art. 6(1)(b) |
When you save a name for a contact, record their birthday, place them in a group called “Family”, or write a reminder note about them, you are giving us personal data about somebody else. This deserves its own section because the law treats it carefully.
For your own private use of the app among people you know, Article 2(2)(c) GDPR — the so-called household exemption — generally means your personal activity is outside the scope of the Regulation. That exemption covers you, not us: we remain the controller for the storage and processing that happens on our systems, and we take that responsibility seriously.
What we ask of you in return is set out in the Terms of Use: only record information about another person that you have a legitimate reason to hold, keep it accurate, and delete it when it stops being relevant. If you use Callagram for professional or commercial outreach rather than personal contact, the household exemption will not apply to you, and you will have your own obligations as a controller in respect of those people.
If you are not a Callagram user and believe a user has stored data about you here, contact us at the address in section 1. We will act on the request, though our ability to identify the record depends on the information you can give us.
Callagram makes no decision producing legal effects concerning you, or similarly significantly affecting you, by automated means within the meaning of Article 22(1) GDPR.
For completeness, because it is automated and it is about people: when you become available, the app decides the order in which your connections are notified. It uses the tier you assigned each person and, within a tier, puts the people you have connected with least recently first, so that the same names are not always reached first. This ordering is configured by you, affects only the sequence of a notification you chose to send, and has no consequence beyond that. It is not profiling in the Article 22 sense, and we mention it here for transparency rather than because it triggers an obligation.
We keep the list of recipients short deliberately. Each of the following acts as a processor under Article 28 GDPR, under a written data processing agreement, and processes your data only on our documented instructions.
| Recipient | What they do | What they see |
|---|---|---|
| Supabase | Authentication, database, file storage for profile photos, and server-side functions. This is where your Callagram data lives | All data described in section 4 |
| Expo | Application builds and push notification delivery. Expo forwards our notifications to Apple and Google | Your push token and the content of notifications we send to you |
| Apple (APNs) and Google (FCM) | Final delivery of push notifications to your device; Sign in with Apple and Google Sign-In where you use them | Your device token and the notification payload. If you signed in with Apple or Google, they know you authenticated to Callagram |
| Google (Firebase Hosting) | Serves this website | Standard web server logs for these pages, including IP address and user agent. No cookies are set |
We may also disclose data where we are legally obliged to — a binding order from a competent authority, for example — on the basis of Article 6(1)(c). We will resist requests that appear overbroad or unlawful, and will tell you unless we are legally prohibited from doing so. If Callagram is ever sold or merged, your data may transfer to the acquirer; you will be told before that happens and in time to delete your account first.
When you tap WhatsApp, Signal, Telegram, Instagram, Messenger, SMS or the dialler in Callagram, your device opens that application with the relevant conversation or number ready. Three things follow, and all three are worth understanding:
| Data | Retention |
|---|---|
| Account, profile, calling methods, connections, groups, preferences | Until you delete the item, or delete your account |
| Availability sessions and their notification queues | Retained as your sent history; deleted with your account |
| Call records (that you opened a calling app for someone) | Deleted when either person removes the connection, and on account deletion |
| One-off reminders | Deleted automatically approximately one hour after they fire |
| Repeating reminders | Kept until you delete them; each occurrence rolls forward rather than accumulating |
| Push tokens | Until the device is unregistered, the token is replaced, or the account is deleted |
| Web server logs for this site | Per Firebase Hosting's retention |
| Backups | Where operational backups exist they are encrypted, held in the same region as the live database, and expire automatically on our hosting provider's standard schedule. A backup is never restored into the live service except in a disaster-recovery event |
We want to be explicit about a single exception, because it is the sort of thing a privacy policy should not bury.
When you remove a connection, Callagram deletes a great deal: your groups for that person, your tier, reminders between the two of you, their place in your group reminders, your snoozes for them, and your shared call history. What remains is the record that a connection request between the two of you was once accepted, and the date it was accepted.
It remains for a specific and limited reason: if you later reconnect with the same person, it restores the original date you first became friends, rather than pretending you met that day. The record consists of two account identifiers, a status, and a timestamp. It contains no message content, no call history and no notes. It is deleted when either party deletes their account.
If you would prefer that record removed while keeping your account, contact us and we will erase it; we rely on Article 6(1)(f) for retaining it, which means you have an unconditional right under Article 21(1) to object, and we will honour that objection.
If you block somebody, removing the connection does not unblock them, and the block survives. Removing a connection is not forgiveness, and a block that silently lapsed would be a safety defect. Unblocking is always available to you and is always a deliberate act.
Your Callagram data is stored in the European Union. Our database, authentication and file storage are hosted by Supabase in the eu-north-1 region — Amazon Web Services' Stockholm region, in Sweden. Everything described in section 4 lives there, and no transfer outside the European Economic Area is involved in storing it.
Two of our processors necessarily operate outside the EEA:
Those transfers are made under Article 46(2)(c) GDPR on the basis of the European Commission's Standard Contractual Clauses, supplemented by the EU–US Data Privacy Framework where the recipient is certified under it. You may request a copy of the relevant transfer mechanism by writing to us.
Our measures under Article 32 GDPR include:
No system is perfectly secure. If a personal data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority within 72 hours of becoming aware of it under Article 33, and will inform you directly without undue delay where Article 34 requires it.
Under the GDPR you have the following rights, exercisable free of charge and, in ordinary cases, answered within one month:
To exercise any of these, email callagram.support@gmail.com. We may ask you to confirm your identity where we cannot otherwise be confident who is asking, which is a protection for you rather than an obstacle.
Right to complain. You may lodge a complaint with a supervisory authority under Article 77, in particular in the EU or EEA member state of your habitual residence, place of work, or the place of the alleged infringement. Callagram is established in the Netherlands, so our lead supervisory authority is the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens. You may complain to them without contacting us first, although we would rather have the chance to put things right.
Callagram is not intended for children. You must be at least 16 years old to create an account. Where the law of your member state sets a lower age for consent to information society services under Article 8(1) GDPR, that lower age applies, subject to a minimum of 13 and, below 16, to the consent or authorisation of the holder of parental responsibility.
We do not knowingly process the data of a child below the applicable age. If you believe a child has created an account, contact us and we will delete it.
We may update this policy as the app changes. The version number and effective date at the top always tell you which version you are reading. Where a change materially affects your rights or introduces a new purpose for processing, we will give you reasonable advance notice in the app or by email before it takes effect, so that you have the opportunity to object or to delete your account.