Zcribbler Software Labs Private Limited

Privacy Policy

Effective date: August 3, 2026 · Version 2.0

In short

This summary is for orientation only. The sections below are the policy.

1. Who We Are

Zcribbler Software Labs Private Limited operates the Zcribbler mobile application and the zcribbler.com website (together, the "Service"). We decide why and how your personal data is processed, which makes us the controller of that data.

This policy applies to the Zcribbler app and to zcribbler.com. It does not apply to Google, Apple, or any other service you reach from inside the app, each of which has its own privacy policy.

2. What Zcribbler Does, So This Policy Makes Sense

Zcribbler is a place to keep your content and distribute it to people you choose. The mechanics matter for privacy, so they are stated here once and referred to throughout:

Section 6 sets out exactly who can see what.

3. Data We Collect

3.1 Data you give us

DataWhy we have it
Name and email address, passed to us by Google or Apple when you sign inCreating and identifying your account, and contacting you about it
UsernameYour unique address inside the app; it appears in mentions and in links you share
Date of birthConfirming you meet the minimum age. It is never shown on your profile or anywhere else in the app
Profile photo, short bio, accent colour, and any profile links you addYour profile, as shown to people who can see it
Zcribbles and instants — your words, photos, videos, and voice recordingsThe core of the Service
Your distributions — which zcribble went to which audience, and whenDelivering content to the people you chose, and to no one else
Your circles — their names and who is in themLetting you reuse an audience. Circles are visible only to you
Reactions, replies, and mentionsConversation on content that was distributed to you
Your labels — a filing vocabulary you inventOrganising and finding content. Labels are private to you, including labels you put on someone else's content
Direct messages — text, voice notes, photos, and reactions to themPrivate conversation between two people
Follows, blocks, and follow approvalsBuilding and controlling your side of the follow graph
Reports you file about content or peopleSafety and moderation. See Section 13
Your settings — who may follow you, who may message you, and your notification preferencesApplying the choices you made
A place name, if you choose to tag oneOnly when you tap to add a place. The app asks your device for its location at that moment and turns it into a place name. It is never collected in the background, and never when the app is closed

3.2 Data collected as you use the app

DataWhy we have it
Sign-in records: IP address, device name, operating system, and app versionKeeping you signed in, showing you your logged-in devices, and detecting suspicious sign-ins
Which content you have seen, and whenNot marking the same thing unread twice, and telling the person who sent it that it was seen (see Section 6)
Counts of your own activity — followers, following, how much you have distributedDisplaying your profile and ordering what people see
Push notification token for your deviceDelivering notifications you asked for
A device-integrity check at sign-in, run by Google Play Integrity or Apple App AttestTelling real installations of our app apart from automated abuse. It reports on the app and the device, not on you, and it never blocks a sign-in
On Android only: the referral parameter Google Play preserves when you install from a linkOpening the app at the profile whose link you tapped. It is read once and never again

3.3 Data from Google, Apple, and Firebase

ServiceWhat is involvedPurpose
Sign in with GoogleA signed identity token containing your email and nameAuthentication
Sign in with AppleA signed identity token containing your email and name, plus a one-time authorisation we store encrypted so we can revoke it if you close your accountAuthentication, and honouring Apple's account-deletion requirement
Firebase Cloud Messaging (Google)A push token for each deviceDelivering push notifications
Firebase Crashlytics (Google)Crash reports and the state of the app when it crashedFinding and fixing crashes. No account identifier is ever attached to a crash report.
Google Analytics for FirebaseWhich screens opened, which actions completed or were abandoned, app version, device model, operating system, and countryUnderstanding where the app is confusing or broken. See below

What usage analytics do and do not contain. Analytics tell us that a step was reached or abandoned. They never contain your name, your username, your email, your account identifier, anything you wrote, anything you shared, or who you shared it with. We do not attach your account identifier to analytics events, and there is no way for us to do so by accident.

No advertising identifier, and no device identifier. On iOS the advertising framework is not built into the app at all, so the IDFA cannot be read. On Android the advertising-ID permission is removed from the app and advertising-ID collection is switched off. The remaining device-scoped identifiers offered by the analytics tools — Apple's vendor identifier and Android's Settings ID — are switched off as well. What remains is a random identifier for this installation, which is discarded when you uninstall the app and reset when you close your account.

