Temzen · Updated 15 October 2026
GTO Solutions AS, Fredrik Meltzers gate 13B, 5007 Bergen, Norway, is responsible for personal data processed through Temzen. Contact support@gtopostflop.com.
Your watch collection, purchase information, valuations, service records, wear history, preferences, photos and documents are stored locally. Serial numbers and attached documents are not included in the app’s Firebase collection backup. Device backups and files you explicitly export or share are governed by the services you choose. If you allow notifications when starting a free trial, the reminder before it ends is scheduled on your device.
The app creates a pseudonymous Firebase Authentication identifier when it connects, even if you do not link an account. This supports access to online services. If you connect Google or Apple, Firebase processes your provider identifier and any name and email the provider supplies. Apple may provide a private relay email.
If you enable cloud backup, watch details, purchase information, notes, valuation and service records, and watch photos may be copied to Firebase under your account identifier. Local-only documents and serial numbers are excluded. Backup depends on connectivity; it is not a guarantee of recovery or continuous synchronization.
If you create a public profile, your chosen handle, display name, biography, optional location text and selected collection information may be publicly visible, including through a shareable web profile. Posts may include the watch, caption, optional location text, photo and wear statistics you choose to share. Purchase prices and serial numbers are not part of the public collection. Following relationships and reactions support community features. Reports and block lists are used for safety and moderation.
Share only information and photos you have the right to publish. Other people may copy public content. Deleting it from Temzen cannot remove copies others have already made.
We use Google Firebase Authentication, Realtime Database, Storage, Hosting and Cloud Functions to operate the app. These services process identifiers and technical request data needed for delivery, security and troubleshooting, which may include IP addresses. Requests for catalogue images or other external content also reach the relevant hosting provider. Opening an external news article or link is subject to that site’s privacy policy.
See Firebase privacy and security and Google’s privacy policy. Service processing may take place outside your country, including outside the EEA, under the provider’s applicable data transfer safeguards.
Temzen Private is bought through Apple’s App Store or Google Play, which handle payment; we never see your payment details. We use RevenueCat to confirm which subscription you have and to restore it on a new device. RevenueCat receives your Firebase account identifier, your purchases and their store receipts, and your store country and currency. See RevenueCat’s privacy policy.
We use Meta’s (Facebook’s) SDK to measure our own advertising, as described under Advertising and tracking. See Meta’s privacy policy.
We process the data needed to provide the features you request, including your optional account, backup and public sharing. We rely on performance of our service agreement for these functions, legitimate interests for proportionate security and abuse prevention, and legal obligations where applicable. We process purchase data to perform the subscription you buy. Advertising measurement relies on your consent: Apple’s tracking prompt on iPhone, and the app’s own question on Android. Where consent is required, you may withdraw it by stopping the relevant optional feature or contacting us.
Temzen shows no ads. To learn which of our own ads bring people to Temzen, the app includes Meta’s (Facebook’s) SDK, which can send Meta app events: opening the app, finishing setup, viewing the Temzen Private offer, and starting a free trial or buying a subscription, with the price and currency.
On iPhone, the app asks whether you allow tracking. Only if you allow it does Meta also receive your device’s advertising identifier, your Firebase account identifier and, if you have linked Apple or Google, your email address, hashed on your device before it is sent. If you do not allow tracking, events are sent without these identifiers and can only be measured in aggregate. You can change your answer at any time in Settings → Privacy & Security → Tracking.
On Android, the app asks the first time you open it. Only if you allow it does anything reach Meta: the events above, your device’s advertising ID, your Firebase account identifier and, if linked, your hashed email address. If you do not allow it, nothing is sent to Meta. You can change your answer at any time in the app under Settings → Your data → Ad measurement.
We do not sell personal data. We do not request your device’s precise location; any community location is text you choose to enter.
Local data remains until you remove it or remove the app, subject to device backup behavior. Cloud account, backup and community records are retained to provide your chosen features until you delete them or request deletion. Use Profile → Delete account & data, or contact support. If removal fails or you can no longer access the account, contact us so we can help verify and complete your request. Some technical records may remain for limited operational, security or legal purposes; we do not retain them longer than necessary for those purposes. Purchase records are kept as long as accounting and store rules require. Data sent to Meta is retained under Meta’s policy.
Depending on applicable law, you can request access, correction, erasure, restriction or portability, object to processing based on legitimate interests, and withdraw consent. Contact us to exercise these rights. You may complain to your local supervisory authority, including Datatilsynet in Norway.
Temzen is not directed to children under 13. Contact us if you believe a child has submitted personal information. We use service access controls and encrypted transport, but no storage or transmission method can be guaranteed completely secure.
We will update this page when our practices change and revise the date above.