DRAFT FOR COUNSEL REVIEW. This page has not been reviewed by a lawyer and is not final.
Privacy
FactWise is a US company. This page explains what we collect when you use FactWise, why, and the choices you have. We don't sell your personal information, and we don't use advertising trackers.
What we collect
- Account: your email address, and your name and company if you add them.
- Your settings: the counties and states you follow, and your alert choices.
- Your Vault: company details, references and documents you upload, such as a W-9 or insurance certificate. Your federal tax ID and uploaded files are encrypted.
- Bid packages: the details you enter for each bid.
- Security records: sign-ins and changes to your account, with the time, IP address and browser. We keep these to protect your account and to meet our security obligations.
- Card check: when you confirm your account with a card, our payment processor checks it. We keep only the card brand, last 4 digits, expiry, name on the card, billing ZIP and whether the checks passed. We never see or store the full card number. Nothing is charged.
- Pages you use: which county, bid and other pages are viewed, searches on our site, and clicks through to county postings. When you're signed in, this is linked to your account so we can support you and improve your alerts. Visitors who aren't signed in are counted without a cookie. If your browser sends Global Privacy Control or Do Not Track, we count the visit but never link it to your account. We delete these records after at most 13 months.
Every event we record
This list is generated from the code that records events, so it is always current. We keep these records for 90 days. After that only totals remain, with no account or visitor attached. Events never contain your email, name or typed text.
| What happened | When it is recorded | Why |
|---|---|---|
| account.created.v1 | first sign-in creates the account | Count new accounts and where they came from. |
| alert.link_clicked.v1 | /api/out/alert/{token} | Run and improve the service. |
| alerts.settings_saved.v1 | alert profile saved | Check that alert settings are understood. |
| auth.signed_in.v1 | sign-in link verified | Keep sign-in working and spot abuse. |
| auth.signin_requested.v1 | sign-in email requested | Keep sign-in working and spot abuse. |
| autofill.completed.v1 | package build completed | Run and improve the service. |
| autofill.failed.v1 | package build failed | Run and improve the service. |
| autofill.started.v1 | package build started | Run and improve the service. |
| bid.opened_source.v1 | /api/out/bid redirect | Count clicks through to county postings. |
| billing.canceled.v1 | subscription canceled | Run and improve the service. |
| billing.checkout_completed.v1 | checkout completed | Run and improve the service. |
| billing.checkout_started.v1 | checkout started | Run and improve the service. |
| billing.past_due.v1 | payment past due | Run and improve the service. |
| billing.plan_changed.v1 | plan changed | Run and improve the service. |
| billing.recovered.v1 | payment recovered | Run and improve the service. |
| county.opened_source.v1 | /api/out/county redirect | Count clicks through to county postings. |
| email.bounced.v1 | email bounced | Check that alert emails are delivered. |
| email.complained.v1 | spam complaint | Check that alert emails are delivered. |
| email.queued.v1 | email queued | Check that alert emails are delivered. |
| email.sent.v1 | email sent | Check that alert emails are delivered. |
| email.suppressed.v1 | email suppressed | Check that alert emails are delivered. |
| email.unsubscribed.v1 | unsubscribed | Check that alert emails are delivered. |
| experiment.exposed.v1 | first exposure to an experiment | Run and improve the service. |
| follow.added.v1 | county or state follow added | Understand which counties people follow. |
| follow.removed.v1 | county or state follow removed | Understand which counties people follow. |
| gate.hit.v1 | backend denies or blurs a plan-gated feature | Run and improve the service. |
| insights.export_requested.v1 | user dashboard export requested | Run and improve the service. |
| insights.viewed.v1 | user dashboard viewed | Run and improve the service. |
| match.alert_sent.v1 | alert marked sent | Measure whether alerts are useful and timely. |
| match.created.v1 | match stored | Measure whether alerts are useful and timely. |
| match.feedback_given.v1 | feedback saved | Measure whether alerts are useful and timely. |
| match.hidden.v1 | match hidden | Measure whether alerts are useful and timely. |
| match.saved.v1 | match saved | Measure whether alerts are useful and timely. |
| match.unsaved.v1 | match unsaved | Measure whether alerts are useful and timely. |
| match.viewed.v1 | match opened | Measure whether alerts are useful and timely. |
| match.why_opened.v1 | Why matched panel opened | Measure whether alerts are useful and timely. |
| match.why_rated.v1 | user rates the explanation | Measure whether alerts are useful and timely. |
| onboarding.skipped.v1 | user leaves onboarding | Find setup steps where people get stuck. |
| onboarding.step_completed.v1 | onboarding_step advances | Find setup steps where people get stuck. |
| page.viewed.v1 | page load or route change | Count visits and see which pages help. |
| pipeline.item_added.v1 | tracker item added | Run and improve the service. |
| pipeline.item_removed.v1 | tracker item removed | Run and improve the service. |
| pipeline.stage_changed.v1 | tracker stage changed | Run and improve the service. |
| rules.preview_used.v1 | rule preview called | Check that matching rules are understood. |
| rules.suggestion_applied.v1 | keyword nudge accepted | Check that matching rules are understood. |
| search.performed.v1 | existing search box | See what people look for and whether results were found. |
| upgrade.prompt_clicked.v1 | upgrade CTA clicked | Run and improve the service. |
| upgrade.prompt_viewed.v1 | upgrade prompt rendered | Run and improve the service. |
| vault.document_added.v1 | vault document added | Run and improve the service. |
| vault.profile_saved.v1 | vault profile saved | Run and improve the service. |
Cookies
We use two cookies, both set by FactWise itself: one keeps you signed in, and one recognizes your browser so we can spot duplicate or fraudulent accounts. Both are required for the site to work. We don't use advertising cookies or third-party tracking scripts, and we don't sell or share what you look at.
How we use it
- To run your account and send the alerts you ask for.
- To fill bid forms when you ask us to.
- To keep the service secure, prevent duplicate accounts and fix problems.
- To understand which counties and features are useful, so we can improve them.
Who we share it with
- Service providers that host and run FactWise for us, such as our cloud host and email provider. They store data in the United States and may use it only to provide their service to us. See the sub-processor list.
- Counties, only when you submit something to them.
- When the law requires it, such as a valid court order.
Where it's stored
All data is stored on servers in the United States. Part of our engineering team works outside the United States; they can't access your Vault or other non-public data.
How long we keep it
- Your account data: until you delete your account.
- Security records: up to 7 years.
- Sign-in links: deleted a day after they expire.
- Data export files: 7 days after they are ready, then deleted.
Your choices
- See and download your data any time in Settings, Account. We prepare the file in the background (usually under a minute), and the download link works for 7 days, then the file is deleted.
- Correct it in Settings or your Vault.
- Delete your account in Settings, Account. This deletes your Vault documents, bid packages, and any export files and package PDFs we prepared for you.
- Depending on your state, you may have other privacy rights. Use the form below or email privacy@factwise.io and we'll respond within 45 days.
Make a privacy request
Public records
Information about county bids on FactWise comes from public sources. Anything you submit to a county can become a public record under that state's law.
Children
FactWise is for businesses. It isn't meant for anyone under 18.
Changes
If we make important changes to this page, we'll email you before they take effect.