Usage analytics are collected from every installation, and there is no in-app switch for them. We rely on legitimate interests (Art. 6(1)(f)) rather than consent, because these records identify no one: they carry no account identifier, no advertising identifier and no device identifier, and we cannot connect a single event to a single person even if asked to. Product decisions that are made on a sample of users who opted in are made on the wrong sample, and the failures we most need to see — a sign-up abandoned before an account exists, an upload that never reached us — are invisible to us in every other way.

How to stop it. Removing the app from your device stops collection from that installation immediately and discards its identifier. You may also object under Art. 21 by writing to [email protected]; see Section 12. Crash reports are a separate pipeline and continue either way, so that a crash you hit can still be fixed; they carry no identifier for you.

3.4 Photo and video metadata

Photos and videos usually carry hidden metadata — the date and time of capture, GPS coordinates, and the camera and lens used. Zcribbler handles it in two separate ways, and the difference matters:

  1. The file everyone else receives has it removed. When your device prepares a photo or video for upload, it re-encodes the file, and the re-encoded file carries no capture metadata. Nobody you distribute to receives your GPS coordinates, your capture timestamps, or your camera details.
  2. A structured copy is kept for you. The same information is read once, at upload, and stored against your own copy of the content. It is owner-only: it is never shown to anyone you distribute to, and it is not used to target, profile, or advertise to you. It is deleted with the content.

3.5 Data we do not collect

We never ask your device for: your phone number, your contacts or address book, your SMS messages, your call logs, your browsing history, your health or fitness data, your financial data, your biometrics, or data belonging to other apps.

We do not use: advertising SDKs, advertising identifiers, tracking pixels, cross-app or cross-site tracking, or third-party data brokers.

We do not track your location in the background or while the app is closed. Location is read only in the moment you ask the app to tag a place.

We do not operate an advertising network, and we do not monetise personal data in any form.

4. How We Use Your Data

We do not use your content, your messages, or your social graph to train artificial-intelligence models, and we do not send them to any third-party AI service. No part of the Service analyses your photos, videos, or writing to infer things about you.

6. Who Can See What

Most privacy questions about Zcribbler are really questions about this. The full answer is below.

6.1 Your content

6.2 What other people learn about you

6.3 What stays private to you

6.4 Direct messages

Direct messages are private between the two people in the conversation. We do not read them in the ordinary course of running the Service, and they are not used for analytics, suggestions, or ranking. We access a message only when it is reported to us, or where the law requires it. Direct messages are not end-to-end encrypted — they are encrypted in transit and at rest, but we hold the keys, which is what makes moderation of a reported message and lawful disclosure possible. Please do not treat Zcribbler messages as a secure channel for information that would harm you if disclosed.

You control who may message you in Settings → Privacy & account → Who can message you.

6.5 Nothing is public on the web

There is no public web page for a Zcribbler profile and no public web page for Zcribbler content. Your content cannot be read by a search engine, by a scraper, or by anyone who is not signed in to the app.

7. Who We Share Data With

7.1 We do not sell your data

We do not sell, rent, lease, or trade your personal data. We do not share it with advertisers or data brokers, and we do not run advertising of any kind.

7.2 Service providers

We use a small number of infrastructure providers — for hosting, storage and delivery, push notifications, and crash reporting — and each of them processes data only on our instructions, under a data processing agreement.

7.3 Legal requirements

We may disclose data where we are legally required to, or where it is necessary to:

Where we are permitted to tell you about such a request, we will.

7.4 Business transfers

If we are involved in a merger, acquisition, or sale of assets, your data may transfer to the acquirer. Your personal data will remain subject to the commitments in this policy, or you will be given notice and an opportunity to close your account before any material change takes effect.

8. Where Your Data Is Held

Your account, your content, and everything that describes who may see it are held in India. Some data necessarily leaves India, as set out below.

DataWhere it is held
Your account, profile, content records, distributions, messages, and settingsIndia
Database backupsIndia, replicated to a second Indian region
Photos, videos, and audio filesAsia-Pacific
Deleted media, during its retention periodIndia
Cached media, while it is being delivered to youEdge locations worldwide, close to the person requesting it
Push notification tokens, crash reports, and usage analyticsUnited States and other Google locations

Safeguards

9. How Long We Keep Data

