Privacy Policy

Buck is a coin and banknote identifier. You take or import a photo, Buck tells you what the item is, shows an estimated market value or value range, and lets you keep a personal collection. Buck has no user accounts and does not sell your data. Because we advertise Buck on TikTok, the App includes the TikTok Business SDK, which reports a few app events to TikTok so we can measure and improve those ads (Section 3.10). On iPhone, your advertising identifier is shared only if you allow tracking.

This policy is written to be accurate to how Buck works today on iPhone and Android, including the optional auto-renewing subscription offered through Apple In-App Purchase and Google Play Billing, the AI services we use to identify items, the community finds feed, the leaderboard and friend invites, the logging we run to keep recognition working, and the advertising measurement described in Section 3.10. If we change what Buck collects, we update this policy and the effective date above before the change goes live.

1. Who we are and who controls your data

Buck is published by a different party on each app store. The data controller responsible for your personal data under the EU and UK General Data Protection Regulation (GDPR) is the publisher of the app you use:

• Buck for iPhone (Apple App Store): Emanuele Pio Totaro, Italy
• Buck for Android (Google Play): EXO, the Netherlands

In this policy, "we", "us", and "our" mean the controller of the app you use. Both apps work the same way and use the same backend service, so this policy covers both and says so where they differ. Contact for privacy matters, for either app: privacy@getbuckapp.com

If you are in the European Economic Area, the United Kingdom, or another region with data protection authorities, you also have the right to contact your local supervisory authority (see Section 11, "Your rights").

2. A quick summary

• No account. You do not sign up, log in, or create a profile to use Buck.
• Your scan photos go to an AI service. The photos you scan are sent to our recognition backend, which passes them to Google Gemini, an artificial intelligence (AI) service we use as a sub-processor, to identify the item (Section 5). The App does not ask for a separate permission for this: scanning a photo sends it.
• Your scan photos are kept in our logs. Every photo you scan, identified or not, is also kept in our private quality logs (on our server, in a private Telegram channel and, on iPhone, in Appdeck) together with your device identifier, so we can monitor and improve recognition. On iPhone, a picture of Buck's screen is also logged whenever you take a screenshot in the App. There is no setting to turn this off; you can ask us to delete your photos (see Sections 3.4, 3.9, 5, and 8).
• Your finds are shared with other users. When a scan identifies an item, its cropped photo, the item's name and estimated value, a display name the App generates, and your approximate city and country are shared with other Buck users in the community feed (Section 3.8). The number of items in your collection and their total value appear on the leaderboard under your profile name (Section 3.11). Both happen automatically.
• Your collection stays on your device. Your collection and app data are stored on your device. Only summary figures leave it, such as the totals shown on the leaderboard (Section 3.11).
• No selling. Ad measurement with TikTok. We do not sell your personal data. The App tells TikTok about a few events, such as the install, the subscription screen being shown, and purchases, together with device identifiers, so we can measure and improve our ads on TikTok (Section 3.10). On iPhone, Buck may ask for your permission through Apple's App Tracking Transparency prompt, and your advertising identifier is shared only if you allow tracking. Your photos, scans, and collection are never sent to TikTok.
• Apple or Google handles payments. If you purchase a subscription, Apple (App Store) or Google (Google Play Billing) processes the payment. We never see your full card number or billing details.

The rest of this policy gives the detail that Apple, Google, the GDPR, and the California Consumer Privacy Act (CCPA/CPRA) expect.

3. What data we collect, and why

3.1 Camera images you capture

When you use the in-app scanner, the App accesses your device camera so you can photograph a coin or banknote. Buck requests camera permission through the standard iPhone or Android permission prompt before any camera access. The captured image is used to identify the item and to display an estimated value. See Section 5 for exactly how the image is processed and where copies of it are kept, and Section 6 for the third parties involved.

• Purpose: to identify the coin or banknote in the photo and show an estimated value or value range.
• Legal basis (GDPR): performance of a contract (Article 6(1)(b)). Scanning is the core function you ask Buck to perform.

