Wersja archiwalna 2.3 – obowiązywała od 2026-10-19 do 2026-10-24. Aktualna wersja: zobacz aktualną wersję.
Polityka prywatności
Wiążąca jest czeska i angielska wersja polityki prywatności; poniżej znajduje się wersja angielska.
Version 2.3 · Effective from 2026-10-19 · Controller: ConsultX s.r.o., ID No. 08973288, Dolní Dobrouč 149, 561 02 Dolní Dobrouč
Change log: 2.1 – adds Part B (internet sharing, server, subscriptions); effective only once internet sharing is made available. 2.0 – first complete text from the platform template; replaces the earlier policy (effective 26 Sep 2026, supplemented up to 10 Oct 2026); adds OneDrive and Google Drive, the Feedback Hub, age 16+ and retention periods.
Language notice: this English text is binding for users habitually resident outside the Czech Republic; for users habitually resident in the Czech Republic the Czech version is binding.
Key points
- The controller of your personal data is ConsultX s.r.o.. Contact for all questions and requests: the Feedback Hub in the app (Settings → Report / ask) or info@consultx.cz.
- Part A (without our server, always applies): your photos, videos, comments and episodes stay on your phone. The app has no user account, advertising or analytics and never modifies the originals of your photos. None of this is sent to us, except a support report that you send yourself.
- Part B (once internet sharing is available): our server stores only technical metadata and encrypted content that we cannot read, for at most 14 days. Processors: Microsoft Azure (EU), Cloudflare R2 (EU jurisdiction), Google (FCM, Play Integrity, Play Billing).
- When you share or publish an episode, the GPS location is removed from the copies for others by default.
- We do not sell data and do not use it for advertising or to train models. The app is intended for people aged 16 and over.
- You have the right of access, rectification, erasure, restriction, portability and objection (Articles 15–16). The full procedure for deleting all data is in Article 16.4. You can turn to the Office for Personal Data Protection.
1. Who the controller is and how to contact us
1.1 The controller is ConsultX s.r.o., ID No. 08973288, registered office Dolní Dobrouč 149, 561 02 Dolní Dobrouč ("we"). This policy applies to the Snapisodes app and the website https://snapisodes.cz.
1.2 Contact for data protection, exercising your rights and complaints: the Feedback Hub in the app (Settings → Report / ask) or info@consultx.cz. We reply within 5 working days and handle requests to exercise rights within 1 month (Article 16).
1.3 We have not appointed a data protection officer. We assessed Art. 37 GDPR: our processing is not on a large scale and the duty to appoint did not arise; we review the decision yearly. The contact point for data protection is the Feedback Hub in the app or info@consultx.cz.
1.3a The person in charge of the protection of personal information (for users in Québec, Law 25) is the managing director of ConsultX s.r.o.; contact info@consultx.cz.
1.4 Roles. For Part A (data on your phone) the Operator does not process personal data from photos and comments: it stays with you. For Part B we are the controller of the server metadata (Article 3.2) and the provider of storage of encrypted content for which we hold no key.
2. Where we get the data
We obtain data: (a) directly from you (choices in the app, support reports); (b) automatically from your device (technical server data, Part B); (c) from Google Play (confirmation that a purchase or subscription is active, without the card number); (d) from other users who add you to a shared episode or put photos and comments about you into it (Article 7). We read photos and videos from your phone's gallery at your instruction; they stay on the phone.
3. Purposes, legal bases, categories and retention
3.1 Part A – the app without our server (always applies)
| Purpose | Categories of data | Legal basis (GDPR) | Retention |
|---|---|---|---|
| Running the app's features: episodes, comments, search, map, backups, export (all on the phone) | photos and videos (read-only from the gallery), GPS stored in photos, file names, sizes and times, comments, episode names and descriptions, settings, flag that the Snapisodes All subscription or Pro bought earlier is active | performance of a contract, Art. 6(1)(b) | on the phone until you delete it or uninstall; records of deleted photos 180 days |
| Optional features with consent: place name suggestion, Health Connect, sign-in to OneDrive and Google Drive, camera for QR code | coordinates rounded to 2 decimals (about 1 km; precise location by the definition of Google Play) sent to the system service, steps and distance, sign-in tokens stored encrypted on the phone | consent, Art. 6(1)(a) (withdraw by turning the feature off or revoking the permission); for health data from Health Connect, explicit consent, Art. 9(2)(a) | until withdrawal; tokens until disconnection |
| One-off Pro bought before 2026-10-19 | flag of an active purchase and the confirmation of consent to immediate supply and acknowledgement of the loss of the right of withdrawal (wording, time in UTC, version of the terms, Google Play order number), all stored on the phone; payment is processed by Google Play as an independent controller | performance of a contract, Art. 6(1)(b); proof of the consent, Art. 6(1)(f) (Section 1837(l) Civil Code) | on the phone until uninstall (the confirmation can be exported) |
| Proof of acceptance of the terms and age confirmation | version and hash of the terms, time in UTC, method, confirmation of age 16+ | legitimate interest, Art. 6(1)(f) (evidence of the contract, Section 1751 Civil Code) | on the phone until uninstall |
| Diagnostics at your request | a file with the app and Android version, phone model, language, record counts and the last error (no photos, file names, places or comments) that you send yourself | consent, Art. 6(1)(a) | with you; we do not receive it until you send it |
| Operation of the website snapisodes.cz | technical connection data (IP address) when a page is delivered by the hosting provider; we do not store or evaluate visitors' IP addresses | legitimate interest, Art. 6(1)(f) (delivery and security of the website) | per the hosting provider, short-term |
| Support via the Feedback Hub | text of the report, category, replies, metadata (app and Android version, device, language), random installation ID; a screenshot only if you attach it yourself (off by default, blurred on screens with photos); the text of the report is read by authorised staff and an AI tool (Art. 8.5) | performance of a contract / legitimate interest, Art. 6(1)(b), (f); screenshot consent, Art. 6(1)(a) | reports 24 months, screenshots 90 days |
Location and its accuracy. The place name suggestion (optional, off, turned on with your consent) passes the photo's coordinates, rounded to 2 decimals (about 1 km), to the phone's system service. For Google Play (the Data safety form) an area smaller than 3 km² is precise location, which is why we declare it as such in the store although we round it. We do not derive location from the IP address.
Location permission and nearby devices (sharing between nearby phones). On Android 11 and earlier the system requires the location permission to discover devices over Bluetooth and Wi-Fi; the app does not read or store your device's location, and the permission only lets the system find nearby devices. On newer Android versions the app requests the Bluetooth and nearby Wi-Fi devices permissions (`BLUETOOTH_SCAN`, `BLUETOOTH_ADVERTISE`, `BLUETOOTH_CONNECT`, `NEARBY_WIFI_DEVICES`), for which it does not use location. You can revoke the permissions at any time in Android settings; sharing between nearby phones then stops working.
3.2 Part B – internet sharing (once the server is available)
| Purpose | Categories of data | Legal basis (GDPR) | Retention |
|---|---|---|---|
| Delivering a shared episode to members over the internet (mailboxes, invitations, upload and download addresses) | random device and episode IDs, the device's public signing key, the episode's device list, message sizes and times, encrypted record batches and objects (photos, videos) that we cannot read | performance of a contract, Art. 6(1)(b) | encrypted content at most 14 days, deleted sooner once all devices confirm delivery; invitation 48 hours; sign-in challenge 2 minutes, access token 1 hour; the device list for the life of the episode |
| Notifications about new photos (Firebase Cloud Messaging) | the device's FCM token at the episode mailbox; the notification contains no names or texts | performance of a contract, Art. 6(1)(b); you allow notifications in the system | until the device is removed or the episode is deleted |
| Security, limits and abuse prevention, debugging | truncated IP address, method, route template, status and duration of the request (no IDs, bodies or tokens), quota counters | legitimate interest, Art. 6(1)(f) (security of the service) | operational and security logs (sign-in and authorisation) at most 30 days; counters are cleaned daily |
| Verifying the authenticity of the app and device | Google Play Integrity token (evaluated by Google), signature of the challenge with the device key | legitimate interest, Art. 6(1)(f) | we do not store the token |
| Snapisodes All subscription | subscription status and tier, product ID, validity, auto-renewal, SHA-256 hash of the purchase token (we do not store the token itself) | performance of a contract, Art. 6(1)(b); legal obligation (accounting), Art. 6(1)(c) | for the subscription and 3 years after it ends |
| Quotas and the phone's account key, pseudonymous device and episode identifiers (Art. 17.1) | account key of the phone that created the episode or bought the subscription, quota counters (episodes, photos and videos per month), identifiers derived from the key | performance of a contract, Art. 6(1)(b); legitimate interest, Art. 6(1)(f) (abuse protection) | for the life of the episode or subscription; counters are cleaned daily |
| Handling requests for access, erasure and objection without an account (Art. 17.6) | device and episode identifier, text of the request, server records found | legal obligation, Art. 6(1)(c) (Arts. 15–21 GDPR) | 3 years after handling |
| Proof of acceptance of terms and consents, defence of legal claims | device pseudonym, version and hash of the terms, time in UTC, method (signature with the device key), truncated IP | legitimate interest, Art. 6(1)(f); legal obligations | 3 years after the contract ends |
| Reports of unlawful content, decisions on restriction (DSA) | text of the report, ID of the object or episode concerned, decision and statement of reasons | legal obligation, Art. 6(1)(c) (Regulation 2022/2065); legitimate interest, Art. 6(1)(f) | 3 years |
4. Obligation to provide data and automated decision-making
4.1 Obligation to provide data. The app requires no registration or e-mail. We need the age confirmation and acceptance of the terms to conclude the contract. All other data and consents are voluntary and refusing them does not affect the basic functions of the app.
4.2 Automated decision-making. We do not use automated decision-making with legal or similarly significant effects on you (Art. 22 GDPR), nor profiling for such purposes.
5. Special categories of data (Art. 9 GDPR)
5.1 Photos and comments may reveal health, belief and other sensitive data depending on what you photograph and write. We do not process such data deliberately: in Part A it stays on your phone, in Part B the server sees it only as encrypted blocks. We do not recognise or group faces and do not process biometric data.
5.2 Health Connect (steps and distance). Optional, off by default. We process health data only on the basis of your express consent (Art. 9(2)(a) GDPR). After your express consent the app reads only steps and distance from Health Connect (permissions `READ_STEPS`, `READ_DISTANCE`) and shows them with an episode. It writes nothing into Health Connect, sends the data nowhere, does not share, sell or use it for advertising, and it is never part of a shared episode. You can withdraw consent at any time in Health Connect (Android Settings → Security and privacy → Health Connect).
6. Children and age
6.1 Snapisodes is intended for people aged 16 and over. On first launch you confirm "I am 16 or older". The app is not intended for children and does not target them; in Google Play the target group is 16–17 and 18+.
6.2 If we find that a person under 16 uses the app, we block the features that use the server and delete data about them.
6.3 Photos of children (your own and others') may be part of your content. The user is responsible for sharing them; the rules are in Article 7 and in the Community Rules.
7. Data about third parties in photos and comments
7.1 Users put photos, videos and comments into the app that show other people (family, friends, passers-by, children) and their location. We do not know these persons and cannot inform them in advance; under Art. 14 GDPR we publish the information here. In Part A this data stays on the user's phone and we have no access to it. In Part B we process it only as encrypted blocks in order to deliver it to the members of a shared episode (legitimate interest, Art. 6(1)(f), and performance of the contract with the user).
7.2 The user confirms having the right to share the photos and, where necessary, having informed the persons; they must not share photos of other people's children without the consent of the legal guardians.
7.3 Location. When you share an episode with other people and when you publish it to the cloud, the app by default removes the GPS coordinates from the copies for others (the user can expressly switch them on for a share) and shows a summary before sending. Copies that a member of a shared episode has already received cannot be recalled.
7.4 If you are a person shown in someone else's photo, you can exercise your rights under Article 15 below (contact in Article 1). For Part B we can, following a report, delete the object or episode concerned; for copies on members' phones this is technically impossible. On an access request we may limit disclosure of data that would adversely affect the rights and freedoms of others (Art. 15(4) GDPR).
8. Recipients and processors
The following processors and other recipients process data for us (contract under Art. 28 GDPR). Independent controllers are in particular Google Play (payment), the phone's system services, Android backup and the map tile provider; the Operator does not send them data itself, they process it under their own rules when you use the feature. Our processor is the Feedback Hub (support reports) and, within it, the artificial-intelligence provider Anthropic (Article 8.5). We disclose data to other recipients only where required by law (law-enforcement authorities, courts) or with your consent.
8.1 Part A – the app without a server
| Provider | Purpose | Country of processing | Transfer mechanism |
|---|---|---|---|
| Google Play (Google Play Billing, distribution) | purchase of the Snapisodes All subscription and of Pro bought earlier, restoring a purchase; the app sees only the flag of an active purchase; independent controller of the payment | EU/USA | Google Play terms, SCC / DPF |
| Google ML Kit via Google Play services | recognising photo content and QR codes directly on the phone; the library may send technical usage data to Google | Google ML Kit data disclosure | |
| Google Nearby Connections (Google Play services) | transfer of a shared episode between nearby phones, end-to-end encrypted | locally between phones | – |
| Android backup to a Google account | backup of the database of episodes and comments (not photos) if you have it turned on | Google towards the user | |
| Map tile provider (today OpenStreetMap, tile.openstreetmap.org) | episode map; the provider learns the IP address and the area displayed, not the photos or where they were taken | United Kingdom (OpenStreetMap Foundation) | – |
| System services of the phone (typically Google): speech recognition, geocoding and place search | dictation; place name suggestion (coordinates rounded to 2 decimals, precise location according to Google Play, off by default) and the home address | service chosen by the user in the system | |
| Health Connect (Android) | optional reading of steps and distance | device | – |
| Feedback Hub (the Operator's support system on Azure) | support reports, replies, optional screenshot | EU | Operator's processor |
| Anthropic (artificial-intelligence provider for triaging reports in the Feedback Hub) | proposal of a category and a reply from the text of the report; without name, e-mail and installation identifier; a human sends the reply (Art. 8.5.3) | USA and possibly other countries outside the EU | contractual safeguards (data processing agreement, SCC) |
8.2 Part B – internet sharing (once the server is available)
| Provider | Purpose | Country of processing | Transfer mechanism |
|---|---|---|---|
| Microsoft Azure (Table Storage, container, Key Vault, Application Insights) | running the server, metadata, encrypted mailboxes, logs | EU (West Europe) | data processing agreement (DPA), data in the EU |
| Cloudflare R2 (EU jurisdiction) | encrypted objects of photos and videos, short-lived signed addresses | EU | data processing agreement (DPA), SCC |
| Google Firebase Cloud Messaging | notifications about new photos without names and texts, device token | EU/USA | SCC / DPF |
| Google Play Integrity and Play Developer API | verifying the authenticity of the app and subscription purchases | EU/USA | SCC / DPF |
| Google Play Billing (separate controller, seller of the subscription) | subscription: hash of the purchase token and product ID; Google is the controller of payments | USA | EU–US Data Privacy Framework, SCC |
8.3 OneDrive and Google Drive (services you connect yourself)
8.3.1 Optional. The features are off by default. After you sign in with your Microsoft or Google account (in the browser; the app never sees the password) the app communicates directly with your account; the Operator has no access to this data. The sign-in is encrypted on the phone and not backed up.
8.3.2 OneDrive (Microsoft Graph). Scopes `Files.ReadWrite` and `offline_access`. The `Files.ReadWrite` scope technically allows reading and changing all files in your OneDrive; the app uses it only in the folder you choose. In it the app looks for the copy of a photo you deleted in the app, compares the checksum and, after the waiting period (7 days by default), moves it to the OneDrive recycle bin (it deletes nothing permanently), and uploads copies of the photos and videos of a published episode. The `Files.ReadWrite.All` scope (a folder shared by another person) technically allows access to all files you can see in OneDrive, including files shared with you; the app requests it only at the moment you expressly select such a shared folder, with an explanation of why, and uses it only in that folder. For work and school accounts, use may require the consent of your Microsoft tenant administrator. You revoke access by disconnecting in Settings or at account.microsoft.com → Privacy → Apps and services.
8.3.3 Google Drive (Google Drive API). Scope `drive.file`: the app sees only folders it created or you picked for it and files it uploaded itself; it never deletes anything in the target and never overwrites other people's files. To pick a folder the app may open a helper page on snapisodes.cz; it loads Google's tools only after you tap the Continue button (Article 11.2). You revoke access in Settings or at myaccount.google.com → Security → Third-party apps.
8.3.4 Publishing an episode to the cloud is optional (Snapisodes All): copies of the episode's photos and videos are uploaded without GPS location (by default); the original on the phone is not changed. Uploaded copies stay in your cloud until you delete them there.
8.3.5 Google API Services User Data Policy. Snapisodes's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. (Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy.) We use information obtained from Google APIs only for features visible in the app (publishing an episode to your folder), do not transfer it to others except as necessary to provide the feature or as required by law, do not use it for advertising or to train models, do not use it to determine creditworthiness or sell it to data brokers, and humans do not read it unless you give consent, it is necessary for security reasons or the law requires it.
8.4 Other services used at your instruction
Whatever you share, open in another app or edit in an editor (photos, episode text, story, photobook, diagnostics file) goes to the app you choose; "Open on map" passes the photo's coordinates to the map app. When you open or edit a photo in another app or set it as wallpaper ("Open in…", "Edit in…", "Set as"), the original file is passed including its location; the setting "Remove location when sharing and exporting" does not apply to this. The title or subtitle of a photobook (PDF) may contain a city-level place name derived from the location; you see it in the preview and can edit or delete it before exporting. These apps process the data under their own policies.
8.5 Support and feedback (Feedback Hub)
8.5.1 How we provide support. Exclusively through "Settings → Report / ask" in the app and through the web form on snapisodes.cz (the "Report / ask" page). Your report (a bug, an idea, a question, a request for help or for exercising your rights) is received by our support system Feedback Hub, operated by ConsultX s.r.o. on Microsoft Azure in the EU (West Europe).
8.5.2 What we send. The text of your report and your further messages; technical data (app version, platform and OS version, device type, language, time zone, screen); a random installation ID (not your e-mail or name). We send your name and e-mail only if you tick the contact consent yourself; for a request to exercise rights the e-mail is needed to reply. You attach a screenshot only voluntarily; before storing it we remove hidden metadata (for example location) from it. Please do not write passwords, health data, children's names or data of other people in the report.
8.5.3 Who reads the report, artificial intelligence. Authorised staff and developers of the operator and artificial-intelligence tools the operator uses for support and development (provider Anthropic; processing may also take place outside the EU under contractual safeguards). We do not pass these tools your name, e-mail or installation identifier, and we remove e-mail addresses and phone numbers from the text beforehand. AI may propose a category and a draft reply; a human always reviews and sends the reply, and nothing is decided automatically. We do not use your text to train models.
8.5.4 A web report without contact. The web form needs no account and no e-mail. If you give no e-mail and do not tick the consent to a reply, we have nowhere to reply actively: you can learn the status of the report only by the report number, if we show it to you after sending, or by sending a new report from the app. We release no data or reply about such a report to anyone who does not prove that they submitted it (Arts. 11-12 GDPR).
8.5.5 Notice of unlawful content (Regulation (EU) 2022/2065, Art. 16). The form for a notice of unlawful content in shared episodes has an optional name and e-mail of the notifier; if given, we use them to confirm receipt and to inform about the decision. For notices of child sexual abuse offences no name or e-mail is required.
8.5.5a Reports of abuse in a shared episode. The “Report” function for a member, photo or comment is used to handle notices of inappropriate or unlawful content or behaviour (Regulation (EU) 2022/2065, Art. 16; Google Play user-generated content policy). We send only the episode and record IDs, the chosen reason, your text and an identifier of your device for the answer – no photo or comment content, names or screenshots. The recipient is our reporting system Feedback Hub operated by ConsultX s.r.o. (not a third party). Legal basis: legal obligation (Art. 6(1)(c) GDPR, DSA) and legitimate interest (Art. 6(1)(f)). We keep it while it is handled and then for 24 months; you see the receipt, status and decision in “My reports”. Hidden members and saved groups of people are stored only on your device.
8.5.6 Basis and retention. To handle your request and fix defects - performance of a contract and legitimate interest (Art. 6(1)(b) and (f) GDPR); the "You have a reply" notification only on the basis of consent (point (a)), which you can withdraw at any time. We keep reports for at most 24 months and screenshots for 90 days (Article 13); then we delete them with messages and attachments. Database backups expire within 12 weeks. You exercise your rights (Arts. 15-16) through "Report / ask" (type "Exercise of rights") or at info@consultx.cz.
9. Transfers outside the EU/EEA
9.1 We store server data (Part B) in the EU (Microsoft Azure in an EU region, Cloudflare R2 with EU jurisdiction). Some providers listed in Article 8 (notably Google) may process data outside the EU/EEA, in particular in the USA. Transfers take place only on the basis of an adequacy decision (EU–US Data Privacy Framework for certified companies) or the European Commission's standard contractual clauses (Art. 46 GDPR) and supplementary measures. We base transfers to the USA on the EU-US Data Privacy Framework for certified recipients and, as a fallback, on standard contractual clauses.
9.2 You can request a copy of the safeguards used (contact in Article 1). We keep an up-to-date list of providers at https://snapisodes.cz/pl.
10. Artificial intelligence and on-device recognition
10.1 Search by photo content (labels such as "dog", "beach", "food") and reading the invitation QR code run directly on the phone using the Google ML Kit library (Image Labeling, Barcode Scanning); the model was downloaded by Google Play services. Photos are not sent anywhere for this; labels live only in the phone's cache and are not backed up (the backup holds only the labels you hid on a photo). The library itself may send technical usage data (device, app, performance) to Google, as described in the Google ML Kit data disclosure. Content recognition can be turned off.
10.2 The app does not recognise or group faces, does not use biometric data, does not profile and does not make automated decisions. We do not use your content to train models.
10.3 Outside the app. When processing support reports the Feedback Hub uses artificial intelligence (provider Anthropic) to propose a category and a reply; a human always reviews and sends it, nothing is decided automatically, and your content from the phone (photos, comments) is not used for this (Article 8.5.3). No feature of the app generates content by artificial intelligence.
11. Cookies and similar technologies
11.1 The app uses no cookies and no advertising or analytics SDKs. It uses the phone's local storage only for its own function (the database of episodes, settings, caches).
11.2 The website https://snapisodes.cz is static: it uses no cookies, analytics, tracking pixels or embedded social-media tools, and we host the Inter font ourselves. The only exception is a helper page for picking a Google Drive folder (not indexed). When opened from the app it first shows an information notice; it loads Google's scripts (Google Identity Services and Google Picker) only after you tap the "Continue" button. Google then receives your IP address and browser details and may process them under its own policies (policies.google.com/privacy); the page itself sets no cookies and stores nothing. The website's hosting provider processes the IP address technically when a page is delivered.
12. Security
12.1 We protect data with technical and organisational measures appropriate to the risk: encryption in transit, end-to-end encryption of shared content (the episode key is held only by the members' phones), device keys stored in the Android Keystore, short-lived access tokens, administrator access control, logs without request bodies and tokens, rate limiting.
12.2 App lock. Shared episodes can be locked with a fingerprint, face or screen lock. The lock is provided solely by your phone's system (BiometricPrompt); the app never sees or stores biometric data.
12.3 We notify the supervisory authority of a breach that poses a risk to your rights within 72 hours and, where the risk is high, you as well (Arts. 33, 34 GDPR); because we do not hold your e-mail addresses, we will notify you in the app.
13. Logs, backups and retention
13.1 Overview of retention periods:
| Data | Retention |
|---|---|
| Episodes, comments, settings on the phone | until you delete them or uninstall |
| Records (episode and comment) of deleted photos on the phone | 180 days (only with full access to photos); sooner in Settings → Backup |
| Backup files in Downloads/Snapisodes/Backup | the last 4 automatic ones; they stay after uninstalling until you delete them |
| Copies uploaded to OneDrive / Google Drive | until the user deletes them |
| Encrypted mailboxes and objects on the server (Part B) | at most 14 days, sooner after delivery to all devices |
| Server operational logs (Part B) | 30 days |
| Server security logs (Part B) | 30 days |
| Feedback Hub reports / screenshots | 24 months / 90 days |
| Subscription status, record of acceptance of terms, moderation decisions | 3 years after the contract ends, or from the decision |
| Accounting documents | for the period required by law |
13.2 After data is deleted from the server (removal of a device, deletion of an episode) we remove or anonymise it within 30 days; the infrastructure makes no backups of content or server metadata (deleted key vault secrets can be recovered for 90 days), so deleted data cannot be restored from anywhere.
13.3 We delete or anonymise data whose purpose has ceased; anonymised data is no longer personal data.
14. Changes to this policy
We may change this policy because of changes in law, the service or providers. We announce material changes in the app and on the website at least 30 days in advance; earlier versions are archived at https://snapisodes.cz/pl. Consents beyond the original scope require new consent.
15. Your rights
Under the GDPR you have the right:
- of access to the data and a copy (Art. 15);
- to rectification of inaccurate data (Art. 16);
- to erasure ("right to be forgotten") where there are no grounds to keep it (Art. 17);
- to restriction of processing (Art. 18);
- to portability of data in a machine-readable format (Art. 20);
- to object to processing based on legitimate interest (Art. 21);
- to withdraw consent at any time, as easily as it was given (Art. 7(3));
- not to be subject to a solely automated decision with significant effects (Art. 22).
16. How to exercise your rights, time limit, complaint and deleting all data
16.1 You exercise most rights directly in the app because the data is on your phone (export: backup file, XMP files, photobook; erasure: Article 16.4). For data on the server (Part B) and in support, write via the Feedback Hub (we identify you through your installation and ask for no further personal data) or to info@consultx.cz; we may need to verify your identity, only to the extent necessary.
16.2 We reply within 1 month; in complex cases the period may be extended by a further 2 months, and we will tell you in advance. The reply is free of charge; for manifestly unfounded or excessive requests we may charge a reasonable fee or refuse the request.
16.3 You have the right to lodge a complaint with a supervisory authority: the Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 27, 170 00 Prague 7, Czech Republic, www.uoou.gov.cz; or with the authority in your country of residence or work.
16.4 How to delete all data. In Part A the Operator holds none of your data, so you delete everything yourself; in Part B use steps 7 and 8:
- OneDrive (if you use it): in Settings disconnect OneDrive (this deletes the sign-in and the list of waiting photos). Also revoke access at account.microsoft.com → Privacy → Apps and services. Photos the app already moved to the OneDrive recycle bin are removed from it under OneDrive's rules.
- Publishing to the cloud: in Settings → Publish targets choose Remove for each target; uploaded copies stay in OneDrive or Google Drive, so delete them there yourself. Revoke Google access at myaccount.google.com → Security → Third-party apps.
- Data on the phone: uninstall the app, or in Android Settings → Apps → Snapisodes → Storage choose Clear data. This removes the database of episodes and comments, settings, caches, temporary photos, the OneDrive sign-in and the last crash file. The app never modified the originals of your photos, so none of its changes remain in them.
- Files outside the app: with a file manager or a computer, delete the folder Downloads/Snapisodes (backups, XMP files, photobooks) and use the "Delete backup files" button in Settings.
- Android backup in your Google account: turn backup off, or delete the phone's backup in the Google Drive app → Storage → Backups (this deletes the backup of the whole phone).
- Health Connect: the app writes nothing there; revoke access in Health Connect.
- Shared episodes and the server (Part B): in the shared episode remove your phone (Remove device) or ask the founder to remove you; the founder can also delete the episode together with all its objects on the server. Clearing the app's data or uninstalling deletes the shared-episode database from the phone. Received photos and videos are ordinary files in Pictures/Snapisodes and Movies/Snapisodes: delete them in the gallery. Other members keep the copies they have already received; we cannot delete those. Cancel an active subscription in Google Play (uninstalling does not cancel it).
- Support: ask via the Feedback Hub for your reports in the Feedback Hub to be deleted.
17. Sharing over the internet (Snapisodes server)
17.1 What the server receives. If you turn on sharing over the internet, our server (run in Microsoft Azure in the EU) stores only: pseudonymous identifiers (your device's public signing keys for each episode and a device identifier derived from the key), the account key of the phone that created the episode or bought the subscription, identifiers of episodes, invitations and objects (derived from the content key so that the server does not even see a fingerprint of the content), encrypted and signed mailbox records and encrypted media files (the server knows only their size and time), quota counters (number of episodes, photos and videos per month), the product identifier and a SHA-256 hash of the Google Play purchase token and, if enabled, a Play Integrity token. In transit and in the server's operational log there are the IP address, time, route template, status and response time.
17.1a “Share with the same people” invitations. For a direct invitation the server briefly stores the sealed invitation, a pseudonymous address of the recipient’s inbox (a fingerprint of the device), the time and size of the invitation, which signed-in device reads the inbox, and the IP addresses of the sender and the recipient; the server does not see the content, names or the episode. The invitation is deleted once collected and at the latest after 48 hours; the sender can withdraw it. Operational records with IP addresses are kept for at most 30 days.
17.2 What the server does not receive. The content of episodes, photos, videos, comments, reactions and photo requests, display names, the episode key or the invitation secret (the part of the link after "#"). Content is encrypted on your device; neither we nor anyone with access to the server can read it. For the same reason we cannot restore it if you lose your device and keys. The same applies to the recovery code (Article 17.8).
17.3 Purposes and legal basis. Delivering shared episodes between devices and running the subscription – performance of a contract (Art. 6(1)(b) GDPR). Quotas, abuse protection, verifying the authenticity of the app (Play Integrity) and operational security – legitimate interest (Art. 6(1)(f)); you can object at info@consultx.cz.
17.4 Retention. Mailbox records and media files are deleted once all devices confirm receipt, at the latest after 14 days. The list of episode members (public keys) exists as long as the episode exists; it is deleted when the episode is deleted or the last member leaves. Operational and security logs 30 days; no backups of content or metadata are made (values according to the platform contract).
17.5 Recipients. Microsoft Azure (hosting, EU – West Europe) as processor; Cloudflare R2 (EU jurisdiction) as processor, storing only encrypted media objects; Google (Play Billing – seller of the subscription, Play Integrity – app verification) as a separate controller established in the USA (transfers under the EU–US Data Privacy Framework adequacy decision and standard contractual clauses).
17.6 Your rights without an account. We keep no accounts or e-mail addresses. You can make a request (access, erasure, objection) in the app (Settings → Sharing → Privacy) or at info@consultx.cz, stating the device and episode identifiers that the app shows; we use them to find the records on the server. Deleting an episode in the app also deletes its data on the server.
17.7 Content of other people. Photos and videos may show other people, including children. You are responsible for being allowed to share them; share only with people you trust. Because we cannot see the content, we cannot moderate it; we nowhere scan or automatically evaluate the content of episodes (including searching for child sexual abuse material); an intervention is possible only on the basis of a notice for which the notifier submits the content concerned. Report suspected unlawful content under the Community Rules (state the episode identifier) – we may block the episode or device and cooperate with the authorities as required by law (Regulation (EU) 2022/2065, Arts. 9–10, 16).
17.8 The recovery code stays with you. When you create a shared episode the app generates a recovery code and shows it to you to keep (for example in a password manager or on paper). The code and the episode key never leave your device: we do not send them to the server, to the media storage or to anyone else, so they do not allow us to read content. The server and the members receive only a public verification key, which is used to check the signature of a transfer of administration. If you lose both the administrator's phone and the code, administration of the episode cannot be transferred and we cannot restore it for you.
17.9 Administrator, approver and removal of a member. Every shared episode has one administrator (initially the founder), who adds and removes members and devices and may give selected members the role of approver (who may approve new members and their devices, but may not remove anyone or change roles). A person invited by a member who is not the administrator receives no keys until one of them approves. Removing a member or a device deletes or hides nothing: what the member added to the episode stays with the others, and the copies the member has already received stay with them; the removed member merely gets no further sharing. We cannot technically delete copies already received from a member's device.
18. Users outside the EU
We provide the GDPR standard to all users regardless of country; the same rights and time limits apply to you. We offer the service in the Member States of the EU, the EEA countries (Iceland, Liechtenstein, Norway) and Switzerland.
19. Version and effective date
Version 2.3, effective from 2026-10-19. The document hash (SHA-256) is published at https://snapisodes.cz/pl. No consent to this policy is given; it is information under Arts. 13 and 14 GDPR. Acceptance of terms and consents are recorded separately.
privacy-2.3.en.md · SHA-256: 2ac58feeefa42dceba194a44eb97453c6732d0b0b6f81924a01e216335f18f0c