Stonescout Privacy Policy

Version of 2 October 2026. First prepared 21 September 2026.

Controller/provider: Gürsel Pekgöz. Business/service address: Acıbadem Mah., Acıbadem Cad., Faikbeymescidi Sok., No: 8, 34718 Kadıköy, İstanbul, Türkiye. Privacy contact: pekgoz25gursel@gmail.com. Effective date: the date this version is first published in the app or on the Stonescout support site (version of 2 October 2026).

Information and purposes

InformationHandling in the inspected buildPurpose
Camera or selected photographsImage preparation on the device; collection files/database stored locally. The deployed closed-test analysis service accepts supported, verified signed-in accounts and sends a resized JPEG through Stonescout's authenticated server to OpenAI only after per-photo confirmation.Experimental visual identification and collection display
Collection, favorites and preferencesLocal SQLite/files on native devices and local app storage; web uses browser storageRemember your finds and settings
Sign-in identityFirebase Authentication processes Apple/Google provider identity, account UID and available email, including an Apple private relay email where supplied. Updated app source also supports email/password registration, email verification and password reset; this interface is not present in every existing TestFlight build. Email/password credentials are submitted to Firebase Authentication. Stonescout does not receive your Apple/Google provider password or intentionally log email/password credentials.Sign in and recover the account-linked wallet
Credit balance and transaction referencesNative TestFlight wallet is read from the authenticated Firebase/Firestore service in Frankfurt. Server ledger and purchase-period records support duplicate prevention and refund adjustments. Local demo storage is not the native production wallet. Closed-test reports use server-authorized SANDBOX balances; public paid report delivery and the final native report interface are not yet released.Track and recover purchased/included credits without device-controlled grants
AI reference reportsClosed-test delivery stores tentative specimen identity, generated report text and delivery/access receipts in the account-linked Frankfurt database. The text-only OpenAI estimate request receives the tentative geological name, not the photograph or account identity.Deliver educational USD reference estimates and reopen the same delivered report without another debit
Purchase/subscription informationRevenueCat and the relevant app store process purchase records and subscription status. When signed in, RevenueCat customer identity is linked to the Firebase account UID; this is not anonymous to the service.Validate purchases, restore eligible purchases and enable Pro; RevenueCat dashboard reporting
Support correspondenceInformation you choose to send to the Gmail contact above; ordinary closed support correspondence has a working manual deletion period of 30 days after closure, with documented dispute/legal exceptions assessed separately. No automated mailbox purge is implemented.Respond to requests
Account-deletion requests and notificationsThe deployed request intake requires recent supported-account reauthentication (Apple, Google, or verified email/password) and records request timing and the completion deadline; Apple revocation proof is encrypted where applicable. Cleanup uses an operator workflow, not immediate automatic deletion. It keeps scoped operation evidence and a temporarily encrypted notification recipient, removed on verified completion. A purchase-free email-account test verified Firebase/wallet cleanup and Gmail completion delivery; Apple revocation and deletion of an existing RevenueCat customer remain unverified.Receive deletion requests and evidence separately verified completion without claiming immediate or universal erasure

“Anonymous” SDK identifiers do not mean that no data is processed. Stonescout does not receive your full payment-card details through the inspected purchase integration. Stores handle payment under their own terms and privacy notices.

Permissions and sharing

Camera and photo permissions support the feature you request. Photo-library saving and external sharing are user-initiated. If you share a card, the destination app or recipient receives it under its own practices. Operating-system backups and photo synchronization may also copy files; we do not promise that every photo always remains exclusively on one device.

Notification permission supports local reminders. The inspected code does not request a remote push token. The location preference currently does not implement GPS collection. No separate advertising or third-party analytics integration was found in the inspected application code; this does not exclude purchase reporting by RevenueCat or independent store processing.

You can manage permissions in device settings. Revoking a permission can prevent the associated feature but does not cancel purchases or erase previously shared copies.

Recipients and international processing

OpenAI closed-test identification (implementation update: 2 October 2026)

Closed-test processing requires a supported sign-in with a verified email, not membership in a private operator email list. Before each upload, the app asks whether to send the selected photo to Stonescout and OpenAI. Canceling does not upload the photo. Avoid photographs containing people, documents or personal information. Visual suggestions can cover rocks, minerals and gemstones outside our six detailed catalog entries. Such results are tentative names without verified catalog properties or valuation. No result is certified identification, authenticity verification or valuation.

The Stonescout analysis handler is configured for Frankfurt and does not intentionally persist or log photos or model responses. It stores per-account request counts and a global pilot count for cost control; the authenticated account identifier is not sent to OpenAI. The OpenAI request uses store: false; this does not guarantee zero retention. OpenAI's standard API abuse-monitoring logs may retain content for up to 30 days, with legal and safety exceptions; account-specific zero-retention controls have not been verified. Processing by OpenAI is not represented as Frankfurt-only or EU-only. See https://developers.openai.com/api/docs/guides/your-data for provider controls (checked 1 October 2026). Retention of pilot counters, transfer safeguards and the final release privacy disclosures still require completion before public launch.

