Privacy Policy

Last Updated: July 25, 2026 | Effective July 25, 2026

Side Quest Energy LLC d/b/a optzi! ("Optzi", "we", "us"), a Virginia limited liability company, operates the optzi! consent-management service. This Privacy Policy describes how we handle personal data of visitors to useoptzi.com, our customers, and their team members (for which Optzi is the controller), and how we process end-user consent data on behalf of our customers (for which the customer is the controller and Optzi is the processor; see the Data Processing Addendum). Contact: support@useoptzi.com.

1. Scope

This policy covers (a) visitors to our public marketing site, (b) personal data of our customers and their team members (for which Optzi is the controller), and (c) how we handle end-user consent data that our customers' websites collect (for which the customer is the controller and Optzi is the processor; see the Data Processing Addendum).

2. Customer Data We Collect and Why

Account and identity (name, email, organisation), via our authentication provider, to create and operate your account. Lawful basis: contract.
Billing data (Stripe customer and subscription identifiers, plan and billing state). We do not receive or store your card number; our payment processor handles payment. Lawful basis: contract and legal obligation (tax/accounting).
Support correspondence and operational account activity that you send to us or that is generated when we operate your account, to operate, secure, administer, and support the service. When you choose to open in-app Help, our support provider Featurebase receives your account-specific Optzi member identifier, your Optzi account identifier and account name, your display name when available, and anything you choose to submit through support chat, including attachments. Optzi does not automatically send your email address as part of the authenticated in-app Help identity, and does not automatically send Featurebase your password, payment information, consent records, website visitor records, scan evidence, or customer website content. Support history is separated between Optzi accounts. Lawful basis: legitimate interest and contract.

Do not submit passwords, API keys, payment-card information, or personal data from website visitors through support chat.

3. End-User Data We Process for Customers (as Processor)

When our customer deploys the widget, it records consent interactions of that customer's website visitors: a consent identifier, the consent and notice versions shown, the visitor's choices, and a timestamp. This supports the customer's obligation to demonstrate consent. Optzi also stores, for consent events, a country and region code derived at the network edge (we do not store the raw end-user IP), the visitor's Global Privacy Control signal where the browser sends one, and an impression identifier that links the event to the banner impression. We process this data only on the customer's documented instructions (see the Data Processing Addendum). For this data the customer is the controller, and the visitor should consult that customer's privacy policy.

4. AI-Assisted Script Classification

When a scan finds a script or iframe that our deterministic service registry does not classify, Optzi may use the Anthropic API to generate an advisory category, description, vendor name, confidence level, and short reason for the suggestion. Each request covers one finding. For an external script or iframe, we send the query-stripped host and path together with a limited set of technical attributes. For an inline script, we send the first 200 characters, its total length, and its type attribute. We do not send raw page HTML or end-user consent records to Anthropic. Because an inline script is supplied by the customer's website, its short excerpt could incidentally contain personal data embedded by that customer.

AI suggestions are never approved or applied automatically. A customer must review and approve any suggested classification before it affects the customer's configuration, and the AI classifier is not permitted to designate a script as Strictly Necessary. The feature does not make decisions about individuals.

Optzi clears the exact evidence submitted to the model from its classification record as soon as the request completes or fails. The derived classification may be retained in a rebuildable global technical cache keyed by a content fingerprint; that cache does not retain the submitted excerpt or a customer or organisation identifier. Anthropic states that, under its standard commercial API terms, API inputs and outputs are deleted from its backend within 30 days, subject to limited usage-policy, security, and legal exceptions, and are not used to train its models by default. Where a finding contains Customer Personal Data, Anthropic processes it for Optzi as a sub-processor under the Data Processing Addendum. International transfers are addressed in section 7.