3.2 Photos you submit from your photo library

Instead of using the camera, you can choose an existing photo using the system photo picker on iPhone or Android. The photo picker hands Buck only the specific image you select. Buck does not get access to your wider photo library, and neither system requires a photo library permission for this. The selected image is then processed the same way as a camera capture (Section 5).

• Purpose: the same as camera images: identification and value estimation.
• Legal basis (GDPR): performance of a contract (Article 6(1)(b)).

3.3 Your collection and app preferences (stored on your device)

Buck saves your collection and app state locally on your device, using the standard on-device storage of iPhone (UserDefaults) and Android. This information stays on your device. It is not an account, and we cannot read it remotely. The exceptions are the totals the leaderboard uses (Section 3.11) and the figures the in-app chat sends (Section 3.6). Deleting the App removes this local data (see Section 8), except the device identifier described in Section 3.7.

• Purpose: to remember your collection and app state between sessions and let the App work offline.
• Legal basis (GDPR): performance of a contract (Article 6(1)(b)). This data is processed on your device, not by us.

3.4 Device, diagnostic, and usage information

Apart from the TikTok Business SDK, which we use only to measure and improve our own advertising (Section 3.10), and RevenueCat's subscription SDK (Section 3.5), Buck does not embed any third-party analytics, advertising, or crash-reporting software development kits (SDKs). We do run our own usage logging so we can see that the App works and improve it. This logging records app events (for example that the App was opened, that a scan was completed, or that the paywall was shown) together with basic technical context: your device model, operating system version, App version, device language and region settings, an approximate city-level location derived from the IP address of the request, and the random device identifier that the App creates on first launch (Section 3.7). It also records crash and performance reports (for example where in the App a crash happened, launch time, and memory use). The device identifier is not your name, email, phone number, Apple Account, or advertising identifier, and on its own it cannot be used to identify you across other companies' apps or websites (see Section 3.7 for the one case where a hashed copy is shared with TikTok).

Depending on the kind of entry, these logs go to our own analytics database on our server in Germany, to a private Telegram channel that our backend posts to, and to Appdeck, the analytics, logging, and testing service we use to run Buck (Section 6). Only we can read them. They are used to operate, debug, and improve the Service and to test changes (for example which version of a screen works better). The logs themselves are never used for advertising, never sold, and never shared with data brokers. A few of the same app events are also sent, separately, to TikTok to measure our advertising (Section 3.10).

Scan photos and screenshots are part of these logs. A copy of every photo you scan is included (Section 5), and on iPhone so is a picture of Buck's screen each time you take a screenshot while Buck is open (Section 3.9). There is no setting in the App to turn this off.

When the App contacts our recognition backend, the connection also necessarily involves basic technical information that is part of any internet request, such as your device's IP address and a standard request timestamp. We use this to operate the Service securely, including rate limiting and abuse prevention, so that the recognition endpoint stays available and is not misused. We do not use it to build an advertising profile.

If you have enabled Apple's optional sharing of app analytics and diagnostics at the iOS level, Apple may provide us with aggregated, non-identifying crash and usage statistics through App Store Connect. Google Play similarly gives us aggregated crash and performance statistics from Android devices whose owners share usage and diagnostics data with Google. This is controlled by you in your device settings and is governed by Apple's or Google's privacy policy.

• Purpose: to keep the Service running, secure, and reliable, and to improve and test it.
• Legal basis (GDPR): legitimate interests (Article 6(1)(f)) in operating, securing, improving, and protecting the Service against abuse.

3.5 Subscription and purchase status

Buck offers an optional auto-renewing subscription with a free trial. The purchase is made through Apple's In-App Purchase system on iPhone or Google Play Billing on Android. Apple or Google processes the transaction and your payment. We do not receive or store your credit card number, your full billing address, or other payment card details.

