A specification sheet. Each row names one category of information, the purpose it serves, and the moment it disappears.
When a settings tooltip, a support reply or an in-app notice describes something different from what is written here, the version on this page governs. It covers the mobile app, the web companion, and every message you send our team.
Opening the app is your signal that you accept it. If any part is unacceptable, remove the app and stop using it.
What it contains. Email address, display name, and an optional profile photo. When you sign in through Google, Apple or a similar provider, we receive the public profile fields that service shares — name, avatar, provider identifier.
Why it exists. To sign you in, keep the session alive, and show your name to other users you interact with.
Where it lives. On our encrypted servers, accessible only to engineers with an open ticket touching your account.
When it disappears. Thirty days after you close the account.
What it contains. Text, images, audio and files you upload deliberately. You keep the copyright; we hold a technical licence strictly limited to storing and displaying the content back to you and to whoever you share it with.
Why it exists. So the app can deliver the content you posted to the people you meant to share it with. Nothing else.
When it disappears. The moment you delete it, or when your account closes. Deleting the content ends the storage licence in the same instant.
What it contains. Hardware model, operating system version, app build, language setting, and a diagnostic trace whenever the app crashes. No content from your account travels with that trace.
Why it exists. To reproduce bugs and confirm that a fix works on the devices people actually use.
When it disappears. Ninety days from the moment the trace is recorded, with no archive copy.
What it contains. The message, any attachment, and the reply thread.
Why it exists. To resolve the issue behind the message and train new support staff on real anonymised cases.
When it disappears. Twenty-four months from the last message in the thread.
What it contains. Screen opens, session length, and coarse city-level location derived from your network address — all aggregated before anyone reads them.
Why it exists. To answer one question: where does the interface make people hesitate.
When it disappears. Never, because after aggregation the data can no longer be tied back to you.
Three vendors, each bound by written contract to a single task: a cloud host stores encrypted files, a crash reporter receives diagnostic traces, an analytics service receives aggregated counts.
Beyond those three, information leaves only when a court or regulator acts on a valid legal instrument, when disclosure is necessary to stop active harm to Zalme or its users, or when a successor entity takes over in a merger or asset sale — and in that last case, you are told before the transfer happens.
Each is actioned within thirty days at no cost. Write to the address below and the clock starts the same day.
Children. Zalme is not for anyone under 13, or under the local age of digital consent where that is higher. A registration that fails the age check is discarded before any other field is stored, and no record of the attempt is kept.
Cross-border movement. Data may be processed in the United States and the European Union. Where information crosses a border, Standard Contractual Clauses and equivalent safeguards travel with it.
Revisions. Changes appear in the app the day they take effect. Material changes also arrive by email at least seven days ahead, and the version live in the app is always the one that governs.
Encryption in transit, encryption at rest, least-privilege access, quarterly access reviews, and a written incident response plan. No system is airtight. If a breach exposes your data, we will write to you directly and tell you what was taken, what was not, and what we are doing about it.