Privacy Policy — Evolopia
Version 1 · Effective date: 2026-11-01
This document explains what the Evolopia habit app (Android package com.evolopia.app) collects about you, why, who it is shared with, where it is stored, how long it is kept, and what control you have. Every statement here is written against the actual behaviour of the software; where the service has a limitation, the limitation is stated plainly.
1) Data controller and contact
- Controller: Masoud Saeedi (natural person, sole proprietor)
- Identifier: O2784359
- Address: Attaran, Qom, Iran
- Privacy contact: support@evolopia.com
- Support: support@evolopia.com
2) Honest summary — eight things to know before you sign up
- You sign in with your Google account. There is no phone-number sign-in in Evolopia, and we never see your Google password.
- Our server and database are in Germany; the files you upload are stored in Australia. Section 8.
- The app uses Google Firebase for usage analytics, crash reports and notifications. Section 3-3.
- Your profile picture is stored at a public, stable URL. Section 5.
- You can delete your account inside the app. Signing in again within 30 days cancels the deletion; after that the account is erased. Section 13.
- "Delete habit" in the app is actually an archive — that habit's history stays in your account. Section 12.
- There is no automated data-export tool today; export requests are fulfilled manually. Section 12.
- Your data is not sold and is not used for advertising. Section 7.
3) Data we collect
3-1) Data you give us
| Category | Items | Mandatory | Purpose |
|---|---|---|---|
| Account identity | The identifier and email address of the Google account you sign in with, and the name on it if Google provides one | Yes | Creating your account and signing you in |
| Profile | First name, last name, email, gender, birth year, occupation, education level, profile picture | No | Personalisation and the profile-completion reward |
| Time zone | Device time-zone identifier | Yes | Computing the daily deadline and the logging window |
| Habit content | Title, description, schedule, duration, daily logs | Yes for every habit you create | The core function of the service |
| Support | Ticket subject and body, attachments including images, audio, video and documents | Only if you open a ticket | Answering and tracking your issue |
3-2) Data the service generates while running
| Category | Items | Purpose |
|---|---|---|
| Financial | Wallet balance, the coin transaction ledger, coin purchase records including the store's purchase token, discount-code use | An auditable record of every coin movement and dispute resolution |
| Sign-in and sessions | Hashes of session tokens together with a device identifier | Sign-in security, abuse detection, sign-out from all devices |
| Device technical | App version, platform, device identifier, requested language | Version support, mandatory updates, diagnostics |
| Notifications | Device notification token and the text of notifications generated for you | Delivering notifications and showing your notification inbox |
| Integrity signals | Device boot-session identifier, device-uptime delta, client timestamp | Preventing device-clock manipulation used to log fake progress |
| Service technical | Duplicate-request prevention keys; the stored response can contain your profile | Preventing an operation, especially a financial one, from being recorded twice |
3-3) Usage analytics and crash reports (Google Firebase)
The app sends two kinds of technical data to Google's Firebase services:
- Usage analytics (Google Analytics for Firebase): which screens you open, which buttons you tap and whether an action succeeded or failed, together with a pseudonymous account identifier, the app version, the device model and operating system, the language and the country. The app does not collect the device's advertising identifier and contains no advertising SDK.
- Crash reports (Firebase Crashlytics): when the app crashes or hits an error, the technical details of that error — stack trace, device model, operating system and app version.
These events are designed not to contain your email, your name, the titles or descriptions of your habits, or the text of your support tickets.
3-4) IP address
Your IP address is not stored in the Evolopia database; it is used only as a temporary in-memory partition key for request rate limiting. It may be recorded briefly in server technical logs for diagnostics and security; these logs are rotated and purged periodically. Google also receives it when the app talks to Google sign-in and Firebase.
4) The backup feature is not available
The "backup" feature, which sends a message to a person you choose when you miss a commitment, is not available in Evolopia today. No contact details of any other person are collected. If the feature is introduced, this policy will be updated before it is switched on, with the exact data it shares.
5) Your profile picture is at a public URL
The profile picture you upload is stored in cloud object storage (Amazon S3) at a stable, unsigned URL that anyone can read. Anyone who has that URL can view the image, even if they are not an app user. Using "remove picture" in the app genuinely deletes the stored object, but a cached copy may persist for a while.
Support-ticket attachments, unlike profile pictures, are private and are only retrievable through a short-lived signed URL.
6) What we do not collect
- Card numbers or any banking credentials — purchases are processed by Google Play or the Apple App Store, and your payment details never reach our servers
- Your Google password
- Your device's advertising identifier
- Your device contacts, your messages, your browsing history
- Location
- Biometric data such as fingerprint or face
7) Sharing with processors
Your data is not sold and is not made available to anyone for advertising. It is shared only with these processors, only to operate the service:
| Processor | What reaches them | Why |
|---|---|---|
| Hetzner Online — server hosting in Germany | The data held in our database and server logs | Running the service |
| Amazon Web Services — cloud object storage in Sydney, Australia | The files you upload and their original filenames | Storing profile pictures and attachments |
| Google — Google Sign-In | The sign-in token from your Google account, which we verify | Signing you in |
| Google — Firebase Analytics, Crashlytics and Cloud Messaging | The analytics events and crash reports in section 3-3; the device notification token and the notification text | Finding errors, improving the app and delivering notifications |
| Google Play and the Apple App Store | The product identifier, the purchase token, and an account identifier the app gives the store at purchase time | Verifying in-app purchases and tying a purchase to the account that made it |
| Apple — push notification service | The device notification token and the notification text, on iPhone | Delivering notifications |
| Cloudflare | The messages you send to our email addresses, which it forwards to us | Domain name service and email forwarding |
In addition, information is provided where a competent authority lawfully requires it.
8) Where data is stored, and international transfers
- The primary database and the server are in Germany, in the European Union.
- The files you upload are stored in Australia (Amazon Web Services, Sydney region).
- Google and Apple process the data they receive on their own global infrastructure, including in the United States.
Australia does not have an adequacy decision from the European Commission. Transfers of uploaded files from the European Union to Australia rely on the Standard Contractual Clauses in Amazon Web Services' data processing terms. Transfers to Google and Apple rely on their own transfer mechanisms, such as the EU-U.S. Data Privacy Framework and Standard Contractual Clauses.
If you are in Australia: your personal information is held overseas, in Germany, and is processed by Google and Apple in other countries, as described above.
9) Why we may process your data (legal bases)
| Purpose | Legal basis |
|---|---|
| Your account, habits, coins, purchases and support requests | Performance of our contract with you |
| Security, rate limiting, integrity signals and preventing duplicate operations | Our legitimate interest in a secure and fair service |
| Usage analytics and crash reports | Our legitimate interest in finding errors and improving the app; you may object — section 12 |
| Optional profile fields | Your choice to provide them; you can clear them at any time |
| Keeping financial records | Legal obligations, and the establishment or defence of legal claims |
| Notifications | Your consent through the device's notification permission, which you can withdraw in your device settings |
10) Retention
Scheduled automatic deletion applies today to these categories:
| Data | Retention |
|---|---|
| Duplicate-request prevention keys | 24 hours |
| Sent outbound message-queue rows | Seven days |
| Usage analytics at Google | The retention period set in our Firebase project, at most 14 months |
| Crash reports at Google | Up to 90 days |
- Everything else — profile, habits and performance history, the wallet ledger, purchase records, tickets and attachments, notification tokens — is retained while the account exists, and is deleted or anonymised on account deletion under section 13.
- Financial and payment records are kept for one year even after account deletion, for accounting obligations and dispute resolution.
- If a message permanently fails to send, its queue row remains for manual review.
- Database backups may contain a copy of deleted data until their normal rotation.
11) Security
- All traffic between the app and the server is protected with TLS.
- The app's database on your device is encrypted.
- Google sign-in tokens are verified against Google's published keys before an account is opened.
- Session tokens are stored hashed, and if one token is reused the whole session family for that device is revoked.
- Access tokens are short-lived and must be refreshed frequently.
- Every money path acquires a per-user exclusive lock before reading a balance, so two concurrent operations cannot corrupt it.
- Rate limiting is applied to sign-in and other sensitive paths.
- External providers such as payments are fail-closed in production: if they are not configured the operation is rejected, never silently skipped.
- Administrative access is separated from ordinary user access and sensitive roles are restricted.
No system is perfectly secure. If you see any sign of unauthorised access to your account, sign out of all devices immediately and tell us at support@evolopia.com.
12) Your rights and how to exercise them
| Right | How it works today |
|---|---|
| Access your data | The profile screen in the app; a full copy on request, below |
| Correct it | Profile editing in the app |
| Clear optional fields | Edit your profile and leave optional fields empty. Saving a profile is a full replacement, so a field you send empty is cleared |
| Remove your profile picture | "Remove picture" in the app — the stored object is genuinely deleted |
| Erase your data | Account deletion — section 13 |
| Get a copy of your data (access and portability) | No automated tool exists. Email support@evolopia.com and a copy of your account data is compiled manually and sent to the email address of your account, in a common electronic format |
| Object to processing, including usage analytics, or ask us to restrict it | Email support@evolopia.com |
| Withdraw consent to notifications | Remove the device from the notification list in the app, or turn off app notifications in your device settings |
| Set a habit aside | "Delete habit" in the app is actually an archive: it leaves the active list, but its history and performance records stay in the account. Full erasure happens only through account deletion |
We answer every request within one month. A habit that carries an active stake cannot be archived; you must first exit that stake.
13) Account deletion
In the app, open your profile, tap Edit profile, then Delete account, and confirm. Your account is deactivated and every session is signed out at once. If you sign in again with the same Google account within 30 days, the deletion is cancelled and the account is restored; after that window the account is erased or anonymised. The steps, how to request deletion without the app, and the exact table of what is deleted versus retained are on the account deletion page.
14) Children and teenagers
You must be at least 16 to use Evolopia, and 18 or older to buy coins or place a stake. Because entering a birth year is optional, we do not verify your age and rely on your own declaration.
If we learn that an account belongs to a child under 16, we disable the account and delete its data. Parents and guardians may request a review at support@evolopia.com.
15) Security incidents
If an incident affects your personal data, then after containing it and assessing its scope we will inform affected users through the app and by email, describing the nature of the incident, the data involved and the recommended action, and we will notify the competent supervisory authority where the law requires it.
16) Changes to this policy
- Every material change is published with a new version number and effective date, and announced in the app.
- Before a feature that shares data with a new processor is switched on — for example Sign in with Apple, the backup feature or an AI assistant — this policy is updated first.
- The current version is always at https://legal.evolopia.com/en/privacy.html.
- Superseded versions are kept in the archive area of the same address so you can tell which text governed on a given date.
17) Contact and complaints
- Privacy matters: support@evolopia.com
- General support: support@evolopia.com
- Postal address: Attaran, Qom, Iran
Please ask us first. You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the European Union country where you live or work. In Australia, you may contact the Office of the Australian Information Commissioner.