The App uses RevenueCat (Section 6) to learn whether you currently hold an active subscription or trial, so it can unlock the corresponding features. RevenueCat receives your device identifier (Section 3.7) and your purchase information (product, price, subscription status). RevenueCat also tells our backend when a subscription starts, renews, or ends, with the product, the price, and your device identifier, and we record these events in our logs (Section 3.4).

On iPhone, RevenueCat also collects Apple's ad attribution token (AdServices), which tells us which of our Apple Ads campaigns, if any, led to your install.

• Purpose: to unlock and manage subscription features you have paid for, and to see which of our Apple Ads campaigns bring subscribers.
• Legal basis (GDPR): performance of a contract (Article 6(1)(b)) for the subscription; legitimate interests (Article 6(1)(f)) for purchase records in our logs and for Apple Ads attribution.

3.6 Messages you send us

If you email us (for example at support@getbuckapp.com or privacy@getbuckapp.com), we receive your email address and whatever you choose to put in your message, so we can reply and help you.

The App also has places where you can write to us, such as the "Deleting? Tell us why" box and a short chat that can open when you delete the App or manage your subscription. What you type is sent to our backend with your device identifier and some facts about your use of the App (for example your plan, how many items are in your collection and their total value, how many scans you have made, and how long you have used the App). Chat messages are answered by AI (Google Gemini, or our backup route through OpenRouter, Section 6). Your messages are posted to a private Telegram channel, kept on our server, recorded in our usage logs and, on iPhone, in Appdeck. We do not require you to contact us, and you control what you include.

• Purpose: to respond to your questions, support requests, and rights requests, and to understand why people leave or cancel.
• Legal basis (GDPR): legitimate interests (Article 6(1)(f)) in providing support and improving Buck, and compliance with a legal obligation (Article 6(1)(c)) when handling a data rights request.

3.7 Device identifier, App Attest, and Play Integrity

On first launch the App creates a random device identifier and stores it on your device. It is a random value. It is not your name, email address, phone number, Apple Account or Google Account, or your device's advertising identifier (IDFA on iPhone, advertising ID on Android), and it is not shared with advertisers, data brokers, or any other company for their own purposes, with one exception: on iPhone, if you allow tracking, a hashed copy of it is sent to TikTok for advertising measurement (Section 3.10). The hashed copy cannot be turned back into the identifier, but it still lets TikTok recognise your device. The identifier is the key that joins the usage logs (Section 3.4), the subscription records held by RevenueCat (Section 3.5), your scan photos in our logs (Section 5), your community finds (Section 3.8), your leaderboard row and invites (Section 3.11), and the experiments we run through Appdeck, so that we can support you, honour your subscription, and answer a deletion request. Because it persists on your device and joins those records together, we treat it as personal data and describe it as such throughout this policy.

On iPhone the identifier is also kept in your device's keychain, so it stays the same if you delete and reinstall the App, and it moves to a new iPhone restored from an encrypted backup; if you allowed tracking, TikTok then receives the same hashed copy again. On Android it is kept in the App's storage: deleting the App removes it, but Android's backup or device transfer can restore it. To stop its hashed copy from reaching TikTok, turn off tracking for Buck (Section 3.10). To have it and the data linked to it deleted, write to privacy@getbuckapp.com (Section 11).

