Published
Cookie Policy
How Grik.io uses cookies, local storage, pixels, analytics, security signals, and similar technologies.
Cookie Policy
1. Scope
This Cookie Policy explains how Grik.io uses cookies, local storage, pixels, SDK identifiers, mobile identifiers, logs, and similar technologies on the website, web app, desktop/mobile apps, Ricochet, Rico, docs, billing, support, and marketing pages.
2. What cookies are
Cookies are small files or identifiers stored by your browser or device. They help sign you in, protect sessions, remember preferences, measure usage, improve the product, detect fraud, and show relevant messages.
3. Cookie categories
| Category | Purpose | Can it be disabled? |
|---|---|---|
| Strictly necessary | Account login, security, billing, consent storage, load balancing. | Usually cannot be disabled without breaking the service. |
| Preferences | Language, theme, region, UI settings, selected model or workspace. | Can be blocked in browser settings, but preferences may not persist. |
| Analytics | Visits, page views, funnels, performance, errors, feature usage. | Can be disabled through cookie banner or browser where available. |
| Marketing and attribution | Advertising, referrals, affiliates, campaign measurement, conversion measurement. | Requires consent where required by law. |
| Security and abuse prevention | Fraud detection, bot protection, rate limits, suspicious activity, account protection. | Usually necessary for security. |
| Support and chat | Support requests, chat widget, help center session. | Can be limited, but support may work less effectively. |
4. Cookies and BYOK
In free BYOK mode, Grik.io should not use cookies to store prompts, code, files, API responses, or outputs. Cookies may be used for account sessions, settings, consent, security, and analytics if you use the Grik.io site or app.
If you use a third-party AI provider directly, that provider’s cookies, logs, and privacy practices are governed by its own terms, not this Cookie Policy.
5. Cookies and hosted inference / Rico
When using hosted inference, Rico rendering, Grik Gateway, billing, credits, or cloud functions, cookies and similar technologies may associate request metadata, job IDs, workspace IDs, billing events, consent choices, and anti-abuse signals with your account. We do not aim to place prompts, code, or media content in cookies.
6. Third-party technologies
We may use providers for analytics, crash reporting, payment processing, billing, fraud prevention, email, customer support, hosting, CDN, advertising, referral tracking, and product analytics. The specific provider list may be published in the AI Providers & Subprocessors and updated as infrastructure changes.
7. Managing cookies
- use the Grik.io cookie banner or privacy settings where available;
- delete or block cookies in your browser settings;
- use mobile OS settings for advertising identifiers and tracking permissions;
- unsubscribe from marketing emails using unsubscribe links;
- note that blocking essential cookies may break login, payment, security, or product functionality.
8. Do Not Track and Global Privacy Control
Some browsers send Do Not Track or Global Privacy Control signals. Where required by law or technically supported, we honor such signals for applicable cookies and tracking technologies.
9. Retention
Session cookies are typically deleted when you close the browser or log out. Persistent cookies may remain longer for security, consent, preferences, analytics, attribution, or fraud prevention. Retention depends on the technology, purpose, and user settings.
10. Changes
We may update this Cookie Policy when technologies, providers, laws, or the product change. The updated version takes effect when posted unless stated otherwise.