Back to Cronod

Privacy policy

Cronod keeps your private timepiece collection on your device. This policy explains what stays there, what is sent when you use online features, and how to manage your information in the app and website.

Your private collection

Watch details, serial numbers, costs, receipts, service records, accuracy readings, stories, straps and original attachments are stored locally. Core collection features work without an account or internet connection. Signing in does not upload or synchronize the collection. The local database relies on private app storage and device protection; Cronod does not separately encrypt it.

Backups and on-device tools

You choose when to export a passphrase-protected encrypted backup and where to save it. It can include photos and documents. Cronod does not receive the file or save the passphrase, and cannot recover a lost passphrase. Restore replaces local records after confirmation. Device backups and storage providers you choose have their own settings and policies. There is no automatic Cronod cloud backup or full collection sync. Dial-photo processing and strap previews run on device. Acoustic analysis uses microphone audio in temporary memory; audio is not saved or uploaded.

Optional Cronod accounts

The backend stores your name, email address, account identifier, sign-in provider, verification status and session records to authenticate you and manage publications, votes and reports. Email/password accounts store a salted password hash, never a readable password. When enabled, Google sign-in supplies identity information and a provider identifier to verify your account; Cronod does not receive your Google password. Mobile session credentials use platform secure storage. An account does not give the website access to your private collection.

What you choose to publish

Sharing sends the reviewed page title, description, optional collector name, selected watch details, authored stories and selected photo copies to the backend. Private pages are restricted to the owner; unlisted pages can be viewed by anyone with the link; public pages can appear in browsing and search. Sale listings separately publish approved watch information, asking prices, selected photos and the public seller name and contact details you enter. Public collection snapshots exclude private serials, costs, receipts and ownership history. Public photo copies are re-encoded to remove source metadata; originals remain on device. New watches are never enrolled automatically. Shared collection snapshots change only when you publish again. After you enroll a sale listing, approved public fields synchronize while the app is open and online; newly added photos still require selection. Pending listing changes are stored separately by account and retried when connected. Other people and search engines may retain copies outside Cronod’s control.

Votes, reports and discovery

Votes and reports store your account identifier, the page, time and vote or report reason for voting limits, rankings and moderation. Voter and reporter identities are not included in public responses. Rankings use public pages. Trending uses aggregate public Wikipedia page-view data fetched by the backend; the app does not send your collection or browsing history to Wikipedia.

Device permissions

Camera and photo access support images you choose to add or analyze. Microphone access supports experimental acoustic analysis and optional voice search. On supported iOS devices, voice search also requests speech-recognition permission and requires on-device recognition; its audio is not sent to Cronod or a remote speech service. Recognized words become search text and may be sent to the backend when you search public content. Notifications enable local care reminders. You can decline or revoke permissions in device settings and still save ordinary records. Cronod does not need your contacts or precise device location. Seller locations are text entered by the seller.

Website sessions and preferences

Google and Cronod email/password sign-in use the same backend accounts as the mobile app. The website keeps your backend session in an encrypted HttpOnly cookie for up to eight hours and verifies it on protected requests. Better Auth handles the Google redirect with encrypted OAuth cookies; its website cookie alone does not grant account access. Accounts are never automatically linked by matching email. Signing out revokes the current backend session and clears this browser’s login cookies. Language may be saved in a cookie and appearance in browser storage. Clearing browser data removes those preferences. Cronod does not integrate advertising trackers or behavioral analytics.

Providers and online requests

Online requests send information needed to serve and secure the connection, such as IP address, requested URL, browser/device information and timestamps, to hosting and network services. Cronod uses its backend for accounts and shared content, and Amazon Web Services for hosting and, where enabled, listing photo storage and delivery. Google processes identity information when you choose its sign-in option. Providers may process information outside your country under their service and privacy terms. Cronod uses information to operate and protect the service, not to sell personal information or target advertising. Email providers process support messages and attachments you choose to send.

Retention and deletion

Local records remain until you delete them, replace them by restoring a backup, or remove the app’s local data. Exported backups remain where you saved them. Account deletion removes the account and makes its publications unavailable; background cleanup retries removal of remaining publication data and photos. Copies held by other people or search engines may persist. Scheduled cleanup removes vote ballots older than three months and ballots from deleted accounts. Reports remain while their referenced page exists. Historical ranking records may retain internal account/page identifiers; contact us about remaining account-linked records. Technical logs and support correspondence may be retained for troubleshooting and handling requests. Ask us about information relating to you.

Your choices and requests

You can edit or delete local records, export backups, make shared pages Private, withdraw sale listings, revoke permissions and sign out. Online publication changes require a successful connection. To delete a backend account, use Settings → Account → Account options → Delete account in the mobile app and reauthenticate. This does not erase your local collection, exported backups or Google account. Contact us to request access, correction or deletion of information held by the service. We may need to verify that the request is yours. Never include passwords, backup passphrases or private collection files in an initial request.

Account deletion instructions

Children

Cronod is designed for timepiece owners and collectors and is not directed at children. If you believe a child has provided personal information through an online feature, contact us so we can investigate and address the request.

Policy changes

We update this page when data handling changes and show the revision date above. Planned features, including full collection sync and cloud passports, are not enabled by this policy. Additional permissions or publication choices must be presented when a feature needs them.

Contact and privacy questions

Contact Cronod at the address below for privacy questions, personal-data requests or account-deletion help. Describe the request and relevant account without sending passwords or private watch documents.

cronodofficial@gmail.com

Visit Cronod support