Cookie Policy

Cookies, local storage, session storage, pixels, SDK identifiers and similar technologies can remember choices, keep sessions working, protect accounts, measure site use or support embedded provider flows.

The same privacy expectations can apply even when the technology is not technically a cookie.

Essential technologies keep navigation, security, authentication, legal acceptance, billing redirects, cookie preference storage and dashboard operation working. These are needed to provide the service or a requested function.

Examples may include session cookies, CSRF or request identifiers, launch lock state, OAuth redirect state, Stripe/Twilio/Supabase flow state and preference values.

Analytics technologies help us understand page performance, broken journeys, documentation gaps and product interest. They should be configured to respect consent requirements and minimise personal data.

If analytics is disabled or not consented to, core service access should still work.

Marketing or remarketing technologies are not essential. If used, they should only run with appropriate notice and consent where required.

SIMCOAI should not use marketing cookies to make hidden eligibility or pricing decisions.

We may store cookie choices locally or in legal acceptance records so the site and dashboard remember whether you chose essential-only or all available categories.

Clearing browser data, changing device or using private browsing may reset preferences.

The dashboard may use secure authentication/session storage through Supabase and related application state. These technologies protect accounts and keep the dashboard usable.

Do not disable all storage and expect login, checkout, OAuth or legal acceptance flows to work reliably.

Stripe-hosted checkout and portal pages may use their own cookies or similar technologies for fraud prevention, payment processing, session continuity and billing security.

Card details are handled by Stripe-hosted surfaces, not by SIMCOAI chat or voice flows.

Twilio-powered voice, messaging or verification features may create provider-side events, identifiers or logs needed to route calls, diagnose delivery and comply with telecoms requirements.

Telecoms data can be subject to additional rules beyond ordinary web analytics.

The public AI assistant may use local state to remember UI mode, open/closed state, draft text or recent non-sensitive support context. Do not type secrets, card numbers or unnecessary sensitive personal data into the assistant.

The assistant should route account-specific or risky requests to support rather than guessing.

Use the SIMCOAI cookie banner or dashboard controls where available. You can also use browser settings to block or clear cookies, but doing so may break login, checkout, preference persistence or security features.

If the visible preference control is not available, email hello@simcoai.co.uk with the page, browser and request.

Session technologies may expire when the browser session ends. Preference and security technologies may last longer so choices and account protections persist. Provider technologies follow provider policies.

We review durations during product changes and aim to avoid keeping identifiers longer than necessary.

Essential technologies are generally used because they are needed for a requested service or security. Non-essential analytics or marketing technologies should rely on appropriate consent where required.

Cookie rules can apply alongside UK GDPR, so transparency and user choice both matter.

We update this policy when technology, providers, law or guidance changes. Material changes may be reflected in the dashboard legal acceptance versions.

Last updated dates are shown so customers can tell when a policy changed.

Questions about cookies or storage can be sent to hello@simcoai.co.uk. Include the page, device, browser and what you expected to happen.

For data protection rights, see the Privacy and GDPR pages.