Cookie Policy
Local review draft: October 7, 2026 — not approved for publication
This Cookie Policy explains how VectorOS uses cookies and similar technologies. It should be read alongside our Privacy Policy. VectorOS is built to use as few cookies as possible: the ones needed to keep you signed in securely, preferences, and referral or campaign measurement on tracked visits. The four attribution cookies are described below by name; they are not all set on every visit. Landing-page and demo analytics are not collected.
What cookies are
Cookies are small text files stored on your device by your browser. Similar technologies include local storage, which we use to remember preferences such as your appearance/theme setting. We refer to these together as “cookies.”
How we use cookies
We use cookies to keep you signed in, to operate and secure the service, to remember your preferences, and to measure which of our own referral links produced a signup. Landing-page and demo analytics are not collected. The former optional landing-measurement cookie (vx_landing_measurement) and its browser preference are no longer set; visiting the landing page removes the stored preference. That cookie lasted at most 30 minutes, and the retired endpoint clears any copy it receives. We do not use cookies for advertising, and we do not track you across other websites.
Types of cookies we use
Strictly necessary / authentication. Set by our authentication provider to establish and maintain your signed-in session and to protect against unauthorized access. The service cannot function without these.
Preference. Used to remember choices such as your selected theme. These are stored on your device and are not used to track you across other sites.
Operational security. Used by our infrastructure providers to route requests and protect the service against abuse.
Referral measurement. First-party cookies vec_g, vec_g_visit, vec_ref and vg_attr may be set on tracked visits. They are not strictly necessary — VectorOS works without them. Their different purposes and protections are described below.
Optional Calendar connection. Starting a Google Calendar connection sets vec_calendar_oauth, an encrypted, HttpOnly cookie for the consent flow, lasting up to ten minutes. Successful consent replaces it with vec_calendar_access, an encrypted, HttpOnly temporary read token, also lasting up to ten minutes. The token is cleared after a successful requested snapshot or disconnect. These cookies bind the connection to your Vector account and workspace; they do not enable background sync or advertising. HTTPS environments mark them Secure.
The referral-measurement cookie
We publish links to VectorOS in places such as software directories. Those links have the form /g/<code>, where the code identifies the listing — not you. When you follow one, we record that the link was used and set a cookie so that if you later start a trial, we can tell which listing brought you.
What is stored. The vec_g cookie holds the opaque code from the link. The vec_g_visit cookie holds a random private click proof; only its hash is stored with that visit, so a public link cannot claim other visitors. We do not put your IP address, browser fingerprint, or any identifier of you into it, and the visit record we keep alongside it contains no IP address, user-agent string, or device fingerprint. Before you create an account, the record says “this link was followed,” not “this person followed it.”
Campaign parameters. The vec_ref cookie stores a validated acquisition source from ref or utm_source and preserves the first source through sign-in redirects. The vg_attr cookie stores validated ref and utm_source, utm_medium, utm_campaign, utm_content and utm_term identifiers plus a timestamp; it uses the last valid tracked visit within its expiry window. Neither is a payment receipt or proof that a campaign caused a purchase. Selected vg_attr campaign metadata may be sent to Stripe with checkout and processed with billing records.
Why we use it. To learn which places we list VectorOS are worth continuing and which are not. Without it we would be guessing, and guessing costs money we would rather spend building the product.
How long it lasts. Each attribution cookie lasts up to 30 days. They use SameSite=Lax on the VectorOS host where they are set. The referral cookies vec_g and vec_g_visit are HttpOnly and Secure in production; vec_ref is HttpOnly and Secure. The client-set vg_attr is readable by page JavaScript; it is not HttpOnly. First-party storage does not mean information can never be processed by our infrastructure or billing providers.
What it is linked to. If you create an account while the cookie is present, we link that referral record to your account. If you later become a paying subscriber, we record that too — but only when Stripe confirms a real payment, with the Stripe event identifier and amount kept as proof. A refund adjusts refunded payment amounts. Cancellation stops future renewal according to its confirmation; it does not automatically refund or erase an earlier payment. The purpose is counting: which listing produced a subscriber. It is not used to profile you, target advertising at you, or change the price you are shown.
How long the record is kept. Linked referral and billing records are considered during an account-deletion request; legal, security and billing retention requirements may limit deletion. A visit that never became an account stays unlinked — there is no person attached to it — and is kept for as long as we are still measuring that listing. We have not set a fixed number of days for those, and we would rather say so than publish one we do not enforce.
What it is not. Not an advertising-network or cross-site tracking cookie. Infrastructure providers process service records, and Stripe may receive selected campaign metadata with checkout. We do not embed third-party advertising or analytics networks in the app.
How to refuse it. Reach VectorOS by typing vectoros.ca rather than following a referral link or a URL with ref/utm parameters, and block or clear these cookies in your browser. A direct visit does not clear existing attribution. A private window can still receive these cookies while it is open; it is not an opt-out. Clearing cookies does not erase previously recorded visits or billing records. Attribution cookies are for measurement rather than sign-in. Consent or an objection mechanism may be required for particular markets; this draft does not establish that those requirements have been met.
Third-party cookies
When you make a payment, Stripe may set cookies necessary to process the transaction and prevent fraud on its checkout. Those cookies are governed by Stripe’s own policies. We do not embed third-party advertising or analytics trackers in the app. If this changes, we will update this policy and, where required, ask for your consent.
Your choices
You can control or delete cookies through your browser settings, and clear local storage at any time. Because our authentication cookies are strictly necessary, blocking them will prevent you from signing in and using VectorOS. Blocking or clearing the referral-measurement cookie has no effect on the product at all — see the section above.
Changes to this policy
We may update this Cookie Policy from time to time. Material changes will be reflected by updating the date above.
This page is part of the VectorOS Trust Center. Questions? Contact vectoros.app@gmail.com.