The short version
We never connect to your systems. People answer questions in a browser, and nothing reads their tools, files or messages.
Answers are stored in the US, encrypted in transit and at rest, and never sent to an AI model.
You choose how anonymous each survey is. A report stays private to whoever launched the survey and your admins until they share it, and our team enters your workspace only with your permission.
No access to your systems
AI Adoption Score measures AI adoption by asking people, not by watching them. There are no integrations, browser extensions or tracking agents, and we never ask for access to your email, chat, code or files. People open a survey link and answer in their browser, with no account and no app.
The only outside account involved is Google, when your admins or a survey use Sign in with Google. We ask Google only for the basic profile. For admins we keep the name, email address and photo; for people answering a survey, the verified email address and Google account ID.
That keeps a security review short: there's nothing to install, and no access to grant.
What we keep from an answer
Whoever launches a survey picks how people get in, and that decides what we keep with their answers. Pick one to see the difference:
In every case, we don't keep IP addresses or device details with answers, and survey pages load no analytics or advertising trackers. Google's sign-in script loads only when a survey uses Google sign-in. Answers that haven't been saved yet wait in the person's own browser, so a dropped connection loses nothing.
When a name or an email is kept, tell people the survey is confidential, not anonymous. Getting high response rates explains why that matters for honest answers.
Who sees what
- Reports start private. Only the person who launched the survey and your organization's admins can open a new report.
- Sharing is a choice. They can share a report with named colleagues or with the whole organization. Anyone it's shared with sees all of it, including each response. Someone invited only to view reports sees just the reports shared with them.
- Public links show insights, not individual responses. The exception is AI Skills Distribution, whose insights list people's names and levels. A link can have a password, can be switched off or reset at any time, and stops working when the report is archived. Without a password, anyone with the link can open it, and search engines may list it.
- Small groups. Results show from the first answer, with no minimum group size, so in a small team a result can point to one person.
- Our team. We enter your workspace only to give support, and only with your permission. Approving our visits in the app, with a log of each visit you can see, is planned.
Where data lives
- In the US. Our database (Neon) and cache (Upstash) run in AWS's us-east-1 region in Northern Virginia, and the app runs on Vercel. Company logos are kept in the database too, with no separate file storage.
- Encrypted in transit and at rest. Every page and request uses HTTPS. The database accepts only encrypted connections and is encrypted at rest with AES-256 (Neon's security overview).
- Passwords and links. Passwords are hashed with bcrypt, and we keep only hashes of password-reset, invitation and survey-session tokens. A password-reset link works once and expires after an hour.
- Every request is checked. Our server checks each request against your organization and the person's current role, so someone you remove loses access right away.
- No account for people answering. Their survey session is a secure cookie that works only for that one survey and ends when it closes, after 30 days at most.
Companies that process it
These companies run parts of AI Adoption Score for us. Our privacy policy lists the same ones.
| Company | What it does | What it gets |
|---|---|---|
| Vercel | Hosts our website, app and surveys | Every request to them |
| Cloudflare | Delivers and protects our website | Visits to our website |
| Neon | Our database, in AWS us-east-1 | Everything the app stores: accounts, survey answers, and the names and emails in your audience |
| Upstash | Caching for the app, in AWS us-east-1 | Lists and settings the app caches, and counters that limit repeated requests. Never answers or sign-in details |
| Resend | Sends our emails | The names and addresses we email, and the emails themselves: invitations, reminders, password resets and Help Center messages |
| Sign in with Google, our team's inboxes, and Google Analytics on our website | The basic profile at sign-in, the messages you send us, and website visits if you allow analytics | |
| OpenRouter | Runs the "Ask AI" survey picker | What an admin types into it, and our public list of surveys. Never survey answers |
AI and your data
- Survey answers never go to an AI model. Scores and insights come from fixed rules, which our survey pages explain, and we don't train AI models on your data.
- The "Ask AI" survey picker helps admins choose a survey. It sends only what the admin types, up to 500 characters, and our public list of surveys to OpenRouter, which runs the AI model. We don't store what was typed.
- Connecting your own AI assistant, such as Claude or ChatGPT, is optional and read-only. It signs in with access that lasts 15 minutes at a time, and you can disconnect it whenever you like. It can read your reports' results but never anyone's individual answers, though it sees names or emails where your reports show them. What it reads goes to that AI company under your own account.
Deleting data
- Whoever launched a survey can delete a single response, and it's gone for good.
- To delete an account, someone's answers across surveys, or your whole organization, email [email protected] and we'll do it. Deleting these yourself in the app is planned.
- If you answered a survey, the organization that sent it controls your answers: ask them, or email us.
- We keep data while your workspace is active, as our privacy policy explains.
What we don't have yet
We'd rather tell you now than have you find out in a security review.
- Certifications. We're not SOC 2 or ISO 27001 certified.
- Single sign-on (SAML or OIDC). Planned.
- Two-factor sign-in for accounts that use a password. Planned. Sign in with Google uses your Google account's own 2-Step Verification.
- A data processing agreement (DPA). In preparation.
- Self-service deletion and in-app approval of our support visits. Planned.
Reporting a security issue
If you think you've found a security issue, email [email protected] with the details. Please don't access or change data that isn't yours, and give us time to fix the issue before telling anyone else.