PRIVACY NOTICE
COINSIDER · DETAILED INFORMATION ABOUT PROCESSING
Effective and last updated: 2026-11-10 · v6.3
Previous version 6.2Service provider and data controller
Tomasz Żądkowski (Coinsider), Sole proprietorship (JDG) Address: ul. Spadek 41, 22-400 Zamość, Polska Tax identification number: NIP 9222733587 Registry number: REGON 060204701 Legal and personal data contact: biuro@strefaczysta.pl
1. Data we process
We process account and authentication identifiers; email and language; a name or profile name only for accounts created earlier through Apple or Google sign-in, when supplied by that sign-in provider; coin photographs and information supplied by the user; scan, identification and report metadata; purchase, entitlement and transaction identifiers; support messages and attachments; public-catalog content chosen by the user; and limited security, diagnostic and operational logs. In Coinsider Explorer we also process pseudonymous likes and session statistics without an account identifier, and in the “2 Coins to start” promotion the data needed to check its conditions and to confirm that ads were watched. In the iOS app Google’s advertising SDK (Google Mobile Ads) works only for the rewarded ads in that promotion, when you choose them, and for the native ads in Coinsider Explorer on the Free plan; in the browser, with your consent, ads may be shown by Google AdSense. We do not sell personal data.
2. Detailed processing table
| Operation and data | Purpose and legal basis | Recipients | Retention |
|---|---|---|---|
| Account and sign-in: e-mail address, password, user ID, language, sign-in evidence and the one-time codes and links sent by e-mail to confirm the address and to change the password; a name or profile name only for accounts created earlier through Apple or Google sign-in, when supplied by that provider. | Create and protect the account; contract and legitimate security interests. | Base44; SendGrid (e-mail delivery of the Base44 platform). | Until account deletion; recovery cycle up to 30 days; security logs up to 12 months. |
| Coin photos and details (Coinsider Vision only): photos, crop, liveview full frame, weight, diameter, description and scan metadata. The description fields that the owner types in before identification are not transferred to Google Cloud/Gemini. | QC, AI identification, reports and fraud prevention; contract and legitimate security interests. | Base44; Google Cloud/Gemini. | Account content until the user deletes it. A deleted coin waits in the Trash for 30 days in the Free plan and 90 days in a paid plan, then we delete it for good; recovery copies up to 30 days; limited Google logs for 30 or 400 days by log class. |
| Results and reports: AI/QC outputs, alerts, reports, serials and operation history. The identification result replaces the description fields typed in earlier by the owner. | Deliver and re-download results, troubleshoot errors; contract. | Base44; Google to generate results; authorised support. | Until coin/account deletion; dispute evidence up to 6 years. |
| Publication (Coinsider Vision certified scans only): sanitised photo copy, description, report, serial number, QR and moderation status. | Optional Encyclopedia publication; publication consent and user licence. | Public visitors (the archive, the Encyclopedia and Coinsider Explorer with the public number of likes), search engines and Base44; no private original or owner identifier. | Until unpublishing/deletion; moderation 12 months, appeal 6 months; independent caches may expire later. |
| Purchases: product, transaction, storefront, entitlement, refund/revocation and balance, including the conversion of scans from the former scan pack into Coinsider Coins. | Plans and Coinsider Coins, double-spend prevention, tax and claims; contract, legal obligation and legitimate interests. | Apple and Base44. | Pseudonymised transaction evidence through 31 December of the sixth year after the transaction year. |
| Support: messages, attachments, contact details and resolution history. | Support, complaints, AI errors and rights requests; contract, legal obligation or legitimate interests. | Base44 and authorised support staff. | Ordinary support 24 months; complaints, disputes and claims up to 6 years. |
| Security: time, action, result, limited session, diagnostic, performance and fraud data. | Service protection, abuse detection and stability; legitimate interests and legal obligations. | Base44, Google Cloud and authorised administrators as necessary. | Generally up to 12 months; required Google Cloud logs up to 400 days. |
| Legal evidence: version, language, text hash, control state, time, product and transaction correlation. | Prove the contract, permission or acknowledgement and defend claims; legal obligation and legitimate interests. | Base44; authorised administrators, authorities or advisers where necessary. | 6 years unless a documented legal hold requires a specific record for longer. |
| Coinsider Snap and data entered by the owner: descriptive data of Coinsider Snap coins, hashes and parameters of their photos, description fields of Coinsider Vision coins typed in before identification (title, period or category, country, denomination, material, mint, ruler, year, condition) and collector data and notes. | Keeping the collection catalogue, synchronisation, restoring from a backup; Article 6(1)(b) GDPR. We do not verify these data and do not transfer them to AI. | Base44. | Until the coin is deleted for good or the account is deleted; description fields of a Coinsider Vision coin until an identification replaces them with its result. A deleted coin waits in the Trash for 30 days in the Free plan and 90 days in a paid plan; recovery copies up to 30 days. |
| Plan and access: the plan of the account, the state and dates of the subscription, the previous plan, the collection limit, the hourly scan limits and their use. | Granting access and limits according to the plan; Article 6(1)(b) GDPR. | Base44; Apple (purchases). | For as long as the account exists. |
| Account deletion signal: a random secret of the account, stored on the account and on the devices where the account was used, and its SHA-256 hash in the account deletion receipt. | Removal of Coinsider Snap photos and of copies of account data from its devices after the account is deleted; Article 6(1)(c) GDPR in conjunction with Article 17 GDPR. Keeping the hash in the receipt: demonstrating that the erasure request was carried out; Article 6(1)(f) GDPR. | Base44. | Secret: until the account is deleted. Hash: 6 years, like the account deletion receipt. |
| Coin state: the identifier and number of a coin in the collection and its state (in the collection, in the Trash, deleted for good or replaced by a Coinsider Vision card). | Consistency of the collection across devices and when restoring from copies: a deleted or replaced coin does not come back from a copy or from pending writes; Article 6(1)(b) GDPR. | Base44. | Until the account is deleted. |
| Coinsider Coins wallet: grant, debit (including for a Coinsider Vision scan), automatic return, conversion of pack scans into Coinsider Coins and balance operations. | Accounting for scans and AI services, crediting Coinsider Coins back to the balance, accounting for payment refunds and handling complaints; Article 6(1)(b), (c) and (f) GDPR. | Base44; Apple (purchases). | Until 31 December of the sixth year after the year of the operation; after account deletion the data are pseudonymised. |
| Purchase confirmation of a pack of Coinsider Coins: product, number of Coinsider Coins, date, transaction identifier, the statements given and the e-mail address of the account. | Confirmation of the contract on a durable medium; Article 6(1)(c) GDPR in conjunction with Article 21(1) of the Polish Consumer Rights Act. Keeping the record of the sending: demonstrating that the obligation was met; Article 6(1)(f) GDPR. | Base44; SendGrid (e-mail delivery of the Base44 platform). | We do not keep the text of the message; the record of the sending, with SHA-256 hashes, is kept for 6 years. |
| Iron Vault file: the Coinsider signature of the scan data and identification results of Coinsider Vision coins, containing the account identifier and an HMAC hash of the original App Store subscription transaction identifier (originalTransactionId); when restoring, the data and photos of these coins from the file, including the data entered by the owner, which the signature does not cover. | Data export and restoration of the collection on the account or on a new account with the same Apple ID, without accepting altered scan data or identification results; the data entered by the owner are restored like the owner’s edits; Article 6(1)(b) and (c) GDPR in conjunction with Article 20 GDPR. | Base44. | We do not store the signature on the server; you keep the file. Restored coins and photos are kept like other account content. When restoring we also record an entry for the photo upload limit; we keep it for 12 months. |
| Plan confirmation: an e-mail after the purchase of a plan or a move to a higher plan (not after a renewal) with the plan, the Coinsider Coins added, the end date of the period and the App Store transaction identifier, sent to the e-mail address of the account in its language. | Information about the active plan and its benefits; performance of the contract, Article 6(1)(b) GDPR. | Base44; SendGrid (e-mail delivery of the Base44 platform). | We do not keep the text of the message; the entry about the sending in the technical logs (account and transaction identifiers) is kept like the security logs, generally up to 12 months. |
| Likes in Coinsider Explorer and in the archive: an account pseudonym (an HMAC-SHA256 hash of the account identifier and e-mail address, computed with a secret key) or, without an account, a device pseudonym (an HMAC-SHA256 hash of a random device key, computed with a separate key), the identifier of the liked record and the day of the like; the public like counter of the record. | Likes and the public counter; from an account: performance of the contract, Article 6(1)(b) GDPR; without an account: legitimate interest in offering likes to people without an account and in protecting the counters from abuse, Article 6(1)(f) GDPR. | Base44; the counter without personal data: public visitors. | A like from an account: until it is withdrawn or the account is deleted, which deletes it together with the account. A like without an account: until it is withdrawn from the same device, at most 24 months from the day of the like. The counter: as long as the public record. |
| Coinsider Explorer session statistics: random identifiers of the session and of the card order, the day and time of the start, the plan (no account, Free or a paid plan), language, platform, app version, entry point, counters of cards viewed, flips, zooms, saves, likes, answers to questions and of views and taps of sponsor cards and Coinsider cards, and short events (kind, card, time, position, ad provider); separately, an anonymous notice of a purchase or registration within a day after a tap on a Coinsider card. No account identifier and no text typed by the user. | Measuring the operation, cost and quality of Explorer, limiting the number of ads, settlements with advertisers in aggregate form and assessing the effectiveness of Coinsider cards; legitimate interest, Article 6(1)(f) GDPR. | Base44. | Up to 90 days from the day of the session, then deleted. |
| The “2 Coins to start” promotion: the acceptance of the promotion and the progress of its steps (one-time codes of the steps, the number and time of failed attempts to show an ad, the coin of the second step), the marker and date of the grant, the scans and identifications left under the promotion and the entries of the Coinsider Coins wallet; confirmations from Google that rewarded ads were watched (account identifier, step code, reward transaction identifier, ad unit, time); to check the conditions: the account creation date, the plan, the balance and purchase history, the account role, the domain of the e-mail address, the activation of the account in the iOS app with the hash of the App Store app download identifier (appTransactionId), an entry about an account with the same e-mail address awaiting deletion, membership of the random comparison group and the daily number of promotions granted. | Granting and settling the promotion under the Terms, including showing the rewarded ad you choose and checking that it was watched, Article 6(1)(b) GDPR; checking the conditions, protecting against repeated use of the promotion and measuring its effectiveness against a comparison group, Article 6(1)(f) GDPR. | Base44; Google Ireland Limited and Google LLC (confirmations that ads were watched). | The promotion fields of the account: until the account is deleted; the wallet entries: as in the row “Coinsider Coins wallet”; the confirmations that ads were watched: until the unit is granted, at most 30 days; the marker that the promotion was used for a given Apple account (hash of the App Store app download identifier, account identifier, campaign and date): 24 months from the grant, also after the account is deleted. |
| Google AdSense ads in Coinsider Explorer in the browser: the decision in the consent message (the TCF string stored in a cookie) and, after consent, data from cookies and ad requests, for example the IP address, cookie identifiers, information about the browser and device, the page address and the views and clicks of ads. | Showing and measuring ads that finance the free use of Explorer; consent, Article 6(1)(a) GDPR and Article 399 of the Polish Electronic Communications Law (in the EEA, the United Kingdom and Switzerland). Further processing for advertising purposes is the responsibility of Google as controller. | Google Ireland Limited and Google LLC; advertising partners named in the consent message. | The browser keeps the consent decision in a cookie of the consent message, for the period stated in that message; the provider keeps the data of ad cookies under its own rules. You can withdraw your consent at any time. |
| Google AdMob rewarded video ads in the “2 Coins to start” promotion in the iOS app: the decision in Google’s consent message (stored on the device by the Google SDK) and the answer in the system tracking dialog (ATT) and, when an ad is shown, data collected by the Google Mobile Ads SDK, for example the IP address, information about the device, system and app, the views of and interactions with the ad and, if you allow tracking, the advertising identifier of the device (IDFA); to confirm the view, the account identifier and the step code passed to Google. | Showing the ad you choose in the promotion and confirming that it was watched: performance of the contract, Article 6(1)(b) GDPR; ads matched to interests and storing and reading information on the device for ads: consent, Article 6(1)(a) GDPR and Article 399 of the Polish Electronic Communications Law (in the EEA, the United Kingdom and Switzerland consent in Google’s consent message; matching also requires permission to track in the ATT dialog). Without these consents the ads are non-personalised, and without consent in Google’s consent message they are shown in limited mode. Further processing for advertising purposes is the responsibility of Google as controller. | Google Ireland Limited and Google LLC. | The Google SDK keeps the decision in Google’s consent message on the device until it is changed or the app is deleted, and iOS keeps the answer in the ATT dialog; Google keeps ad data under its own rules. You change or withdraw your consent in Google’s consent message in the account settings in the app, and your tracking permission in the iOS Settings (Privacy & Security › Tracking). |
| Google AdMob native ads in Coinsider Explorer in the iOS app (Free plan): the decision in Google’s consent message (stored on the device by the Google SDK) and the answer in the system tracking dialog (ATT), shared by all Google ads in the app, and, when an ad is shown, data collected by the Google Mobile Ads SDK, for example the IP address, information about the device, system and app, the views of and interactions with the ad and, if you allow tracking, the advertising identifier of the device (IDFA). We do not pass the account identifier to Google. | Showing and measuring labelled ads that finance the free use of Explorer: legitimate interest, Article 6(1)(f) GDPR; ads matched to interests and storing and reading information on the device for ads: consent, Article 6(1)(a) GDPR and Article 399 of the Polish Electronic Communications Law (in the EEA, the United Kingdom and Switzerland consent in Google’s consent message; matching also requires permission to track in the ATT dialog). Without these consents the ads are non-personalised, and without consent in Google’s consent message they are shown in limited mode. Further processing for advertising purposes is the responsibility of Google as controller. | Google Ireland Limited and Google LLC. | The Google SDK keeps the decision in Google’s consent message on the device until it is changed or the app is deleted, and iOS keeps the answer in the ATT dialog; Google keeps ad data under its own rules. The counter of ads shown stays on the device only, and we keep the session statistics as in row 18. You change or withdraw your consent in Google’s consent message in the account settings in the app, and your tracking permission in the iOS Settings (Privacy & Security › Tracking). |
3. Purposes and legal bases
We process data to create and secure the account, provide scans and AI identification, maintain subscriptions and virtual balances, generate reports, provide support, prevent abuse, meet legal obligations and defend claims. Depending on the activity, the basis is performance of a contract, legal obligation or legitimate interests. Consent is requested only for a specific optional action, such as publishing a report; it is not bundled with access to the service and can be withdrawn prospectively.
4. Data sources and required information
We receive data from the user, the device when a requested feature is used and Apple in connection with a transaction. Email and account identifiers are required for an account; coin photos and details are required only for the selected analysis; publication is optional. Missing information required for a feature prevents that feature from working but does not authorize another use.
5. Disclosure to Google Gemini
When the user expressly requests QC, identification, a PRO report or image search, selected coin photos, user-supplied details (except the description fields of a Coinsider Vision coin that the owner typed in before identification), request context and necessary technical identifiers are transmitted through Coinsider infrastructure to Google Cloud/Gemini. The purpose is limited to the requested feature, security and diagnostics. Under the applicable paid API terms, prompts and responses are not used to improve Google products; Coinsider does not train its own models on them without a separate opt-in.
Coinsider Snap does not use AI and does not transfer photos or data to Google.
The permission to transfer data to AI is separate and voluntary. Your collection, Coinsider Snap and support provided by people work without it. We ask for it before you first use an AI feature; at sign-up you may give it or skip it.
AI features are: the photo quality check, identification, the PRO analysis, image search, the assistant in support, and the machine translation of your messages to support and of your appeals against moderation. Before each such operation our server checks the permission of the owner of the data, also when a member of Coinsider staff acts. Without the permission neither your photos nor your texts reach the AI provider, and our staff read your messages in the original.
You can withdraw the permission at any time in your account settings, as easily as you give it. After the withdrawal we start no new AI operation on your data; operations already accepted are completed. Results saved in your collection remain, and the withdrawal does not affect the lawfulness of earlier transfers.
We record the giving and the withdrawal of the permission with the date, the version and the language of the text, so that we can demonstrate what you agreed to or withdrew. We keep this record for 6 years.
6. Providers and recipients
The principal AI provider is Google Gemini within Google Cloud; Google Cloud Vision and infrastructure may support image analysis. Base44 provides the application platform and hosting. Apple provides StoreKit and App Store billing. No push provider is active in release V1. A future push feature requires a separate product, privacy and vendor review before activation. Providers act under applicable contracts. Transfers outside the EEA or UK must rely on adequacy decisions or appropriate safeguards such as standard contractual clauses, the UK Addendum or IDTA, plus any required transfer assessment—not on “consent by use.”
E-mails from the app, for example with the code that confirms the address, for changing the password and with a purchase confirmation, are sent from an address in the coinsider.ai domain through the e-mail service of the Base44 platform, operated by SendGrid (Twilio group). SendGrid may measure opens and clicks of these messages: an invisible image in the message tells it that the message was opened, and links lead through its server, which records the click and then redirects. It records the time, the IP address and information about the e-mail program or browser, for its sending statistics. The measurement is a setting of the sending provider; we do not use its results for marketing or profiling. You can limit it by turning off the automatic loading of images in your e-mail program.
When the third finished result of a Premium identification or a PRO analysis appears on the device, the iOS app may ask the system for the App Store rating dialog, regardless of how you rated the results, at most once every 120 days and never while you decide on a PRO analysis. Apple shows and handles the dialog, and we give no benefit for a rating. We do not learn whether the dialog appeared or whether and how you rated the app; in the diagnostic data of the app, without an account identifier, we note only whether the request was sent and, if not, for what reason.
| Provider | Scope and role | Location / transfer | Key terms |
|---|---|---|---|
| Base44 / Wix group | Platform, hosting, authentication, database, functions, storage and e-mail delivery (through SendGrid as a sub-processor); processor. | Production: United States; DPA, DPF/adequacy and SCCs. | TLS, encryption at rest, access controls; deleted records recoverable for up to 30 days. |
| Google Cloud / Gemini API | QC, identification, PRO reports, image search and infrastructure; processor/AI service provider. | Core infrastructure europe-west1; other locations under Cloud DPA/SCCs. | Paid API no use of prompts/responses to improve products; no File API or durable Gemini profile. |
| Apple | App Store, StoreKit, refunds and storefront; activity-specific role. | Under Apple terms. | Coinsider receives minimal transaction/entitlement identifiers, including a pseudonymous appAccountToken that binds the subscription to one account; account deletion does not cancel a subscription. |
| OneSignal — historical erasure only | No V1 SDK or new notifications; only deletion of a historical identifier. | No new operational transfers. | After erasure it is not a provider of the active release. |
| Google Ireland Limited (Google AdSense, Google AdMob and the consent messages) | Ads in Coinsider Explorer in the browser and the consent message (TCF 2.2); in the iOS app, rewarded video ads in the “2 Coins to start” promotion with the confirmations of views, native ads in Coinsider Explorer on the Free plan and the consent message; controller of the data collected through its own cookies, scripts and SDK. | Ireland; Google LLC in the United States (Data Privacy Framework and standard contractual clauses). | We load the ad script only in the browser, when ads are switched on, and where consent is required only after it. In the iOS app we start the Google Mobile Ads SDK only when you choose an ad in the promotion or when an account on the Free plan opens Coinsider Explorer with ads switched on; the ads are matched to interests only after permission to track (ATT) and, in the EEA, the United Kingdom and Switzerland, also after consent in Google’s consent message. Rules: policies.google.com/technologies/partner-sites. |
7. International transfers
Base44 hosts production application data in the United States. The Base44 DPA provides applicable adequacy and Data Privacy Framework mechanisms and Standard Contractual Clauses. Configured Google infrastructure operates in europe-west1; other support and subprocessing locations are governed by the Google Cloud DPA and SCCs. Information about safeguards may be requested at biuro@strefaczysta.pl.
Ad data is received by Google Ireland Limited, which may transfer it to Google LLC in the United States: in the browser, data from cookies and ad requests after your consent, and in the iOS app, the data of the rewarded ads you choose in the promotion with the confirmations that they were watched, and of the native ads in Coinsider Explorer. Google relies on the Data Privacy Framework and standard contractual clauses.
8. Retention and account deletion
Active account and coin content is kept until deletion. Immediate deletion starts after verified reauthentication; scheduled deletion provides a 30-day restoration window, while public records are withdrawn immediately. Base44 may retain deleted records in its recovery cycle for up to 30 days. Ordinary support is kept for 24 months after closure; consumer/account/AI disputes and legal claims, legal-text acceptance and deletion evidence for 6 years; moderation evidence for 12 months with a 6-month in-app appeal; security and fraud logs for 12 months. Apple/tax/ledger evidence is de-identified at account deletion and kept through 31 December of the sixth calendar year after the transaction year. A documented court, regulator, tax, claim, security or fraud hold pauses deletion only for the affected class and is reviewed at least every 90 days. Deletion does not cancel an Apple subscription.
When a subscription ends, the account and its data stay in the Free plan until you delete the account. Details are set out in the Terms, section “End of the subscription and account deletion”.
A coin you delete is kept in the Trash for 30 days in the Free plan and 90 days in a paid plan, and is then deleted for good.
After you ask for your account to be deleted, you can restore it within 30 days, or within 3 months for an account in the PRO plan. We then delete the account and its data, except data we must keep by law and data covered by a documented deletion hold (legal hold). You can also delete the account at once.
We keep Coinsider Explorer data briefly: session statistics up to 90 days, likes without an account at most 24 months from the day of the like, and likes from an account until they are withdrawn or the account is deleted. We delete the confirmations that rewarded ads in the “2 Coins to start” promotion were watched once the unit is granted, and unclaimed ones after 30 days at the latest. We keep the marker that the promotion was used for a given Apple account for 24 months from the grant, also after the account is deleted.
9. Rights, complaints and contact
Subject to applicable law, users may request access, correction, deletion, restriction, portability and objection, and may withdraw a specific consent. EEA users may complain to their local supervisory authority or Poland’s UODO; UK users may complain to the ICO. California residents may exercise applicable rights to know, delete, correct and non-discrimination; Coinsider does not sell personal data. In the iOS app Google ads, that is the rewarded ads in the “2 Coins to start” promotion and the native ads in Coinsider Explorer, are matched to interests only if you allow tracking in the ATT dialog and, in the EEA, the United Kingdom and Switzerland, also give your consent in Google’s consent message; otherwise they are non-personalised; in the browser, Google AdSense cookies may serve advertising matched to interests, and in the EEA, the United Kingdom and Switzerland only with your consent (section “Coinsider Explorer, likes and ads”). Requests: biuro@strefaczysta.pl. Support: coinssupportpl@wp.pl.
We give effect to the right to data portability by, among other means, the Iron Vault file, which you can save in the iOS app or in the browser on every plan, also after your subscription ends. The file is a single ZIP archive and covers the whole collection: Coinsider Snap and Coinsider Vision coins, including those in the Trash, their data and identification results in JSON and CSV files, and their photos, in ZIP archives. It is a commonly used, machine-readable format. You can encrypt the file with your password; anyone who has a file saved without a password can open it. We receive neither the file nor the password. We will provide data that the file does not cover on a request sent to the address given above.
10. AI and automated decision-making
Identification and valuation results are probabilistic and informational. Coinsider does not use them to make solely automated decisions producing legal or similarly significant effects on the user. Every user can ask for a human review of an AI result, whatever the plan; we reply within 7 days.
11. Data stored on your device
The application saves in the storage of your device the data necessary for the operation of the services you ask for: session state, language and settings, a copy of collection data for offline use and photos of coins added in Coinsider Snap. Coinsider Snap photos do not leave the device unless you export them yourself, for example in an Iron Vault file or in a collector card PDF. A backup of the whole device that you turn on in the system settings (for example iCloud) may include the application data, including these photos. You and the provider of the system manage such a backup. You can exclude the data of this application from such a backup in the backup settings of the system. Before saving, the application re-encodes the photo, reduces its size if necessary and removes its metadata, including location information. Saving these data is necessary to provide the service, so it does not require separate consent (Article 399 of the Polish Electronic Communications Law). You can delete these data in the application settings, by deleting the application or by clearing the site data in the browser. An Iron Vault file saved in the app lies in its folder on the device (visible in the Files app), is covered by the backup of the device, and you can copy or delete it from there. In the browser, the Iron Vault file is downloaded to where the browser saves downloaded files; the website does not keep it. After the final deletion of the account the app removes this file from the device together with the other data of the account; before that you can save a copy of it elsewhere.
We do not process Coinsider Snap photos on our servers and we have no access to them. We process only the descriptive data linked to the coin and the cryptographic hash and parameters of the photo (size, dimensions, time added). We do this to recognise the photos when they are restored from an Iron Vault file or a Coinsider Snap backup and to avoid creating duplicates.
After migration from Coinsider Snap to Coinsider Vision is complete, the new card keeps the collection number and date added. We retain the link between records and the consent and completion markers so that old backups and pending writes cannot restore the deleted Snap card. These technical records remain until account deletion, even if you delete the new Vision card earlier. Backup files and PDFs previously saved outside the application remain under your control. The new card takes over the collector data, the notes and the entered weight and diameter of the old card; it does not take over its description, which the identification fills in or you enter again.
12. Local data, security and minors
The web and app store necessary session state, language, settings and acknowledgement versions locally. In the iOS app we start the Google Mobile Ads SDK only for the rewarded ads in the “2 Coins to start” promotion that you choose and for the native ads in Coinsider Explorer on the Free plan; we ask for tracking permission (ATT) once per device, before we show the first Google ad: in the promotion before the first rewarded ad, and in Coinsider Explorer when you open the feed on the Free plan. The advertising identifier (IDFA) is available to Google only after that permission, and the app itself never reads it; we use no cookies for behavioural advertising in the app. In the browser, Google AdSense cookies work only in Coinsider Explorer, under the rules of the section “Coinsider Explorer, likes and ads”. Measures include transport encryption, access control, minimisation, operation logging and incident procedures. No system can guarantee absolute security. The service is only for persons aged 18 or over.
The application removes EXIF metadata, including GPS data, from Coinsider Snap photos and does not send these photos to servers. Files on the device are kept separate for each account. The application encrypts the Iron Vault file with a password that you choose, using AES-256; a file saved without a password is not encrypted. We receive neither the file nor the password. When Coinsider Vision coins are restored, the application sends us only their data and photos from the file, and we keep those photos like the photos of scans. Coinsider Snap coins return to the account as descriptions, and their photos stay on the device. Details are set out in the section “Data stored on your device”.
13. Changes and contact
Material changes are published with a new date and version. If a new purpose requires consent, we ask before processing starts. Data requests: biuro@strefaczysta.pl. Complaints may be made to the competent authority, including Poland’s UODO or the UK ICO.
Account deletion14. Data in content notices
The Coinsider service provider identified in this Notice controls notice data. We process contact details, supplied name, language, URL/identifier, description, reasons, correspondence and necessary email metadata to review, reply, handle appeals and prevent abuse. The bases are applicable legal obligations and legitimate interests in protecting the service and people’s rights, not marketing consent or AI permission.
Preparing the form does not transmit its fields to Base44 or AI or save them in browser storage. Opening your email app passes the text to that app; subsequent processing and sending follow your email service. WP Poczta (Wirtualna Polska Media S.A.) and authorised Coinsider staff handle mail to coinssupportpl@wp.pl. Where necessary for moderation or appeal, an authorised person may record case evidence in Base44; receiving an email does not automatically create a ticket or run AI.
Moderation evidence follows the retention table: generally up to 12 months, and appeal evidence up to 6 months; specific claims evidence may require up to 6 years, with longer retention where legally required or subject to a documented legal hold. Access is limited to necessary staff and providers. Reporter contact details are not published in the archive. Without contact details, an individual reply is impossible. Data rights and contact biuro@strefaczysta.pl are described in this Notice.
Reporting and notice-and-action15. Coinsider Explorer, likes and ads
Coinsider Explorer works in the iOS app and in the browser, also without an account. To arrange the cards, the app sends to Base44 the language, the plan (or the information that you are not signed in), the platform, the app version and short lists of preferences (for example eras, rulers, materials, denominations, countries and Encyclopedia drawers) from the interest profile stored on your device. The server uses them only to arrange the cards and does not store them. Matching the cards to your interests is profiling that produces no legal effects for you and does not similarly significantly affect you. The legal basis is the performance of the contract (Article 6(1)(b) GDPR) and, for people without an account, our legitimate interest in offering a matched view of the public archive (Article 6(1)(f) GDPR).
On the device, in the memory of the app or of the browser, Explorer stores: the interest profile (weights that decrease with each session), the lists of saved and liked coins, the results of “Test yourself” questions, the state of an interrupted session, a random device key (for likes without an account and for the gradual availability of Explorer), a counter of sponsor cards shown on the day (and, when an hourly limit applies, also the times such cards appeared in the last hour) and, for at most a day, the information about a tap on a Coinsider card. These data do not leave the device except for the requests and statistics described in this section; you delete them by clearing the data of the app or of the website. Storing them is necessary for the Explorer features you use, so it does not require separate consent (Article 399 of the Polish Electronic Communications Law).
We store a like from an account under the account pseudonym: an HMAC-SHA256 hash of the account identifier and e-mail address, computed with a secret key, without the identifier and address themselves. We store a like without an account under the device pseudonym: an HMAC-SHA256 hash of the random device key, computed with a separate key, without the key itself; we do not link the device pseudonym to an account or to a person. With a like we also store the identifier of the record and the day, and with the record we publish only the total number of likes. The IP address is used in real time for the request limit and is not stored with a like. Deleting the account deletes its likes; until the next change of the likes of a coin, its counter may show one more. You withdraw a like without an account from the same device; after the data of the device are cleared we can no longer link it to you.
The session statistics, described in the processing table, contain no account identifier; some sessions may not be reported at all. When a purchase or registration follows within a day after a tap on a Coinsider card, the app sends a separate, anonymous notice of the kind of card only. We may give an advertiser the number of views and clicks of its sponsor cards only in aggregate form.
Our app shows sponsor cards and Coinsider cards itself, without advertising SDKs and without third-party cookies. The image of a sponsor card may be loaded from a server named by the advertiser, which then receives the IP address and information about the browser or app; after a tap on the card you go to the advertiser’s page, for which the advertiser alone is responsible. In the browser, when ads are switched on, we load the Google consent message, a consent management platform compliant with TCF 2.2. In the EEA, the United Kingdom and Switzerland we load the AdSense script only after your consent to storing information on the device and to that provider; without consent, a Coinsider card takes the place of the ad. After consent, the provider may store and read cookies to show ads, including, if you allow it, ads matched to your interests, to measure them and to protect them from abuse. Outside these areas, ads may work without the consent message, under the provider’s rules. There are no AdSense ads in the iOS app; paragraphs 7 and 8 describe the Google ads in the iOS app.
You can withdraw or change your consent to ad cookies at any time in the privacy and cookie settings available in Coinsider Explorer in the browser, and also by deleting the cookies of the website; withdrawal does not affect the lawfulness of earlier processing. The consent message lists the partners and the storage periods of the cookies under “Manage options”, and the page policies.google.com/technologies/partner-sites sets out the provider’s rules. You may object to processing based on legitimate interest (Article 21 GDPR).
We show rewarded video ads in the “2 Coins to start” promotion only in the iOS app and only when you choose an ad to receive a unit of Coinsider Coins (Terms, section “Coinsider Coins”); there are no rewarded ads in Coinsider Explorer (paragraph 8 describes the native ads in Explorer). They are shown by the Google Mobile Ads SDK (Google AdMob), which we start only after that choice. In the EEA, the United Kingdom and Switzerland, before the first ad Google shows a consent message (IAB TCF standard) and stores your decision on the device; without consent Google shows the ads in limited mode. Then, once per device, the app asks in the system App Tracking Transparency (ATT) dialog whether you allow tracking. Google’s consent message and the ATT dialog are shared by all Google ads in the app: an answer given earlier, for example when you opened Explorer, also applies in the promotion. The ads are matched to your interests only if you allow tracking and, in the EEA, the United Kingdom and Switzerland, also give your consent in Google’s consent message; Google may then use the advertising identifier of the device (IDFA) and link data from this app with data from other apps and websites. In all other cases the ads are non-personalised. Your answer in the ATT dialog or in Google’s consent message does not affect whether you receive the unit. Google processes the data collected by the SDK (for example the IP address, information about the device and app, and the views of and interactions with the ad) as a separate controller, under the rules at policies.google.com/technologies/partner-sites. To grant a unit, we pass your account identifier and a one-time step code to Google, and Google sends a signed confirmation of the view to our server; we delete it once the unit is granted, and an unclaimed one after 30 days at the latest. The legal basis for showing the ad you choose and checking that it was watched is the performance of the contract (Article 6(1)(b) GDPR), and for ads matched to interests and storing and reading information on the device for ads, your consent (Article 6(1)(a) GDPR, Article 399 of the Polish Electronic Communications Law). You change your tracking permission in the iOS Settings (Privacy & Security › Tracking) and, in the EEA, the United Kingdom and Switzerland, your consent in Google’s consent message in the account settings in the app (“Ad privacy settings”); declining ads blocks nothing in the app.
In the iOS app an account on the Free plan may see in Coinsider Explorer, between the coin cards, a card with a Google AdMob native ad, that is an ad in a layout prepared by Google, shown inside the card; the card is labelled “Ad”, explains why you see it, offers a way to report the ad and has a button to go to the next coin, and the Terms limit how often it appears (section “Coinsider Explorer and likes”). Accounts on paid plans and people without an account see no Google ads in Explorer in the app. The ads are shown by the Google Mobile Ads SDK, which in Explorer we start only when an account on the Free plan opens it and ads are switched on. Google’s consent message and the ATT dialog are shared by all Google ads in the app: in the EEA, the United Kingdom and Switzerland, before the first ad Google shows a consent message (IAB TCF standard), and then, once per device, the app asks in the system ATT dialog whether you allow tracking; if you have not answered them earlier in the promotion (paragraph 7), you will see them when you open Explorer. The ads are matched to your interests only if you allow tracking and, in the EEA, the United Kingdom and Switzerland, also give your consent in Google’s consent message; Google may then use the advertising identifier of the device (IDFA), which the app itself never reads. In all other cases the ads are non-personalised, and without consent in Google’s consent message they are shown in limited mode. Your answers in the ATT dialog or in Google’s consent message do not affect your access to Explorer or your Coinsider Coins. We grant nothing for watching or clicking an ad: the ads finance the free use of Explorer. Google processes the data collected by the SDK (for example the IP address, information about the device and app, and the views of and interactions with the ad) as a separate controller, under the rules at policies.google.com/technologies/partner-sites; Google receives no account identifier from us. We count the ads shown only on the device, for the limits on the number of ads, and the views and taps in the session statistics without an account identifier (paragraph 4). The legal basis for showing and measuring labelled ads that finance the free Explorer is our legitimate interest (Article 6(1)(f) GDPR), and for ads matched to interests and storing and reading information on the device for ads, your consent (Article 6(1)(a) GDPR, Article 399 of the Polish Electronic Communications Law); you may object to processing based on legitimate interest (Article 21 GDPR). You change your tracking permission in the iOS Settings (Privacy & Security › Tracking) and, in the EEA, the United Kingdom and Switzerland, your consent in Google’s consent message in the account settings in the app (“Ad privacy settings”).