Privacy Policy
Last updated: 19 November 2026
This policy explains what the Debato Android app
(com.debato) collects about you, why, where it is kept, and how to get
rid of it. It covers the app and this website.
The short version. Debato stores the account you sign up with, the profile you fill in, and the debates, votes, comments and pictures you post. It uses Google Firebase to do that. It does not sell your data, does not show third-party advertising, and does not track you across other apps or websites. You can have everything deleted by emailing us.
1. Who we are
Debato is an independent Android app developed and operated from Pune, India. For the purposes of data protection law, we are the data controller for the information described here. You can reach us at debato.appsupport@gmail.com.
2. What we collect
Everything below is either given by you or generated by using the app. There is no data broker in the picture and we buy nothing about you.
Account information
- Email address — from the address you register with, or from your Google account if you use Google Sign-In.
- Display name and, with Google Sign-In, your Google profile picture.
- A unique account identifier issued by Firebase Authentication.
- Whether your email has been verified, since taking part requires it.
We never see your password. Password sign-in is handled entirely by Firebase Authentication. Your password is not stored in the app or in our database, and we cannot read it.
Profile information
- Your @username, which is unique and visible to others.
- Your bio and interests, if you add them.
- Your chosen avatar, or a profile photo you upload.
- The date you joined.
All of this except the join date is optional and can be edited or cleared in the app at any time.
Things you post
- Debates you create: the topic, type, options, duration and any picture, together with its moderation status.
- Votes you cast, recorded against your account so the app can show you your own vote, stop you voting twice, and count the result.
- Comments and replies, and the emoji reactions and likes you add.
- Notifications generated for you, such as a debate being approved or someone replying to you.
Technical information
- A push notification token for your device, so notifications can reach it.
- Usage and device analytics collected by Google Analytics for Firebase: which screens are opened and broad device information such as model, Android version, language and country. This is aggregate product analytics, not a profile of you as an individual, and it is not used for advertising.
- When the app checks for an available update, it contacts Firebase Remote Config, which involves an app instance identifier.
What Debato does not collect: no precise or background location, no contacts, no call or SMS data, no microphone or camera access beyond picking a photo you choose yourself, no advertising identifier, no payment details, and no financial or health information.
3. Why we use it
| What | Used for | Basis |
|---|---|---|
| Email, account identifier | Creating and securing your account, signing you in, verifying ownership of the address, replying to support requests | Performing our agreement with you |
| Username, bio, interests, avatar | Showing who wrote a debate or comment, and letting people view your profile | Performing our agreement with you |
| Debates, votes, comments, reactions | Running the debate, counting the result, showing the discussion | Performing our agreement with you |
| Uploaded pictures | Showing the picture on the debate, and moderator review before it goes live | Performing our agreement with you |
| Push token | Sending the notifications you have turned on | Performing our agreement with you; your device permission |
| Analytics | Understanding which features are used so the app can be improved, and finding faults | Our legitimate interest in maintaining the app |
| Moderation records | Reviewing submissions, enforcing the Terms, and handling repeat abuse | Our legitimate interest in keeping the service safe |
4. What other people can see
When you take part in a debate, other signed-in users can see:
- your display name, @username and avatar or profile photo;
- your bio and interests, if you added them;
- the debates you created that were approved, and your comments, replies and reactions;
- counts such as how many debates you have created and votes you have cast.
Your email address is never displayed anywhere in the app, and neither is your account identifier or anything to do with authentication. How you voted in a particular debate is not shown next to your name; votes are presented as totals and percentages.
Treat anything you post as public. Other people can read it, screenshot it and repeat it elsewhere, and deleting it here does not remove copies someone else has already made.
5. Pictures you upload
You can attach a picture to a debate, and set a profile photo. Both are optional.
Photos are stripped of their metadata before they leave your phone. Debato re-encodes every picture on your device to fit the app's layout. A side effect is that the original file's EXIF data — including any GPS coordinates recorded by your camera, and the device serial — is discarded in the process. What is uploaded is the picture itself and nothing else.
A picture attached to a debate is reviewed by a moderator before the debate is published, which means a moderator sees it. Pictures are stored in Google Cloud Storage for Firebase and are readable by signed-in users of the app once the debate is live.
6. Push notifications
If you allow notifications, Firebase Cloud Messaging issues a token identifying your installation, and we store it against your account so messages can be routed to you. Notifications cover things like your debate being approved or rejected, replies to your comments, and debates you are following finishing.
You can turn notifications off at any time in your Android system settings for Debato. Doing so stops the messages; the token is removed when you delete your account.
7. Third-party services
We do not sell your data and we do not share it for advertising. Debato is built on Google Firebase, and the following Google services process data on our behalf as our processors:
| Service | What it handles |
|---|---|
| Firebase Authentication | Sign-in, passwords, email verification, password resets |
| Cloud Firestore | Profiles, debates, votes, comments, reactions, notifications |
| Cloud Storage for Firebase | Uploaded debate pictures and profile photos |
| Firebase Cloud Messaging | Push notifications |
| Google Analytics for Firebase | Aggregate usage and device analytics |
| Firebase Remote Config | Checking whether an app update is required |
| Google Sign-In / Play services | Signing in with a Google account |
These are operated by Google LLC under Firebase's privacy and security terms. Google's own handling of your data is described in the Google Privacy Policy.
The app is distributed through Google Play, which collects installation and device information under Google's policy, independently of us.
This website is hosted on GitHub Pages. GitHub records server logs, including IP addresses, when pages are requested — see the GitHub Privacy Statement. The site loads fonts from Google Fonts, which involves a request to Google's servers. The site itself sets no cookies and runs no analytics or tracking.
We may disclose information where the law requires it, to respond to a valid legal request, or to protect the rights and safety of users or the public.
8. Where it is stored
Data is held on Google Cloud infrastructure used by Firebase, which may be in a different country from yours, including the United States. Google provides contractual safeguards for these transfers, including the European Commission's Standard Contractual Clauses where they apply.
9. How long we keep it
- Your account and profile are kept for as long as the account exists.
- Debates, their comments, votes and pictures are not kept indefinitely. Old debates are cleared out periodically as routine housekeeping, which removes the debate along with its comments, its votes and its uploaded images. Keep your own copy of anything that matters to you.
- Notifications are removed once they age out of your list.
- Analytics are retained by Google for the period set in our Firebase configuration, and are not linked to your profile.
- Moderation and enforcement records may be kept after content is removed, where needed to enforce the Terms — for example to stop a banned account being recreated.
10. Deleting your data
Email debato.appsupport@gmail.com from the address on your account, with "Delete my account" in the subject. Sending it from the registered address is how we confirm the request is really yours; if you cannot, tell us your @username and we will verify another way.
We will action the request within 30 days. Deletion removes:
- your account and sign-in credentials;
- your profile, including username, bio, interests and profile photo;
- the debates you created, with their pictures, comments and votes;
- your comments and replies elsewhere, your reactions and your votes;
- your push notification token.
Some things may survive: aggregate vote counts that no longer identify you, content other people have quoted or screenshotted, backups until they expire on their normal cycle, and records we are legally required to keep. Deleting your Debato account does not delete your Google account.
You can also delete individual debates, comments and your profile picture in the app, without closing your account.
11. Your rights
Depending on where you live — including under the EU and UK GDPR and under India's Digital Personal Data Protection Act — you may have the right to:
- ask what personal data we hold about you and get a copy;
- have inaccurate details corrected, most of which you can edit yourself in the app;
- have your data deleted;
- object to or restrict certain processing, including analytics;
- withdraw consent where processing relies on it, such as notifications;
- complain to your local data protection authority.
Email us to exercise any of these. We do not charge for it and we will not treat you differently for asking.
12. Security
Traffic between the app and Firebase is encrypted in transit with TLS, and data is encrypted at rest by Google. Access to the database is governed by server-side security rules rather than being left to the app, so the restrictions hold even if the app is modified. Taking part requires a verified email address, which keeps throwaway accounts out of debates.
No service can promise perfect security. If a breach affects your personal data, we will notify affected users and the relevant authority as the law requires.
13. Children
Debato is not intended for children under 13, and we do not knowingly collect their personal data. Where local law sets a higher age for consenting to data processing, that age applies instead. If you believe a child has created an account, email us and we will remove it.
14. Changes
If this policy changes we update the date at the top of this page, and for changes that materially affect how your data is used we will give notice in the app before they take effect.
15. Contact
Privacy questions, access requests and deletion requests: debato.appsupport@gmail.com.