Cookie Policy

This Cookie Policy explains how Triptomize(operator of the APIgent service, “we”) uses cookies and similar technologies (collectively, “cookies”) when you visit our website and use the Service. It works alongside our Privacy Policy, which describes how we handle personal data more generally.

1. What cookies are

Cookies are small data files placed on your device when you visit a website. They let the site remember information about your visit — such as that you are signed in, what your preferences are, or which pages you have visited — and make it work more efficiently. We also use closely related technologies such as localStorage and sessionStorage entries, which serve similar purposes and are covered by this policy.

2. Categories we use

We group cookies into three categories. You can change your preferences at any time via the Cookie preferences control, which opens the same consent dialog you saw on first visit. Rejecting non-essential cookies does not affect your access to the core Service.

2.1 Strictly necessary

These are required for the Service to function. We do not need consent to set them, and you cannot turn them off through our consent tool — though you can usually block them via your browser settings, at the cost of breaking parts of the Service.

• Authentication session — set by Firebase Authentication when you sign in, to keep you signed in across requests. Storage: cookie and IndexedDB entries used by the Firebase SDK. Retention: until you sign out or the session expires.
• Consent state— records which cookie categories you have accepted so we don’t prompt you again on every page. Storage: a cookie named cc_cookie (set by the consent tool). Retention: up to six months from your last interaction with the dialog, after which we will ask again.
• Theme preference — remembers whether you chose light or dark mode. Storage: a localStorage entry named ag-color-mode. Retention: until you clear it.

2.2 Analytics

These help us understand how the Service is used — for example which features are popular and where users encounter errors — so we can improve it. They are off by default; we only set them after you opt in.

Currently active: none. We may add an analytics provider in the future; if and when we do, we will list it here and your existing consent choice will gate it automatically.

2.3 Marketing

These would allow third-party services to measure the effectiveness of marketing campaigns and to show relevant content. They are off by default and require your opt-in.

Currently active: none.

3. Third-party cookies

Some of the cookies above are set by third parties rather than by us directly. In particular:

• Google / Firebase— sets cookies and storage entries in the course of handling authentication, including federated sign-in with Google. Google’s privacy practices are described at policies.google.com/privacy.

We do not control how third parties use the cookies they set. Please consult their privacy notices for details.

4. How to manage cookies

You can control cookies in two main ways:

• Through our in-app control — use the Cookie preferences button on this page, or the equivalent link in the website footer.
• Through your browser settings — most browsers let you block all cookies, block third-party cookies, or delete cookies on demand. See your browser’s help pages for details. Blocking strictly necessary cookies will prevent you from staying signed in.

5. Changes to this policy

We may update this Cookie Policy from time to time, for example when we add or remove a provider. When we do, the “Effective date” above will be updated. For material changes we will also re-prompt you for consent through the consent dialog.

6. Contact

Questions about this Cookie Policy can be sent to triptomize@codecrox.com.