Your study data is not advertising inventory.

Information you give us

When you create an account, you give us your email address and a password. If you joined our earlier waitlist, we hold what you gave us then: your name, email address, exam date, answers about how you study, and whether you have Anki history. Paivio also processes your account details, uploaded decks and source material, generated cards, settings, and study and review history so the product can work.

When you are signed in, Paivio records first-party product analytics events, such as opening the dashboard, rating a card, or starting checkout. These first-party records are deleted when you delete your account. When product measurement is enabled, selected browser events are also sent to PostHog as described below.

Site measurement

Paivio uses a first-party cookie named la_vid to connect an anonymous visit with a later waitlist signup or account, so we can see which page and campaign tags it first arrived from. The cookie contains a random identifier, not your name or email address. We record the page visited and, when present, campaign or referral tags from the arrival URL. The cookie lasts for up to one year.

After a UK or EEA visitor answers the Meta advertising measurement prompt, Paivio sets an HttpOnly cookie named paivio_tracking_choice that contains only the identifier for that choice. The cookie expires with the choice after about 13 months.

Product analytics and session replay

When product measurement is enabled, Paivio uses PostHog in the United States to understand how people use the website and study product, where uploads fail, where study sessions stop and which errors people meet. PostHog receives page views and page exits, clicks, form changes and submissions (without the element's text or what you typed), repeated and unresponsive clicks, page-load performance, error reports with technical details, answers to optional rating surveys, feature-flag assignments, browser and device information, the address of the site that referred you and campaign tags in the page address, random browser and session identifiers, and your Paivio account identifier when you are signed in. Paivio's servers also send PostHog a few account milestones linked to that identifier — account confirmed, goal saved, material ready, each review recorded, first study and paid checkout — with your plan, whether you hold a beta spot and the dates you reached each milestone. We do not attach your name or email address to these reports. PostHog is a separate recipient from Meta.

Session replay records a reconstruction of eligible pages and your interactions, including browser console messages and the timing of network requests. Page text, including card questions and answers and deck names, can be visible in recordings; typed answers and other form inputs are masked, and account details such as your email address are hidden. Authentication, credential handoff and administrative pages are excluded. We do not record network request or response contents or headers, or canvas content.

For UK and EEA visitors, this measurement starts only after a separate product measurement choice. It is enabled by default in other regions, including when a region cannot be identified, unless you decline or Global Privacy Control is enabled. A previous permission for Meta advertising does not grant permission for PostHog. Research consent remains separate from both choices. The same choice governs the server milestones: Paivio sends them only while measurement is enabled for the browser making the request, and a paid checkout counts as enabled when measurement was enabled as checkout started.

Use Measurement settings at the bottom of the website or app to decline or change this choice. Declining stops further collection; reports already sent cannot be recalled by that control. The first-party HttpOnly cookie paivio_product_choice contains only a reference to your saved choice and lasts for about 13 months. PostHog also uses browser storage for its identifiers while measurement is enabled.

PostHog recordings and analytics have their own retention settings. Account deletion removes Paivio's first-party records but does not automatically erase reports already sent to PostHog. Contact info@paivio.aito request removal of those reports. You can read more about the provider in PostHog's privacy policy.

Meta advertising measurement

On the homepage, product, science, subjects, pricing, about, and waitlist pages, the Meta pixel may report PageView and ViewContent when a page loads, WaitlistStart when someone begins the waitlist form, and Lead after a successful waitlist submission. These events tell us whether advertising led to visits and waitlist signups. They do not include your decks, study history, profile, or quiz answers.

For visitors in the UK and EEA, Paivio does not load the Meta pixel or send a server-side report to Meta until you choose “Allow measurement” in a prompt about optional Meta advertising measurement. Choosing “No thanks” records an opt-out that cancels pending deliveries. Global Privacy Control hides the prompt. For US visitors, the existing default-on Meta advertising measurement is unchanged.

Meta is the recipient of this advertising measurement. PageView and Lead browser reports include the event, page URL, and an event identifier. Paivio also sends Meta a server-side PageView, Lead, CompleteRegistration, FirstStudy, and Purchase when eligible. The server-side Lead is created only after the waitlist email is verified, and its delivery queue runs hourly. CompleteRegistration is sent once per account, from the server only, when you confirm the email address for a new account. FirstStudy is sent once per account, from the server only, the first time you rate a card; it carries no deck, card, rating or study content. Purchase is sent once per paid checkout, from the server only, after Stripe confirms the payment; it carries the price paid before tax and its currency, and no card, deck or study data. Server-side PageView matching may use your IP address, browser user agent, and Meta's _fbp and _fbc cookies. Lead, CompleteRegistration, FirstStudy, and Purchase matching may use those details plus a one-way hash of the email address submitted to the waitlist or used for the account. CompleteRegistration, FirstStudy, and Purchase matching also uses a one-way hash of your account identifier. The shared event identifier lets Meta treat the browser and server reports as one event rather than two.

Loading the Meta pixel sets Meta's _fbp cookie on this site and, after an ad click, its _fbc cookie. Meta governs how long those cookies last. Meta's pixel also collects standard browser and device information described in Meta's policy.

How long measurement data is kept

The la_vid cookie lasts up to one year. A server-side measurement choice remains valid for about 13 months; Paivio does not treat it as permission after that. Paivio keeps the hashed email, IP address, user agent, and Meta cookie values used for server-side matching for no more than about 43 hours; a recorded opt-out erases them sooner. After reporting a Lead, the browser stores the normalized waitlist email in local storage to avoid reporting it again; that entry remains until you clear this site's browser storage. Other first-party funnel and waitlist records do not currently have a fixed automatic deletion period. Meta's own retention and use of data it receives are governed by Meta's policies.

How to opt out of Meta measurement

Enable Global Privacy Control in your browser. Paivio checks that signal before the browser loads the Meta pixel and when its server receives a waitlist submit, a page-view request, or an account email confirmation. A Lead already captured without Global Privacy Control is not cancelled if you enable the signal afterwards. A request already sent to Meta cannot be recalled.

What we do not sell or share for advertising

We never sell your decks, study history, or profile, and the only study fact we share for advertising is a one-time signal that your account has started studying. Study data is used to provide Paivio and, where you separately consent, for the learning research described in the signed-in research consent policy. Research choices do not replace the advertising-measurement choice described here.

Service providers and security

Paivio uses service providers to host the application, store data, authenticate accounts, deliver product email, and run the product. We limit access to what is needed for those services. Signing in sets the cookies that keep you signed in. No internet service can promise perfect security, but access to private account and study data is restricted by account and service-role controls.

When you buy a plan or credits, Stripe processes the payment. Your card details go directly to Stripe and are not stored by Paivio; we keep the Stripe customer, subscription and checkout identifiers linked to your account, your plan, and your credit balance.

Paivio sends error reports to Sentry so we can find and fix failures. A report holds the technical details of the error and the page or API address where it happened. We remove query strings, cookies, request headers and form contents before a report is sent, and we do not attach your name, email address, or account identifier.

Paivio uses AI model providers and proprietary LLM systems to run study features. When you type an answer for Paivio to check, we send the card's question, its expected answer, and the answer you typed to an AI model provider so that a model can grade it. We do not send your name, email address, or account identifier with that request.

Your account and questions

You can download your data or delete your account from Settings. You can ask a privacy question by emailing info@paivio.ai. We may update this policy as Paivio changes; the effective date above shows the current version. See also the terms of service.