Buck also uses Apple App Attest (part of Apple's DeviceCheck framework) on iPhone and Google Play Integrity on Android to confirm that a request to our backend comes from a genuine, unmodified copy of the App. App Attest produces a cryptographic assertion generated by Apple hardware; Play Integrity asks Google Play to vouch for the App and the device. Neither identifies you by name, and both are used only to protect our backend from abuse and to count friend invites only from genuine installs (Section 3.11).

• Purpose: to operate and support the Service, honour subscriptions, and prevent abuse of our backend.
• Legal basis (GDPR): performance of a contract (Article 6(1)(b)) for subscription entitlement, and legitimate interests (Article 6(1)(f)) in operating and securing the Service.

3.8 Community finds feed

Buck includes a community finds feed showing coins and banknotes that other people have identified. Each time a scan identifies an item, the App automatically submits it to our backend: the cropped photo of the coin or banknote (a small image), its name, the estimated value shown, a display name the App generates for your device (not your profile name), and your device identifier. Our backend adds your approximate city and country, derived from the IP address of the request, and stores a scrambled token in place of your device identifier. The entry is then shown to other Buck users inside the App, and the cropped photo is served from a public web address that is not guessable but is not password-protected either.

This means the photo you scan can be seen by other people. There is no setting in the App to turn this off. Only scan items you are happy to make public, and keep faces, documents, addresses, screens, and anything else private out of the frame. The feed keeps the latest 500 finds from everyone; older finds and their photos are deleted. You can ask us to delete anything you have shared by writing to privacy@getbuckapp.com. We do not attach your name to a shared find, because we do not have it.

• Purpose: to show Buck users a community feed of real finds.
• Legal basis (GDPR): legitimate interests (Article 6(1)(f)) in running the community feed.

3.9 Screenshots you take inside the App (iPhone)

On iPhone, whenever you take a screenshot while Buck is open, the App renders a picture of the Buck screen you were looking at and sends it to our backend, which posts it to our private Telegram log channel (Section 3.4) together with your device model, iOS version, App version, and your approximate city and country derived from your IP address. A copy also goes to Appdeck. This helps us see exactly what a confusing or broken screen looked like. It captures only Buck's own interface, never other apps and never your photo library, and it is not kept in our scan archive. There is no setting in the App to turn this off. The Android app does not do this.

• Purpose: to diagnose visual and layout problems.
• Legal basis (GDPR): legitimate interests (Article 6(1)(f)) in finding and fixing problems in the App.

3.10 Advertising measurement (TikTok)

We advertise Buck on TikTok. To learn which of our ads lead people to install Buck and subscribe, the App includes the TikTok Business SDK, a software development kit made by TikTok. TikTok also uses these results to show our ads to people who are more likely to be interested in Buck.

The data the SDK collects is received by TikTok. For users in the European Economic Area, the United Kingdom, and Switzerland, that is TikTok Technology Limited (Ireland) and TikTok Information Technologies UK Limited (United Kingdom), which TikTok's privacy policy names as the controllers for those regions; for users elsewhere, it is the TikTok company named in TikTok's privacy policy for their region (together, "TikTok"). TikTok's privacy policy says that it processes certain information it receives from partners that integrate its advertiser tools as a joint controller with them. For collecting this data in the App and sending it to TikTok, we and TikTok are joint controllers; TikTok alone decides how it uses the data once received. Our part: we chose to include the SDK, we decide which events the App sends, and we tell you about it in this policy. TikTok's part: everything it does with the data afterwards, as described in TikTok's privacy policy. You can exercise your rights with either of us. TikTok may also link this data to your TikTok account, if you have one, and, if you agreed to this on TikTok, use it to personalise the ads you see on TikTok.

Through the SDK, the App reports these events to TikTok:

• that the App was installed, that it was opened, and that it was opened again on the day after installation;
• that you completed the first-run setup (onboarding);
• that the subscription screen was shown, and from which part of the App;
• that you started a purchase or a free trial, with the product (no price);
• that you completed a purchase, with the product, its price, and the currency.

With these events the SDK sends technical information about your device and connection: device model, screen size, operating system version, App version and build, language and region settings, IP address, your device's browser identification string (user agent), the time of each event and of your App sessions, a random identifier that the SDK creates, and diagnostics about the SDK itself (for example how long its requests take). On Android it also sends the app store that installed Buck, your network type, the time your device was last restarted, and reports of crashes caused by the SDK. In addition:

• On iPhone: Apple's identifier for vendor (IDFV), which only apps from the same developer can read on your device, and whether you allowed tracking. Only if you allow tracking in Apple's App Tracking Transparency prompt, the SDK also sends your advertising identifier (IDFA) and a hashed copy of Buck's device identifier (Section 3.7). Buck may show this prompt once, during the first-run setup. If you are not asked, or you choose "Ask App Not to Track", neither is sent. The SDK also uses Apple's SKAdNetwork, through which Apple tells TikTok whether one of our ads led to an install or a purchase, and roughly how much was spent, without identifying you or your device. We have switched off TikTok's predictive measurement for Buck's iPhone app: if you do not allow tracking, TikTok does not use your device information to attribute our ads to you, and our ads are measured only through SKAdNetwork.
• On Android: your advertising ID from Google Play services (unless you have deleted it) and the Google Play install referrer, which records the link or ad, if any, that led to the install, and when you clicked it and installed the App. Buck itself never reads your advertising ID: the SDK sends it to TikTok only to measure and improve our ads, and we do not connect it to persistent device identifiers or to information that identifies you by name. The Android app does not send Buck's device identifier to TikTok.

Your photos, scans, scan results, collection, community finds, and messages are never sent to TikTok, and Buck switches off the SDK's optional features that could capture screenshots, record what you tap, or log purchases automatically. TikTok handles the data it receives under its own terms and privacy policy.

• Purpose: to measure and optimize our own advertising on TikTok.
• Legal basis (GDPR): on iPhone, consent (Article 6(1)(a)), given through Apple's App Tracking Transparency prompt, for your advertising identifier and the hashed device identifier; legitimate interests (Article 6(1)(f)) in measuring and improving our own advertising for everything else described in this section.
• Your choices: on iPhone, go to Settings > Privacy & Security > Tracking and turn tracking off for Buck or for all apps: your advertising identifier and the hashed device identifier are then no longer sent, at the latest from the next time Buck starts. On Android, go to Settings > Privacy > Ads (on some devices, Settings > Google > Ads): deleting your advertising ID stops it from being sent, although the SDK may still send its stored copy for the rest of that session and during the next one, while resetting it replaces it with a new one. The App has no setting that turns the SDK off: with tracking off or the advertising ID deleted, the App still reports the events listed above, with the IDFV on iPhone and the SDK's random identifier. Uninstalling the App stops all of it. For the data TikTok already holds, see Section 8.

3.11 Leaderboard and friend invites

Buck has a collectors' leaderboard. Whenever your collection changes, the App sends our backend, with your device identifier: the name on your profile ("Buck Collector" unless you change it), the number of items in your collection, their estimated total value, your most valuable coin, the avatar you picked, whether you have Pro, and your country (the one you pick on your profile, otherwise your App Store country or device region, otherwise the country of your IP address). Our backend also keeps how much your collection grew each day, for the daily and weekly rankings. Other Buck users see your profile name, avatar, item count, total value, most valuable coin, Pro badge, and country on the leaderboard. Devices that have never sent their own figures may appear under an anonymous name (for example "Collector 1F2A"), with figures taken from our usage logs. There is no setting in the App to leave the leaderboard; you can ask us to remove your row (Section 11).

When you invite a friend, the App shares a message with your personal code and invite link. When someone opens the link, our backend records the code, a scrambled form of their IP address, the platform, and the time, for 24 hours, so that the install can be matched to the invite; on Android the code also travels through the Google Play install referrer. A successful invite, or a code typed in by hand, makes you friends in the App, so you see each other on the friends leaderboard, and enough successful invites can earn the inviter free Pro time, granted through RevenueCat.

• Purpose: to run the leaderboard and friend invites.
• Legal basis (GDPR): legitimate interests (Article 6(1)(f)) in running these features, and performance of a contract (Article 6(1)(b)) for invite rewards.

4. What we do not collect

To be clear, Buck does not:

• require an account, username, password, or social login;
• ask for your name, postal address, date of birth, or government ID;
• access your contacts, microphone, calendar, health data, or precise location;
• use GPS or your device's location services (where we use a location, it is the approximate city or country derived from your IP address, or a country taken from your device settings or your profile);
• include any advertising SDK other than the TikTok Business SDK (Section 3.10), or any third-party analytics SDK;
• use your iPhone's advertising identifier (IDFA) unless you allow tracking in Apple's App Tracking Transparency prompt;
• sell or rent your personal data to anyone.

5. How your images are processed

This is the most important section, so we describe it step by step.

1. You capture a photo with the camera or pick one from your library.
2. The App sends the image to our recognition backend over an encrypted (HTTPS) connection. The image is transmitted so it can be identified.
3. Our recognition backend forwards the image to Google Gemini, an AI service we use as a sub-processor, using a server-side key. If Google's service is slow or unavailable, the backend can send the same request through OpenRouter, a service that passes it to an AI model (normally Google's Gemini) under a setting that excludes providers that keep or train on the data. Your device never holds or sends these keys, and the App does not talk to Google or OpenRouter directly.
4. The AI service returns identification details about the item, such as country, denomination, year, mint mark, variety, name, and a confidence indicator. Buck uses only the identity. Any value or grade produced by the AI model is discarded; Buck does not rely on the AI for value.
5. The App displays the result to you.