DataHow longWhy
Your account and everything in itFor as long as your account is openProviding the Service
Content and account records, after you close your accountErased within 180 daysSee Section 11
Photos, videos, and audio files, after you delete them or close your accountRemoved from delivery immediately; the retained copy is destroyed within 190 daysRecovering from mistakes and errors, and answering legal requests
Sign-in sessionsExpire on their own after a period of inactivity, and in any case at a fixed maximum age. You can end any session yourselfSecurity
Database backupsUp to 35 daysDisaster recovery
Server logs30 daysDiagnosing faults and abuse
Reports of content or accountsKept while the matter is open and for a reasonable period afterwards for safety record-keepingA report is a record about the reported account; it is not deleted because the reporter left
Child-safety recordsRetained as long as the law requiresLegal obligation, including under the POCSO Act, 2012
Records of account bansRetained for as long as the ban is in forcePreventing a banned account from returning
Crash reports and usage analytics held by FirebaseUp to 14 months, under Google's own retention policyDiagnosing crashes and understanding usage

When a retention period ends, the data is deleted. We do not keep personal data for longer than the purpose it was collected for requires.

10. Security

We will notify you and the relevant supervisory authority of a personal data breach where the law requires it, and within the deadlines the law sets.

No method of transmission or storage is completely secure. We take the measures above seriously, but we cannot guarantee absolute security.

11. Closing Your Account

You can close your account yourself, from Settings → Account → Delete account. You re-authenticate with Google or Apple to confirm, which is what stops someone else from doing it.

Closing your account is immediate and cannot be undone. There is no waiting period during which you can change your mind, and we cannot restore an account once it is closed. Signing in again with the same Google or Apple identity creates a completely new, empty account. It does not bring the old one back.

At the moment you confirm:

What remains, and why. Replies, reactions, and direct messages you sent on other people's content stay where they are, under your name. What you said on someone else's content is part of that content's record and is not yours to withdraw by leaving. Your own content is a different matter, and it goes.

Erasure. Underlying records of a closed account are held in a deactivated state, unreachable by any other user and returned by no part of the Service, and are erased within 180 days of closure. Media files are destroyed within 190 days. Backups age out on their normal rotation, within 35 days. Records we are legally required to keep — child-safety records and records of an account ban — are retained as described in Section 9.

Full step-by-step instructions, including how to request closure if you have lost access to your device, are on the Delete Your Account page.

12. Your Rights

12.1 Under the GDPR (EU, EEA, and UK)

12.2 Under the DPDP Act, 2023 (India)

12.3 How to exercise them

Withdrawing consent. Notifications, camera, microphone, and location can each be withdrawn individually, from your device's system settings, without affecting the rest of the Service. Usage analytics do not run on consent — see the objection right above, and section 3.3. Because using Zcribbler at all depends on accepting these Terms and this policy, the way to withdraw consent entirely is to close your account.

13. Automated Systems, and What They Do Not Do

13.1 Ordering, not deciding

The order of your feed and the people we suggest you might know are chosen automatically. These systems use signals such as who you follow, who you interact with, and how recent something is.

They affect order and suggestion only. They never decide who is allowed to see your content — that is decided by the audience you chose, and by nothing else. They do not restrict your account, do not affect your rights, and produce no legal or similarly significant effect. A small selection of broadcast content is also chosen by people at Zcribbler rather than automatically, and shown separately from your feed.

13.2 Moderation is done by people

No content is hidden and no account is restricted automatically. Every moderation decision is made by a person at Zcribbler who has looked at the report and the content it names. There is no report threshold that removes content on its own.

If we act against your content or your account, you can appeal by email — the address is shown to you in the app at the point you are told. See Terms, Section 8.

14. Children

These measures are designed to meet our obligations under Section 9 of the DPDP Act, 2023, and Article 8 of the GDPR.

15. Changes to This Policy

We may update this policy. When a change is material — a new purpose, a new category of data, a new provider, or a shorter protection for you — we will:

Continuing to use Zcribbler after the effective date means you accept the updated policy. If you do not, you may close your account.

16. Grievance Officer and Data Protection Contact

Appointed under Rule 3(2) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, and Section 13 of the DPDP Act, 2023:

We acknowledge a grievance within 24 hours and resolve it within 15 days of receipt.

If you are not satisfied with our response, you may approach the Data Protection Board of India, or — in the EU, EEA, or UK — your national supervisory authority.

17. Contact Us

Zcribbler Software Labs Private Limited, Kannur, Kerala, India.