Privacy Policy

1 · Everything we collect, category by category

PURCHASE RECORDS (software). Your email as reported by the payment provider, order contents, transaction ids, and license grants — kept because they are the proof of what you own and the basis of support, refunds, and revocation. Money amounts are recorded on an append-only audit ledger for integrity. Lawful basis: performance of our contract with you, and our legal obligation to keep tax records.

PURCHASE RECORDS (merchandise). The same order record, plus one thing that only exists on this rail: a shipping address. The address is collected and held by Stripe on the hosted checkout page and is used by us to fulfil the order — our own database stores the order, the email, and the amounts, not the address. Lawful basis: performance of our contract with you.

LICENSE ACCESS LINK. When a purchase completes we email a link containing a single-use access token. We store only a SHA-256 hash of that token, never the token itself, and issuing a new link revokes the previous one. Lawful basis: performance of our contract — the link is how a purchase is delivered.

ACCOUNT IDENTITY (when accounts are enabled). If you sign in, our identity provider Clerk holds your account credentials and profile; we receive a user id and an email address and key your order history, rewards balance, and support tickets to that id. We never receive or store your account password. Lawful basis: performance of our contract with you.

SIGNAL LIST. An email address you submit to be told when we launch, stored with the source and the date. Lawful basis: your consent, which you may withdraw at any time (see §5). Withdrawing it never affects your licenses.

SUPPORT TICKETS. What you send us when you open a ticket: your message, the product and framework you name, and any log or configuration text you paste. Secrets are stripped server-side at ingest before anything is stored — we keep only the redacted text plus a count of what kind of secret was removed, never the secret value. Attachments are stored as metadata and a storage pointer; file bytes never enter our database. Lawful basis: performance of our contract, and our legitimate interest in supporting the product.

INSTALL CONCIERGE INTAKE. The diagnostic tool accepts pasted text — typically server.cfg fragments, console output, or SQL errors. That text is sent to our server, redacted and analysed there by a deterministic rules engine, and the structured result is returned. The pasted text is not stored, not persisted to any database, and is not sent to any third-party model. Lawful basis: performance of our contract, and our legitimate interest in diagnosing installs.

NETWORK ADDRESS (rate limiting). Every public endpoint counts requests per client address to stop a single client hammering it. The counter lives in the server process's memory, holds the address as a bucket key and nothing else, and is discarded when its window rolls (at most 15 minutes). It is never written to a database and never used to identify or profile you. Lawful basis: our legitimate interest in keeping the service available.

ERROR REPORTS. When something breaks, Sentry receives the technical detail of that one request — typically IP address, user agent, URL, and a stack trace — so it can be fixed. Session replay is switched off. Lawful basis: our legitimate interest in a working store.

WE DO NOT COLLECT: card or bank details (the payment page is hosted by Tebex or Stripe and we never see them); gameplay, player, or database data from your FiveM server; location data; advertising or behavioural profiles; or any special-category data. We do not sell or share personal information, and we do not process it for cross-context behavioural advertising — under the CCPA and comparable state laws, there is nothing here for you to opt out of.

2 · Cookies and browser storage

We set no advertising cookies and we sell no data, and we run no analytics product of our own. Our hosting provider, GoDaddy, loads a traffic-measurement script (from img1.wsimg.com) on the pages it serves, and that script sets cookies: _tccl_visitor and _tccl_visit hold a random identifier that tells one browser from another, and _scc_session counts the pages viewed in a session and the time of the last one. They carry no name, email, or purchase information. Counting visitors is analytics, so we say so rather than claim we do none. Your cart is held in your own browser's local storage under the key vf_cart_v2 (a cart saved under the older key vf_cart_v1 is read once and migrated) and never leaves your device until you check out. Tool pages that ask you to paste something — the redaction checker, the start-order checker, the install checklist — keep that text in the page's memory for the visit and write it nowhere.

When accounts are enabled, Clerk sets the session cookie that keeps you signed in; it is strictly necessary for that purpose. A separate development-only cookie exists in the codebase for local testing and is ignored outright on the production deployment.

3 · Processors we rely on

GoDaddy — hosts this website; its traffic-measurement script sets the cookies described in §2. Tebex Limited — checkout, payment, and taxes for software, as merchant of record; their privacy policy applies to payment data. Stripe, Inc. — checkout, payment, sales tax, and shipping-address collection for physical merchandise; their privacy policy applies to that data. Cfx.re — escrow license delivery bound to your Cfx account. Clerk — account identity and sign-in, when accounts are enabled. Vercel — site and API hosting. Neon — database hosting for the order, license, and support ledgers. Sentry — error monitoring.

Each processes data under its own terms, and we share only what its function requires. Several of these are United States companies, so personal data may be processed in the United States; where a transfer mechanism is required for your jurisdiction we rely on the processor's own published safeguards. The list above is machine-checked against the code: adding a processor without naming it here fails our build.

4 · How long we keep each thing

Orders, license grants, and the audit ledger: retained for as long as a license may need proving and as long as tax and accounting law requires (commonly seven years). The audit ledger is append-only by design — entries are never edited or deleted, which is the point of it.

License access tokens: 30 days from issue, then expired; reissuing revokes the previous token immediately. Revoked and expired rows are kept as an audit record with only the hash, never a usable credential.

Signal-list emails: held until you ask to be removed, then deleted.

Support tickets and their redacted messages: retained while relevant to your licenses and defect history [terms-pending] — a fixed period has not been set, and we would rather say so than publish a number we do not enforce.

Rate-limit buckets: at most 15 minutes, in memory only. Error reports: held by Sentry under Sentry's own retention schedule for our plan, which we do not control.

5 · Your rights, and how to actually use them

Depending on where you live (GDPR, UK GDPR, CCPA/CPRA and comparable US state laws, and others), you may request access to, a copy of, correction of, or deletion of your personal data; object to or restrict processing based on legitimate interests; and withdraw consent. Email support@vicedrip.com and we will verify the request against your purchase email and answer within the statutory period (one month under GDPR/UK GDPR; 45 days under the CCPA). You will never be charged or treated differently for exercising a right.

Leaving the signal list: email support@vicedrip.com with "unsubscribe" and we will delete the address. Every marketing email we send will also carry a working one-click unsubscribe link, as US, EU, and UK law require. We have not yet sent a marketing email — no mail transport is configured — and our build gate refuses to let this policy promise a removal route that the code does not implement.

What a deletion request cannot remove: transaction and audit records we are required to keep for tax, accounting, or license-integrity reasons. We will tell you exactly what remains, why, and for how long. If you are unhappy with our answer you may complain to your data protection authority — in the UK, the ICO; in the EU, your national supervisory authority.

6 · Children, changes, and contact

This store is not directed at children and we do not knowingly collect personal data from anyone under 16. If you believe a child has given us data, tell us and we will delete it.

This policy is versioned and dated; material changes update the version and effective date above and are announced on the site before taking effect. Contact for privacy matters, including any request under §5: support@vicedrip.com. New Origins Studio is the data controller.