Cookies & Local Storage Notice

This notice covers two surfaces:

• The Timents website at timents.com, including the public-safe web preview pages for profiles, moments, chapters, and invites (the /u, /m, /c, and /invite routes).
• The Timents iOS app for iPhone, distributed in private beta via Apple TestFlight.

It sits alongside our Privacy Policy, which explains the personal information Timents collects more broadly, and our Privacy Choices page, which maps the controls available to you. Where this notice talks about "storage," we mean cookies, browser local storage, and on-device app storage, not the personal information practices described in the Privacy Policy.

For tracking, advertising, or building a profile of you: no. The Timents website sets no advertising cookies and no cross-site tracking cookies, and it does not load third-party ad or analytics trackers for that purpose.

The website is a static site configured with a privacy-respecting default: it sends a no-referrer referrer policy and opts out of interest-cohort (FLoC-style) participation. Any storage it does set is limited to what is strictly necessary to serve the page and remember a small number of your own display preferences.

We do not claim to use cookies we do not use. If a strictly-necessary cookie is needed in the future to keep the site working (for example, basic security or load balancing), it would be limited to that purpose and described here.

On the website, we may use your browser's local storage only for strictly necessary purposes — for example, remembering a choice you make during your visit so the page behaves consistently. Any such value stays in your browser, is never tied to an advertising identity, and is not used to track you across other sites. Clearing your browser storage removes it.

In the iOS app, Timents does not use web cookies. Instead it uses standard on-device storage to make the app function, such as keeping you signed in between launches, caching content you have already loaded so the app feels fast, and storing your in-app preferences. Firebase SDKs (described below) also keep a local installation identifier and cached state on the device for app functionality. This on-device data is removed when you delete the app, and account data is handled per the deletion flow described in our Privacy Policy.

Like virtually all websites and online services, our servers keep standard request logs when a page or preview is served. These logs may include details such as the request time, the page or route requested, IP address, browser user-agent, and response status.

We use these logs to operate the Service reliably, troubleshoot problems, and protect against abuse and security threats. They are first-party operational records, not an advertising or cross-site tracking mechanism. The public-safe web preview pages (/u, /m, /c, /invite) are rendered by a Google Cloud Run service, and that infrastructure generates request logs of this kind.

Any analytics Timents uses are first-party and exist only to operate and improve the Service. We use them to understand reliability and basic product usage, not to follow you around the web.

Consistent with our overall posture, there is no third-party advertising, no cross-app or cross-site tracking, and no tracking as defined by Apple's App Tracking Transparency framework. In the iOS app, product analytics are first-party and governed by in-app consent controls; you can review and change those on Privacy Choices. Revoking analytics consent stops future product analytics collection where the app and backend support that state.

To be unambiguous:

• Timents does not run third-party advertising on the website or in the app.
• Timents does not use advertising cookies, advertising identifiers, or interest-cohort signals to target you.
• Timents does not perform cross-site or cross-app tracking, and the app declares no tracking under Apple's App Tracking Transparency framework.
• Timents does not sell personal information.

This is a deliberate design choice. Timents is built to be a calm, private-first memory app, not an advertising or comparison engine, so we have no reason to track you across other services.

Timents relies on a small set of infrastructure providers to run the Service. Some of these may set their own technical storage on your device to function. We do not use them for advertising or cross-site tracking, but their own technical mechanisms are worth naming:

• Google Firebase. Used for authentication, the Firestore database, Cloud Storage for your media, Remote Config, and Cloud Messaging (push). In the app, the Firebase SDKs keep local installation identifiers and cached state on your device so these features work.
• Google Cloud Platform. Hosts the Service and runs the Cloud Run service that renders the public-safe web preview pages. Serving those pages produces standard server request logs as described above.
• Apple. Provides app distribution via TestFlight and the App Store, and the Apple Push Notification service for delivering notifications.
• Email and SMS delivery providers. Send your one-time verification codes and account messages.

These providers process data under their own terms and only for the purposes described in our Privacy Policy. The public web previews are intentionally minimal, and private, friends-only, or chapter-limited media is never served as a permanent public URL.

You stay in control of what is stored on your device.

In your browser

• Most browsers let you view, block, or clear cookies and local storage in their privacy or site-data settings. Clearing site data for timents.com removes any preferences we have saved, such as your theme choice.
• You can browse in a private or incognito window to avoid persistent local storage between sessions.

On your iPhone

• You can manage app permissions for Camera, Photo Library, Contacts, and Notifications in iOS Settings. Contacts access is optional and only used for friend discovery when you grant it.
• Deleting the Timents app removes its on-device storage and cached content. Account data is handled separately through the in-app account deletion flow described in our Privacy Policy.

Blocking strictly-necessary storage may affect basic functionality, such as remembering a display preference, but the website does not depend on advertising or tracking storage to work.

Because Timents does not perform cross-site tracking and does not sell or share personal information for advertising, there is no cross-site tracking behavior for a browser signal to switch off. We honor this stance regardless of the signal your browser sends.

Browsers handle Do Not Track (DNT) and the Global Privacy Control (GPC) inconsistently, and there is no single industry standard for how a static site like ours should respond. Our practices already align with what these signals ask for: no advertising cookies, no cross-site tracking, and no sale of personal information. If our practices ever change in a way that makes these signals meaningful, we will update this notice and honor a valid GPC signal as an opt-out where the law requires.

We may update this notice as the Service evolves, for example if we introduce a strictly-necessary cookie or add a privacy-respecting first-party analytics tool. When we make material changes, we will revise the effective date above and provide additional notice where appropriate. We will not quietly add advertising or cross-site tracking; introducing anything of that nature would be a material change reflected here and in our Privacy Policy.

Questions about cookies, local storage, or this notice can be sent to privacy@timents.com. General support is available at support@timents.com, and legal notices can be sent to legal@timents.com.