Privacy notice

Data we receive

Account and workspace details include your login identity, membership, settings and support messages. Verification work can include uploaded email addresses, source rows, selected connected contacts, results and usage records. Billing records include purchases, credit effects and payment references. FairValid does not ask you to enter card details in the workspace.

How data is used

We use this information to authenticate users, run requested checks, show results, manage credits and purchases, deliver service messages, answer support requests and protect the service. Optional marketing messages honor your unsubscribe choice. Connected sources are accessed only after you authorize them.

Language preferences

Our hosting platform supplies an approximate country or region to select a language on your first visit. Your saved language choice takes priority. When you sign in, we store your language preference with your account so pages and FairValid emails can use it across devices. The language feature does not store your IP address or share a preference between people using the same IP address.

Sharing

Information needed for a selected workflow can be processed by hosting, verification, payment and message-delivery services. An authorized connector exchanges only the data needed for the selected source or write-back action. A public summary link is address-hidden and can be revoked or expire.

Approximate customer country

After a verified sign-in, we save the first available country code supplied by our hosting platform, its observation time and source with your owned workspaces. Staff use it to understand customer numbers and credit usage by country. It is an estimate from your connection, not verified residence or nationality. This feature does not store your IP address, city or precise location, use advertising identifiers, or send country reports to advertising services. The observation is removed when its workspace is permanently deleted; observations in other workspaces you own remain until those workspaces are deleted.

Analytics and cookies

Google Analytics is optional and may load only after you accept it on public pages. Essential cookies keep you signed in and remember your choice.

With consent, we may also send limited server-confirmed sign-up, checkout and credit-purchase events using the public analytics browser identifier and, when available, its recent public session identifier. Purchase events contain the product type, currency, credit price before tax and a random analytics receipt, with no account, workspace or payment-provider identifiers. A separate first-paid-workspace event measures new paying customers without counting repeat credit purchases as new customers.

When enabled, a consented checkout keeps its analytics browser identifier, an available public analytics session identifier and an opaque consent reference in private storage. They expire within 24 hours of checkout or consent-reference creation and are removed by a cleanup job scheduled every minute. This allows an eligible payment to be counted if it settles after you leave the return page. We do not backfill events from before your consent.

Turning analytics off immediately stops browser measurement and requests removal of queued purchase attribution on the server. If the network is unavailable, an opaque withdrawal reference is retained for retry while a public page is open; the interface shows when server confirmation is still pending. Server confirmation cancels queued observations. An observation whose dispatch has already started cannot be recalled.

Google ads measurement is a separate, optional choice and starts off. When it is enabled and you allow both analytics and marketing measurement, Google may use a validated Google ad click identifier from a public landing-page URL, its browser and session identifiers, and confirmed purchase events to measure FairValid ads. An earlier analytics choice does not grant this permission. A checkout records the permission that existed at capture; a later opt-in cannot upgrade an earlier checkout. Turning marketing measurement off removes advertising cookies and requests withdrawal of queued purchase attribution. Google advertising personalization and Google signals remain disabled.

Meta ads measurement is another optional choice, independent of Google, and starts off. When enabled, it records a validated Facebook or Instagram click identifier from a public landing-page URL. With your permission, a first confirmed live credit purchase may send that click identifier, the browser type supplied by your browser, the price before tax in USD, a random event receipt and our public homepage address to Meta. This measures a new paying workspace once; repeat purchases are not new-customer events. Measurement-only choices, including all earlier consents, retain Meta's optimization opt-out. If you separately enable Meta purchase optimization, Meta may also use that first purchase event to improve delivery of FairValid ads to people likely to buy. This permission applies only to new checkout context created after that fresh choice; it never upgrades earlier checkouts or purchases. We do not load a Meta Pixel, create a Meta browser identifier, or send email addresses, account identifiers, client IP addresses, uploaded files or verification information through this integration.

Meta click and consent references expire within 24 hours of their creation. The click, browser type and order association expire in private storage within that period, with cleanup scheduled every minute. Turning Meta measurement off removes its local context and requests server withdrawal, independently of your Google choices. A pending withdrawal retries while a public page is open. As with analytics, a dispatch that already started cannot be recalled. An opaque receipt remains to prevent duplicate first-paid events; it contains no click or browser identifier after delivery or context cleanup.

What is never measured

Public-page analytics excludes workspace, account, billing and API pages, email addresses, list names, uploaded files, verification inputs and results, search terms and form contents. Arbitrary query strings and fragments are removed; article and guide paths are grouped. With both analytics and Google ads measurement consent, and when marketing measurement is enabled, Google may receive fixed source, medium and campaign labels for FairValid's own ads, plus a validated gclid, gbraid or wbraid. Ad and ad-set identifiers, keywords and arbitrary campaign text are removed. Click identifiers are not retained in FairValid's checkout attribution database. Google signals and advertising personalization are disabled in the application.

Cookies used

• fv_consent: an essential cookie remembering your choice for 365 days.
• fv_marketing: an essential cookie remembering the separate marketing choice for 365 days. Without a valid grant, marketing measurement is off.
• fv_meta_consent: an essential cookie remembering the independent Meta measurement choice and, only when freshly granted, purchase optimization permission for 365 days. Without a valid grant, Meta measurement is off.
• Sign-in cookies: essential cookies managed by the authentication service.
• fairvalid_locale: remembers your selected language in this browser for up to 365 days. It is not used for analytics or advertising.
• _ga and _ga_*: optional analytics cookies, configured for up to 390 days without automatic renewal and removed when you turn analytics off.
• fv_attribution: an optional opaque consent reference, lasting up to 24 hours.
• fv_ga_session: an optional public analytics session snapshot, lasting up to 30 minutes.
• _gcl_*: optional Google advertising measurement cookies when both choices permit it. These are removed when you turn either purpose off.
• fv_analytics_withdrawal: remembers a pending withdrawal until confirmation or the reference expires, for at most 24 hours. It contains no analytics browser identifier.
• fv_meta_context and fv_meta_click: optional Meta consent and validated click references lasting at most 24 hours.
• fv_meta_withdrawal: an opaque pending Meta withdrawal reference lasting until confirmation or the original 24-hour context expiry. It contains no click identifier.

Your controls

Workspace roles restrict access. You can delete lists, disconnect integrations, revoke keys and links, and request support. An owner can permanently delete the workspace after confirmation. You can contact support@fairvalid.com about your data.

Retention and deletion

Verification results remain in an open account unless you delete them. Permanent workspace deletion ends access and removes workspace data from active systems after accepted work settles.

Encrypted recovery backups follow a 30-day retention policy. If recovery is needed, deletion records are reapplied before access reopens, so backups do not reactivate deleted workspaces.

Minimal billing records required for accounting are kept separately through the seventh year after the calendar year in which the applicable accounting year ends. This does not retain workspace lists, source contacts or verification results. Limited security or deletion audit evidence may also remain separately where required.