Copies of your scan photos. The identification step itself keeps no image: our backend does not store the image it forwards for identification, and it keeps only a record of the result (what the item was, with a technical key from App Attest or your IP address). Separately, the App uploads a copy of every photo it scans, whether or not the item was identified (both sides when you flip a coin), to our private quality logs, so we can monitor and improve recognition:

• our scan archive on our server in Germany, with your device identifier, the result, the value shown, the App version, your device model, and your approximate city and country (from your IP address). It holds about 3 GB of photos and deletes the oldest first. It has no web address, and only we can read it;
• our private Telegram channel, with the result, the value shown, your device model, the App version, and your approximate city and country, where photos stay until we delete them;
• on iPhone, Appdeck (Section 6).

There is no setting in the App to turn this off. These logs are never used for advertising, and you can ask us to delete your photos at any time by writing to privacy@getbuckapp.com. When a scan identifies an item, its cropped photo is also shared in the community feed (Section 3.8). When a scan is confirmed, the App may also send our backend a numeric fingerprint of the coin image (not the photo itself), with the coin's catalog number and your device identifier, to improve on-device recognition for everyone.

Estimated value. Buck's value figures are estimates intended to help hobbyists, not a professional appraisal, an authentication, a grading, or financial or investment advice. Actual value depends on condition, grade, authenticity, demand, and the specific buyer. The value pipeline that draws on real market sales data is being rolled out; until it is fully live for a given item, the App will tell you honestly that a value is being checked or is not yet available rather than present a made-up figure.