To keep the consent tool working reliably, the widget sends a small, storage-less diagnostic beacon when it encounters an internal error: the error stage (an enum), the error class name, a "failed open" flag, the site's embed key, the widget version, coarse configuration flags, and the visitor's country only (derived at the network edge). It never sends the error message, stack trace, page URL, page content, cookies, local storage, or any visitor identifier, and it sets no storage on the device. Lawful basis: legitimate interest (operating a reliable, compliant tool). The beacon still transmits an IP at the network layer, which is why we disclose it here; we do not store the raw IP. Retention: 90 days. The beacon is deliberately designed to be storage-less and first-party with a closed allowlist of fields and no third-party SDK.

6. Service Providers and Sub-Processors

Our authorised sub-processors for Customer Personal Data are Supabase (database hosting, EU region), Vercel (application hosting), Cloudflare (edge content-delivery network and key-value storage), Trigger.dev (background scan jobs), Anthropic (AI-assisted classification of limited technical scan evidence), and Featurebase (limited to Customer Personal Data a customer voluntarily includes while requesting support). Clerk (authentication) and Stripe (billing) process only Optzi's own account, identity, and billing data. Featurebase ordinarily processes Optzi account identity and support correspondence as our service provider. Google provides tag-management services on useoptzi.com, and Affonso processes affiliate-referral data for Optzi; neither processes Customer Personal Data through those marketing-site roles. Featurebase is used for support, not advertising. Any analytics or marketing service is disclosed in this policy and, where required, controlled through the applicable consent category. A current sub-processor list is maintained in the dashboard or available upon request.

7. International Transfers

Our primary database is hosted in the European Union. Where personal data is transferred outside the EEA, UK, or Switzerland (for example, to US-based sub-processors for edge services, authentication, or billing), we rely on Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Modules 2 and/or 3 as applicable), the UK International Data Transfer Addendum, and any Swiss addendum, as completed for Optzi's data flows. Completed modules and addenda are available upon request from support@useoptzi.com.

8. Retention