Roboflow credentials have been provisioned separately, but this analysis path does not send photos to Roboflow or use it as an automatic fallback.

Account and wallet processing involves Google Firebase Authentication and the Frankfurt Firestore/Cloud Functions service. This region setting is not a claim that all Google identity, support, logging or provider processing occurs exclusively in Frankfurt. Purchase processing involves RevenueCat and Apple or Google Play; sandbox purchase tests have run on both platforms. External sharing recipients are chosen by you. Release-build recipients, checked against the app's dependencies on 2 October 2026: Google Firebase (Authentication, Firestore and Cloud Functions; Stonescout's database and functions are configured in europe-west3, Frankfurt), Google Sign-In and Sign in with Apple when you choose them, OpenAI (photo analysis only after per-photo confirmation, and text-only estimate requests), RevenueCat (purchase and subscription status) and Apple App Store or Google Play (payments and store records). The app contains no advertising, attribution or third-party analytics SDK. Each provider processes connection metadata such as IP address and device/app version as part of delivering its service, and may use its own subprocessors under its published terms.

The controller is based in Türkiye. Legal bases by purpose, where the law requires one:

Processing countries: the providers above may process data in the United States, the European Union and other countries where they or their subprocessors operate. For transfers out of the EEA or UK, Stonescout relies on the safeguards in each provider's data processing terms, such as standard contractual clauses or an adequacy decision where available. For transfers from Türkiye, the Turkish-language KVKK notice in the app describes the transfer basis under KVKK Article 9.

Retention, deletion and security

Report retention decision approved on 2 October 2026: account-linked report text, tentative specimen identity and delivery/access history are retained while the account exists and removed through the account-deletion process. Signing out does not delete them. Purchase records and records subject to a documented statutory retention obligation are assessed separately; this exception is not permission to retain report content indefinitely. A rights-verified catalog-photo analysis-to-report delivery and free reopening were verified through the deployed endpoints. This does not prove native camera/report interaction, deletion of delivered reports or public release readiness.

Collection data remains in app storage until deleted or otherwise removed. In the current build, Settings “Clear data” clears collection entries and app-managed collection photos; it does not clear all preferences, credit records or RevenueCat/store records. Copies exported to Photos, sent to others or stored in system backups are controlled separately. Removing the app does not cancel a subscription and is not a request to erase store records.

Retention periods:

Technical snapshot on 1 October 2026: the named Frankfurt wallet database had no scheduled backups or listed regional backup copies, and point-in-time recovery was disabled. This does not promise immediate physical erasure, exclude short-lived database recovery/version data, or cover all Google/provider infrastructure and device backups. The inspected Cloud Logging default bucket was configured for 30-day retention; other log/audit buckets and provider records require separate review. These observations are not a completed backup-deletion policy.

Sign-out does not delete the Firebase account, wallet ledger, purchase records or analysis counters. The in-app deletion-request service with a 30-day completion deadline has been deployed. On 1 October 2026 an authorized, isolated, purchase-free email-account test verified authenticated intake, Firebase account and wallet removal, completion delivery to an operator-owned Gmail alias and removal of the temporary encrypted recipient. This is not proof of Apple authorization revocation, deletion of an existing RevenueCat customer, paid-account handling, native deletion UX or erasure of all provider backups. These remaining cases require verification before store submission. Account deletion does not cancel an app-store subscription. The process must remove associated data except records with a documented legal retention obligation, revoke Apple authorization where applicable and confirm actual completion; a request receipt is not proof of completed deletion.

The app relies on device/app storage protections and provider safeguards. Do not treat local storage as a guarantee against device compromise. Data sent between the app and Stonescout's services travels over HTTPS (TLS). Server-side access uses separate least-privilege service accounts for each live function, and service credentials are held in Google Secret Manager rather than in the app. Stonescout does not claim independent security certification. If a personal data breach occurs, Stonescout will assess it promptly and notify the competent authority and affected users where the law requires (for example within 72 hours under KVKK and the GDPR).

Your rights and children

Depending on your location, you may have rights to access, correct, delete, restrict, object to processing or receive portable data, and to withdraw consent where consent is used. Contact the privacy address above; we may need proportionate information to verify and locate your records. You may complain to your competent data-protection authority. These rights may be subject to lawful exceptions.

The intended audience selected by the operator is ages 13 and above; children under 13 are not targeted. A store age rating is not proof of age verification, legal capacity or valid consent in every country. Requests are answered within 30 days (one month under the GDPR, 30 days under KVKK), extended only where the law allows. Competent authorities include the Turkish Personal Data Protection Authority (KVKK, kvkk.gov.tr), your local EEA supervisory authority, and the UK Information Commissioner's Office (ico.org.uk). Where local law sets a higher age for consenting to online services (up to 16 in some EEA countries), users below that age need a parent's or guardian's authorization. The Regional Privacy Supplement adds US state and Canadian information.

We will update this policy when practices change and provide notices or obtain consent where required. Review date and effective date will identify the applicable version.