6. Third parties and sub-processors

Buck shares data with a small set of service providers who act on our instructions, and with TikTok for advertising measurement (Section 3.10), which handles that data under its own terms. Other Buck users also see what the community feed and the leaderboard show (Sections 3.8 and 3.11). We do not sell your data to any of them or to anyone else.

About the AI sub-processors. Your photos are shared with a third-party artificial intelligence service, Google Gemini (and, when our backup route is used, OpenRouter), in order to identify what is in them. The App does not ask for a separate permission before a photo is sent: choosing to scan a photo sends it. Google processes the image as our sub-processor solely to return an identification result. We do not permit your images to be used to target advertising to you. Google's handling of data submitted through its AI services is governed by Google's own terms and privacy documentation.

About the community feed. Every scan that identifies an item is also published to other Buck users through the in-app community feed, and its cropped photo is served from a public web address (Section 3.8). This is separate from, and additional to, the AI identification step above, and there is no setting in the App to turn it off.

7. How we share data (and how we do not)

• We do not sell your personal data. We have not sold and do not sell personal data. Sending the app events and identifiers described in Section 3.10 to TikTok to measure and optimize our ads may count as "sharing" for cross-context behavioral advertising as that term is defined under California law. Device settings remove the advertising identifiers only: the App still reports the events in Section 3.10 and has no switch to stop them. Uninstalling the App stops all of it.
• Advertising networks and data brokers. Apart from TikTok, as described in Section 3.10, and the Apple Ads attribution described in Section 3.5, we do not disclose your data to advertising networks, and we never disclose it to data brokers.
• Service providers, and TikTok. We disclose data only to the companies listed in Section 6: to our service providers only to operate, improve, and test the Service and only under terms that require them to protect it, and to TikTok only for the advertising measurement described in Section 3.10. TikTok receives this data under its business terms for advertisers and handles it as described in its privacy policy, which says it protects information with appropriate technical, administrative, and physical security measures.
• Other Buck users. The community feed and the leaderboard show other Buck users what is described in Sections 3.8 and 3.11.
• Legal and safety. We may disclose information if required by law, legal process, or a valid government request, or where necessary to protect the rights, safety, security, or property of Buck, our users, or the public.
• Business transfers. If Buck is involved in a merger, acquisition, financing, or sale of assets, information may be transferred as part of that transaction, subject to this policy.