We retain customer account data for the life of the account. We retain end-user consent records for the life of the customer account (the customer's proof-of-consent), widget diagnostic telemetry for 90 days, and scan results for 90 days. Derived AI-classification results may remain in the rebuildable global technical cache described in section 4 for as long as needed to operate and maintain consistent classifications; the submitted evidence is removed from the cache record when classification completes or fails. Support conversations and attachments are retained while needed to support the account. When we approve a valid deletion request, we remove the applicable information from Featurebase's active workspace using its supported deletion tools. Under Featurebase's published retention terms, customer content may be retained for the agreement term, deletion from active systems after termination may take up to 90 days, and encrypted backup copies may remain until overwritten for up to 365 days. On account termination we return and/or delete consent records within 30 days of the customer's instruction, after first providing a complete export, except where law requires retention; absent an instruction within 30 days after termination, we may delete after giving at least 14 days' prior notice. We retain our own minimised business records that contain no end-user personal data (billing-state ledgers, administrative-action logs, webhook-idempotency records, and our proof-of-erasure log) for up to 7 years for tax/accounting and to establish or defend legal claims. These numbers are enforced in our code where the data is held in Optzi-controlled systems; external support-data requests follow our documented provider process.

9. Your Rights

Subject to applicable law, you may request access, correction, deletion, restriction, portability, or objection. Customers and their team members can exercise rights, including access to or deletion of applicable Featurebase support data, via support@useoptzi.com. End users should contact the website operator (our customer), who is the controller; we will assist that operator as their processor.

10. California Privacy Rights

If the CCPA/CPRA applies, California consumers may have the right to know/access, delete, correct, opt out of sale or sharing, limit certain uses of sensitive personal information, and not be discriminated against for exercising those rights. We collect the categories of personal information described in sections 2 to 5 and 12 to 15 from you, your account, our service providers, and network-level operation of the service. We use them for account creation, authentication, billing, support, service operation, security, diagnostics, AI-assisted script classification, tag management, affiliate attribution, legal compliance, and accounting. We disclose personal information for business purposes to the service providers listed in section 6. Optzi does not sell or share personal information as those terms are defined by the CCPA/CPRA, does not use or disclose sensitive personal information for purposes requiring a right to limit, and does not knowingly sell or share personal information of consumers under 16. You may exercise California rights at support@useoptzi.com; where we act only as processor/service provider for a customer, we will assist that customer rather than respond as the controller/business.

11. Security

We apply technical and organisational measures appropriate to the risk (GDPR Art. 32), including tenant isolation enforced in application code, encrypted transport, and least-privilege database access.

12. Cookies on Our Own Properties

The Optzi dashboard uses cookies strictly necessary for authentication and does not load third-party analytics or advertising. Featurebase Messenger loads only after an authenticated user chooses to open Help. It may then use browser storage needed to identify the support session and preserve conversation continuity; that storage is used for support, not advertising. On useoptzi.com, our consent widget uses the first-party storage described in section 16, Google Tag Manager operates as described in section 13, Affonso storage is permitted only after Marketing consent as described in section 14, and Featurebase is permitted only after Functional consent as described in section 15.

13. Google Tag Manager

On useoptzi.com, we use Google Tag Manager to manage approved site integrations and communicate consent state to tags configured in our container. Google Tag Manager itself does not set analytics or advertising cookies, but loading it sends an ordinary network request to Google that includes technical request information such as an IP address and browser information. Google states that its standard HTTP request logs for Tag Manager are deleted within 14 days and that it may collect aggregated diagnostics about tag firing. Our lawful basis for loading the tag-management container is our legitimate interest in securely managing site integrations and consent state. Optional analytics, advertising, or marketing tags may operate only in accordance with the applicable consent choice and will be disclosed in this policy and in our consent interface before activation.

14. Affiliate Referral Attribution

On useoptzi.com, we use Affonso to operate our affiliate referral program. The Affonso script and tracking API do not load until you choose the Marketing category in our consent banner. After Marketing consent, Affonso may process affiliate and campaign parameters, a referral or click identifier, page and referrer information, and technical request information such as IP address, browser, and device information. It may set the affonso_referral and affonso_data cookies for up to 30 days to attribute a referral, preserve applicable referral-program information, calculate affiliate commissions, and report program performance. Affonso acts as our processor for this referral data. You can withdraw Marketing consent through the consent choices at any time; we then clear both Affonso cookies on this site.

For more information about Affonso's processing, see the Affonso Privacy Policy.

15. Featurebase Support Messenger

On useoptzi.com, Featurebase Messenger and Help Center access are available only after you choose the Functional category in our consent banner. We do not pass account identifiers, email addresses, or other authenticated account identity to Featurebase from the marketing site. If you voluntarily provide contact details, a message, or an attachment, Featurebase processes that information so we can answer your request. You can withdraw Functional consent through the consent choices at any time; this closes Messenger on the marketing site.

On app.useoptzi.com, Featurebase loads only after an authenticated user chooses to open Help. The account-specific identity and support information disclosed in section 2 is used to attribute the conversation to the correct Optzi account. Support history remains separated between Optzi accounts.

Do not include passwords, API keys, payment-card information, or personal data from website visitors in Featurebase messages or attachments.

On a website that uses Optzi, the consent widget keeps two first-party items in the visitor's own browser. Both are strictly necessary to provide the consent function the website has chosen to use, and neither is used for tracking, profiling, or advertising:

A small consent cookie that records the visitor's consent choices and a consent identifier, so the website can remember and demonstrate those choices.
A last-known-good copy of the website's own consent configuration (such as its banner text, consent categories, and script-handling rules), stored in the browser's local storage so the widget keeps applying the visitor's choices correctly if Optzi is briefly unreachable. This copy contains the website's own settings only, not any information about the visitor; it is refreshed on each successful load and expires automatically within 30 days.

These items are first-party storage set in the context of the website the visitor is using. The optzi! consent widget itself loads no third-party storage or SDK on that website.

17. Changes and Contact

We will notify material changes by email and/or dashboard notice. Contact support@useoptzi.com.