English | Polski | Deutsch | Français | Español | Italiano | Português (Brasil) | Nederlands | Türkçe | 日本語 | 한국어 | Bahasa Indonesia | हिन्दी | العربية
Effective date: 2026-10-15 Version: 1.6
This policy describes what the Cramshot Android application (the "App") does with data, in line with the General Data Protection Regulation (GDPR) and Polish law. Every statement matches the shipped App; if the App changes, this policy changes in the same release.
ASE Spółka Akcyjna, ul. Portowa 41, 78-100 Kołobrzeg, Poland, KRS 0000965347, NIP 6711850032, REGON 521363498 ("we", "us") is the controller of personal data processed through the App.
Contact for all privacy matters: sprzedaz@amazinggirl.pl. We have not appointed a data protection officer because the scale and nature of our processing do not require one.
Sharing a deck is your choice and goes only where you send it. "Share as a file" hands a copy of the deck (title, cards and their source excerpts, never your ratings or schedule) to the app you pick, such as a messenger or Quick Share. "Send to a nearby Cramshot" sends the same copy directly to the other phone over Bluetooth and Wi-Fi (Google Nearby Connections) after that person accepts it; it does not pass through our server and we never see it. Nearby transfer needs the "nearby devices" permission (and, on older Android versions, the location permission Android requires for Bluetooth scanning); the App never reads or stores your location.
Android may include the App's local data in the device backup to your Google Account (Android Backup). That copy is made and encrypted by Google under your Google Account settings; we have no access to it. You can exclude the App from backups in the Android settings.
| Data | Why | How long we keep it |
|---|---|---|
| Recognized text of a scan or of the pages you select in an imported file (up to 30,000 characters), a language hint, requested card count and type | To create flashcards | Only while the request is processed; not stored after the request completes |
| The first line of each page range of a long imported file (at most 300 lines of up to 80 characters) and its page count, when you tap "Find topics" (section 3.2a) | To name and group the topics of the file | 24 hours, under a hash of the lines |
| A cryptographic hash of the text | To avoid charging you twice for the same scan | 24 hours |
| The generated cards, including short verbatim excerpts of your material | To return the same result if the request is retried | Not accessible after 24 hours; physically deleted within 72 hours after that |
| One card's question, answer and excerpt when you tap "Explain", and the explanation | To generate and cache the explanation | 30 days (physically deleted within 72 hours after that) |
| A reported card (type, question, answer, excerpt), the reason and your optional comment | To review the quality and safety of AI-generated content | 90 days |
| Anonymous user identifier (Firebase Anonymous Authentication) | Usage limits, subscription entitlement, abuse prevention | Until you delete your data (section 9) |
| App version, device language, first-use date | Compatibility, default language | Until you delete your data |
| Daily usage counters | Enforcing free and paid limits | 3 days |
| A one-way hash (SHA-256) of the Android device identifier (ANDROID_ID), salted with the App's package name | Applying the daily limit per device as well as per installation, so that reinstalling the App does not grant a new free allowance | 3 days, with the daily counters; the raw identifier never leaves your device and the hash cannot be reversed |
| Google Play purchase token, subscription state and its history | Verifying and maintaining your subscription | Life of the subscription plus an audit period; on deletion the link to your identifier is removed and a token hash is retained for audit |
| Entitlement change history | Audit of subscription changes | 400 days |
| AI usage ledger (token counts, cost, outcome; no content) | Cost control | 400 days; your identifier is replaced by a pseudonym on deletion |
| Technical request logs (identifier, route, status, timing, text lengths and hashes; no content) | Operating and securing the service | 30 days |
| Crash reports (stack trace, device model, OS and App version, memory, time; no content) | Fixing faults in the App | 90 days |
We do not log the content of your scans or cards. Our logging is configured to remove such fields.
When you tap "Find topics" on a long file, the App sends our server the first line of each page range of the document (at most 300 lines of up to 80 characters, with lines that repeat on most pages, such as a lecturer or university name, removed first) and the page count. Our server passes these lines to the AI provider to name and group the topics and keeps the result for 24 hours so the same file is not sent twice. Nothing else from the file is sent at this step; the pages you then choose are read as described above.
The App contains no advertising SDK.
Name, email address, phone number, contacts, precise or approximate location, photos other than the ones you scan (which stay on the device), advertising identifiers, and any data for advertising purposes. The App shows no ads.
| Purpose | Data | Legal basis |
|---|---|---|
| Providing the service you request: creating flashcards, explanations, keeping your subscription active | Recognized text, cards, identifier, purchase data | Performance of a contract (Art. 6(1)(b) GDPR) - the Terms of Service |
| Enforcing usage limits, preventing abuse and fraud, securing the service | Identifier, hashed device identifier, counters, logs, App Check data | Legitimate interests (Art. 6(1)(f)) in protecting the service and controlling costs |
| Fixing crashes and faults | Crash reports | Legitimate interests (Art. 6(1)(f)) in a working, stable App |
| Understanding which features are used, to improve the App | Usage events (counts, flags, category names; no content) | Legitimate interests (Art. 6(1)(f)) in improving the App; you can object by uninstalling or by writing to us |
| Reviewing reported AI-generated content | Reported card, reason, comment | Legitimate interests (Art. 6(1)(f)) in content quality and safety, and legal obligations regarding unlawful content where applicable |
| Keeping subscription and entitlement records | Purchase token, entitlement history | Performance of a contract (Art. 6(1)(b)) and legal obligations on accounting and complaint handling (Art. 6(1)(c)). Google Play is the seller of record for the purchase itself in the countries where Google's terms so provide |
Outside the EEA and the UK we process personal data for the same purposes under the laws applicable to you.
| Recipient | What | Where |
|---|---|---|
| OpenAI, L.L.C. (our AI provider; provider policies: https://openai.com/policies/) | Recognized text, language hint, card settings; for explanations one card's question, answer and excerpt; for "Find topics" the page headlines of the file. No identifier, no images, no other decks. | United States (OpenAI API). Processing under the provider's API data processing terms, which exclude use of the data to train the provider's models |
| Google Cloud (Cloud Run, Firestore, Cloud Logging, Secret Manager) | Hosting of our server and database | europe-central2 (Warsaw, Poland) |
| Google Firebase (Authentication, App Check, Crashlytics, Analytics) | Anonymous identity, app integrity, crash reports, usage events without content | Google's infrastructure per Firebase terms |
| Google Play | Purchases and subscriptions | Google's infrastructure |
We do not sell personal data and do not share it for advertising. If the AI provider changes, this policy is updated in the same release.
Our server runs in europe-central2 (Warsaw, Poland). Our AI provider and Google may process data outside the European Economic Area, including in the United States. For those transfers we rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework, under which both OpenAI and Google LLC are certified, and on the Standard Contractual Clauses contained in the data processing terms of each provider. You may ask sprzedaz@amazinggirl.pl for details of the safeguards used.
Retention periods are stated per data type in section 3.2. Time-based deletion is applied by our database automatically; expired records are never served, and physical deletion completes within 72 hours of expiry. Data on your device stays until you delete it or uninstall the App.
The App is not directed at children under 13. If you are below the age at which your country allows you to consent to online services on your own (16 in Poland and in several other EU countries, 13 in others), you may use the App only with the consent of a parent or guardian. We do not knowingly collect personal data from children below that age. Because the App requires no account, we cannot verify age; if you believe a child has used the App in a way that provided us personal data, contact sprzedaz@amazinggirl.pl and we will delete it.
Under the GDPR you have the right to access, rectify and erase your data, to restrict or object to processing, to data portability, and to lodge a complaint with a supervisory authority. In Poland this is the President of the Personal Data Protection Office (Prezes Urzedu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl). Where processing relies on consent you may withdraw it at any time.
How to exercise them:
Purchase records are kept in a form that no longer identifies you (section 3.2) because we need them to handle refunds and audits. Google Play keeps its own records under Google's privacy policy.
Data is encrypted in transit (TLS). The App contains no server credentials or AI provider keys. Our server verifies every request with a signed token and checks that it comes from a genuine copy of the App. Content fields are removed from logs. Access to production systems is limited to named team members. No method of transmission or storage is completely secure; we cannot guarantee absolute security.
Flashcards and explanations are generated automatically from your material by an AI model. They may be inaccurate or incomplete. You can edit, delete and report any card. Reports are used to improve the quality and safety of generated content; they do not train the AI provider's models under our provider terms. We make no decisions about you that have legal or similarly significant effects based on automated processing.
Review reminders are created locally on your device, only when you have enabled them and cards are due: at most two a day (one at the hour you usually study and one follow-up), or up to three a day during the last days before an exam date you set on a deck. No data is sent to us to deliver them.
We will publish changes at https://cramshot-backend-427793999349.europe-central2.run.app/legal/privacy and update the effective date. For material changes (new data types, new recipients, longer retention) we will inform you in the App before the change takes effect.
ASE Spółka Akcyjna, ul. Portowa 41, 78-100 Kołobrzeg, Poland, sprzedaz@amazinggirl.pl.