8. Data retention

• Scan photos: the identification step keeps no image. Copies in our scan archive are kept until the archive reaches its size limit (about 3 GB) and the oldest are deleted; copies in our private Telegram channel are kept until we delete them; copies in Appdeck (iPhone) are kept no longer than needed to monitor recognition. We delete them on request at any time. See Section 6 regarding the AI sub-processors' own handling.
• Community finds: deleted, with their photos, once 500 newer finds have arrived, or earlier on request.
• Screenshots (iPhone): kept in our private Telegram channel until we delete them, and in Appdeck; never in our scan archive. Deleted on request.
• Usage logs: app event logs, crash reports, and the device identifier are kept only as long as needed to operate and improve the Service, and are deleted or anonymized on request.
• Leaderboard and invites: your leaderboard row and your invite and friend records are kept until you ask us to delete them; invite link records are kept for 24 hours.
• On-device data (your collection and preferences): kept on your device until you delete it within the App or delete the App. We do not hold a copy, apart from the leaderboard totals in Section 3.11.
• Technical and security logs: any request metadata used for security and rate limiting is kept only for as long as needed for those purposes and then deleted or aggregated.
• Messages: support emails are kept for as long as needed to handle your request and to keep a reasonable record of support history, then deleted. Messages you type in the App are kept in our private Telegram channel and on our server until we delete them, and are deleted on request.
• Subscription status: RevenueCat keeps your subscription records while they are needed to provide the subscription, and purchase records are kept as needed to meet legal, tax, and accounting obligations.
• Advertising measurement data: TikTok keeps what it receives through the SDK (Section 3.10) as described in its privacy policy; we cannot see or delete TikTok's individual records. To ask for access to or deletion of that data, use TikTok's privacy request form, or write to privacy@getbuckapp.com and we will pass your request on to TikTok.

9. Security

We protect data with measures appropriate to its sensitivity, including:

• encrypted transport: communication between the App and our backend, and between the App and our providers, uses HTTPS;
• server-side AI keys that are never shipped in the App, so they cannot be extracted from your device;
• no web address for the scan photos stored on our server, and access-restricted logs, so only we can read them (community feed photos are public by design, Section 3.8);
• App Attest, Play Integrity, rate limiting, and abuse prevention to protect the Service.

No method of transmission or storage is completely secure, so we cannot guarantee absolute security, but we work to protect your information.

10. Children's privacy

Buck is rated for general audiences (Apple age rating 4+, PEGI 3 on Google Play) and contains age-appropriate content about coins, banknotes, and collecting. The App is not directed to children, and we do not knowingly collect personal data from children under 13, or under the minimum age of digital consent in your country (which can be up to 16 in parts of the EEA). If you believe a child has provided us personal data, contact us at privacy@getbuckapp.com and we will delete it.

11. Your rights

Depending on where you live, you may have some or all of the following rights:

