Data handling
Written for the person who has to sign off on this. Everything below is checkable against what the product does.
Last updated: September 2026
What we do not claim
sixlens holds no SOC 2 report, no ISO 27001 certificate, and no third-party security audit. We are a small company and have not been through those processes.
We also do not assert that we are a "school official" under FERPA. That designation is your institution's to make and record; we will sign a data processing agreement supporting it.
We would rather you know that before you buy than discover it during a security review.
The part most people miss
Producing your report means sending survey data outside our platform to an AI provider. That includes the free text people write in their own words, not just their numeric scores.
Names and email addresses are not sent. But free text can identify its author by what it says — someone describing their own role in a small department is recognizable without being named — so treat a survey the way you would treat any open comment box in your organization. Your staff should know their words leave the building.
We do not sell response data and we do not use it to train models.
Subprocessors
Everyone who receives data from us, and what each one gets.
Anthropic
receives survey free textRuns the eight-agent analysis that produces your scores and report.
Receives: Institution name and type, category scores, and up to 50 survey responses per agent — including the free text people wrote. Not names or email addresses.
OpenAI
receives survey free textConfigured as an alternative model provider. Not used by default: every shipped model is a Claude model, and requests only reach OpenAI if an operator sets a non-Claude model name.
Receives: The same as Anthropic, and only if a non-Claude model is selected.
Supabase
receives survey free textDatabase, authentication and file storage. This is where your data lives.
Receives: Everything the product stores: accounts, institutions, survey responses, reports and decisions.
Vercel
Hosting. All traffic to the application passes through it.
Receives: Request metadata, including IP addresses, and anything in transit while a page is served.
Resend
Sends transactional email: invitations, notifications, and support replies.
Receives: Recipient name and email address, and the contents of the message sent.
LeadConnector (HighLevel)
Receives demo requests submitted from the public marketing site.
Receives: Only what someone types into the demo request form: name, work email, institution, role and areas of interest.
How data is separated
- Row-level access control in the database, so one institution cannot read another's data even through a bug in the application.
- A person sees their own support requests and nothing else, including not their colleagues'.
- Managed authentication; we never store passwords ourselves.
- Encrypted storage and encrypted connections.
Getting your data out, and getting rid of it
Anyone with an account can download everything we hold about them, and delete their account, from Settings. Deletion removes the account, the person's name and email, their notifications, their support messages and any invitation addressed to them.
Survey answers are not destroyed. They stay part of your institution's audit, because removing one respondent would change scores your board may already have seen — but the link to the person is removed, and nothing records that the answers were theirs. Your institution's own data is deleted on request when you end your contract.
Who can respond
Your institution decides who is invited. The survey supports staff, faculty and student respondents, so if you invite students, student responses are collected — and in a K-12 district that means data about minors. Whether to survey students, and what consent that requires, is your call to make before you send the link.
Questions
If your security review needs something not covered here, ask through the support page and you will get a straight answer, including where the answer is "we do not do that yet". See also our privacy policy.