• Access: ask what personal data we hold about you.
• Correction: ask us to correct inaccurate data.
• Deletion: ask us to delete your personal data ("right to be forgotten").
• Portability: ask for a copy of data you provided in a portable format.
• Restriction and objection: ask us to limit or stop certain processing, including processing based on legitimate interests. Some processing happens in the App without a setting to switch it off (the advertising measurement in Section 3.10, the community feed, the leaderboard, and the logging of scan photos and screenshots): for these, we can delete what we hold on request, but we cannot stop the App from sending new data while it is installed. Uninstalling the App stops it.
• Withdraw consent: where we rely on consent (the iPhone tracking permission in Section 3.10), you can withdraw it at any time in Settings > Privacy & Security > Tracking.
• Opt out of sale or sharing (California): we do not sell personal data. For the sharing with TikTok described in Section 7, the ways to limit or stop it are the device settings in Section 3.10 and uninstalling the App.
• Non-discrimination (California): you will not be treated differently for exercising your privacy rights, and the value of the Service to you will not change because you exercised them.

Because Buck has no account and does not build an advertising profile of you, there is no account profile for us to retrieve, and your collection itself lives in the App on your phone, under your direct control. What we hold on our side is linked to your device identifier (Section 3.7): usage logs, scan photos, community finds, your leaderboard row and invites, and any messages you sent us.

How to exercise your rights and delete your data

• Local data: to delete your collection and app data, delete it within the App where the option is provided, or delete the App from your device. This removes the data stored locally on your phone, except the device identifier (Section 3.7).
• Server-side and support requests: to make any access, deletion, or other rights request, email privacy@getbuckapp.com. To help us find your data, include your friend code (shown in the "Add a friend" box in the Friends part of the leaderboard) or, if you subscribed, your App Store or Google Play order number. We will respond within the time required by applicable law (for example, generally within one month under the GDPR). We may need to verify your request, for example by asking you to confirm it from the same email address you used to contact us.
• Subscription: if you subscribe, you manage and cancel your subscription through your Apple Account in iOS Settings or the App Store, or through Google Play on Android. To request deletion of any subscription record we may hold, contact privacy@getbuckapp.com.
• Device identifier: the App has no in-app way to delete the data linked to it. Write to privacy@getbuckapp.com and we will delete the data we can link to it, on our server and with our providers.
• Data held by TikTok: use TikTok's privacy request form, or write to us and we will pass your request on to TikTok (Section 8).

If we ever introduce an account, we will also provide an in-app way to delete that account and its associated data directly from within the App, as Apple requires.

12. International data transfers

The controller of the iPhone app is based in Italy and the controller of the Android app in the Netherlands. Our backend runs on servers in Germany. Some of our providers (including Google, Apple, OpenRouter, RevenueCat, Telegram, and Railway, which hosts Appdeck) and TikTok (Section 3.10) may process data in the United States and other countries; TikTok's privacy policy says it stores the information it holds on servers in the United States, Malaysia, and Singapore. If you are in the EEA, the UK, or Switzerland, this means your information may be transferred outside your home region to countries that may not provide the same level of data protection.

Where we make such transfers, we rely on appropriate safeguards required by law, such as the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, and, where applicable, providers' approved data transfer frameworks. TikTok transfers the data it receives under its own safeguards, including standard contractual clauses, as described in its privacy policy. You can contact us at privacy@getbuckapp.com for more information about these safeguards.

13. Cookies and our website

The Buck App does not use cookies. If our website at getbuckapp.com uses cookies or similar technologies (for example, for basic site functionality or aggregate visit statistics), that use will be described on the website itself. This policy covers the App and the recognition Service.

14. Changes to this policy

We may update this Privacy Policy from time to time, for example when we add a feature that changes what the App sends, or when we add a new provider. When we make a material change, we will update the "Effective date" at the top and, where appropriate, notify you within the App. Your continued use of Buck after an update means you accept the revised policy.

15. Contact us

Questions, requests, or concerns about your privacy:

• Privacy: privacy@getbuckapp.com
• General support: support@getbuckapp.com
• Data controller: Emanuele Pio Totaro, Italy (Buck for iPhone); EXO, the Netherlands (Buck for Android)

We will do our best to resolve any concern you raise. If you are in the EEA or the UK and are not satisfied with our response, you may lodge a complaint with your local data protection supervisory authority.