Security and procurement
Who runs CaptionPass
CaptionPass is not a registered company.
Timothy Sharkey runs it. No legal entity stands behind it yet, and it has no registered address or postal address. We would rather you read that here than find it out halfway through a review.
Until a company exists, this is what that means for your review:
- No company can sign a contract, a data processing agreement or a student-data agreement. No template for any of them exists yet.
- No company can complete a W-9, a supplier registration, SAM.gov or a state vendor portal.
- No insurance is held, so there is no certificate of insurance to give you.
- The published Terms do not cover liability, indemnity, governing law or termination.
- No FERPA school-official agreement is in place.
If your review needs any of these, tell us what you need before you spend more time on it.
What we do not claim
CaptionPass holds no security certification and has had no independent security assessment.
- SOC 2, Type I or Type II
- No audit has been done, and there is no report.
- ISO 27001
- Not certified.
- FedRAMP, GovRAMP or TX-RAMP
- Not authorized or assessed under any of them.
- A completed HECVAT
- We have not filled one in. Send us yours and we will answer it from this page.
- An independent penetration test
- None. The only security review so far was internal, on 22 May 2026, and looked for economically exploitable paths rather than a full OWASP review.
- Employees, or a formal background-check, security-training or offboarding process
- CaptionPass has no employees and no formal process for any of these.
What a signed record cannot establish
- A file's record never states whether the captions match what was said.
- That comparison needs the audio, and the engine only ever sees the caption file, so a file's record states accuracy under FCC 79.1(j)(2)(i) as not evaluated. A vendor who states accuracy from the caption file alone is telling you something they cannot know. On the audit, Program and Contract, a person also samples accuracy, comparing clips with the video by hand, and the report states the sample size and what it supports. The clips come from your own video. How a person measures accuracy.
- We cannot answer anything about live captioning.
- WCAG 1.2.4 is a property of the broadcast, not of a delivered file. It is listed on the report so its absence is visible, and marked Not evaluated by CaptionPass, for you to answer, rather than Not Applicable, because it is entirely applicable to anyone who streams.
- We can only partly answer placement.
- Line count and dropped positioning are visible in the file. Whether a caption covers a lower third or a scoreboard needs the video, so the report says which half it checked.
- A clean scan is not a conformance proof.
- A caption file can show captions failing 1.2.2 but never show them carrying what was said. So a clean library without a person's accuracy sample gets no level from us: not Supports, which would round it up, and not Partially Supports, which by the VPAT's definition claims a defect nobody found. It is the row a careful reviewer looks for first.
What we hold, where and for how long
The caption files you add stay, exactly as uploaded, in one AWS region in the United States until you delete them or your account, or the workspace is closed.
Because a caption file is kept exactly as uploaded, it holds whatever was said aloud in the video, including anyone’s name. CaptionPass runs as one shared SaaS deployment. Accounts are separated in the data, not by infrastructure.
The free converter works in memory for each request and keeps no caption text. Everything else below is about accounts.
| On account deletion | Kinds of record |
|---|---|
| Deleted | 17 |
| Partly deleted | 4 |
| Expires on its own schedule | 12 |
| Kept, with a stated reason | 4 |
The privacy policy lists every kind of record and its reason.
After a deletion, database backups keep a removed row for 35 days, the file store keeps an earlier version of a removed file for 35 days, and server logs, which name no account, expire after 60 days.
When access ends, a workspace turns read-only. Nothing is deleted and nothing expires on its own: it stays until someone asks for its files, the account or the workspace to be deleted. Closing a workspace has a 14-day wait, and only ever starts because a person asked.
Who else receives it
6 outside services receive customer or personal data, each listed here.
| Service | What it does | What it receives | Where | When |
|---|---|---|---|---|
| Amazon Web Services | Hosting, storage, computing, email delivery, logs, content delivery and the firewall | Everything CaptionPass stores or sends | One region in the United States. Pages reach visitors through CloudFront's edge locations worldwide | Always |
| Sign-in with Google | The identity and consent of someone who chooses it | Google's own infrastructure | Only when a person signs in with Google | |
| Google (YouTube API Services) | Reads a connected channel's videos and caption tracks | Requests made under the access the channel's owner gave | Google's own infrastructure | Only when a workspace owner connects a channel |
| Slack | Tells CaptionPass about account events | An organization name and event details, never an email address or a name | Slack's own infrastructure | Always |
| Have I Been Pwned | Refuses passwords known from breaches | The first five characters of a one-way hash of the password, never the password | The service's own infrastructure | Only when a password is set |
| Google Workspace | CaptionPass's own email | Whatever someone writes to a CaptionPass address | Google's own infrastructure | Only when someone emails us |
This site runs no third-party analytics. A sampled video plays in the reviewer’s browser from the institution’s own platform, and never passes through CaptionPass.
AI
The product uses no AI model, and sends caption text to none. CaptionPass itself is built with the help of AI coding assistants. Customer data is not given to them. The founder made this commitment on November 8, 2026.
How it is encrypted
Stored files and database tables are encrypted at rest with keys AWS manages, and traffic is encrypted in transit with TLS 1.2 or later.
| What | How | Keys |
|---|---|---|
| Caption files and stored records | AES-256 server-side encryption, with all public access blocked | Managed by AWS |
| Database tables | AWS's default encryption at rest | Owned by AWS |
| Access tokens for connected channels | Encrypted separately, and readable only by the one service that talks to YouTube | A dedicated AWS KMS key |
| Traffic | TLS 1.2 or later to the site and between the site and its servers, with HTTPS enforced for 365 days at a time | Managed by AWS |
| Passwords | bcrypt with cost 12, at least 12 characters, and breached passwords refused | One-way |
| API keys | Stored only as a keyed HMAC-SHA256 hash, and shown once | A secret held on the server |
| Signed records | Signed with HMAC-SHA256 | A secret held on the server, not in a hardware module |
There are no customer-managed keys, and caption text is not encrypted field by field beyond the encryption above.
Who can reach it
Inside a workspace, roles decide who can do what. CaptionPass admins reach accounts through a console that only allowlisted addresses can open.
| Role | May |
|---|---|
| Owner | invite people, manage members, read the workspace, change the workspace, add files, delete files, export the whole library, connect a video source, create API keys and revoke API keys |
| Editor | read the workspace, change the workspace, add files and delete files |
| Viewer | read the workspace |
| Integrator | create API keys, revoke API keys and read the workspace |
People sign in with Google or with an email and password, and a session lasts up to 12 hours. Multi-factor sign-in is not offered. We keep an internal activity log to run the service. There is no customer-facing audit log or export.
Admin access
Timothy Sharkey runs CaptionPass. 1 other person holds an admin account. The admin console opens only through Google Workspace sign-in from an allowlisted address, and what each person can see depends on their admin role.
Admins can read caption text during an accuracy review. The roles that can open one are Owner, Admin and Sales. Every admin change, refusal and view of an account is logged and kept for 730 days. Anyone who operates the AWS account can also reach stored data directly, outside that console.
Backup and recovery
Database tables can be restored to any point in the last 35 days, and an earlier version of a file is kept for 35 days after it is replaced or deleted.
Our target is to lose no more than 5 minutes of data and to restore within 2 hours, or 4 hours for the usage tables. These are targets, not measurements. What has been measured is one restore to a new table, on stage, on November 7, 2026: 5 min 32 s for the users table and 3 min 47 s for the library table. Pointing the running services at a restored table has not been rehearsed.
If something goes wrong
Report a security problem to info@captionpass.com.
Alarms on server errors and an uptime check every 5 minutes reach CaptionPass by email and in Slack. There is no public status page.
We will tell the affected workspace owners by email within 72 hours of confirming an incident. The founder made this commitment on November 8, 2026.
Deleting and getting your data back
A person can delete their account at once. A workspace Owner can take every caption file with its record, and a workspace Owner can close the workspace after a 14-day wait.
| What | Who | Today |
|---|---|---|
| Delete an account | The person | API keys stop first, then the data goes. Files added to a team stay with the team. |
| Delete a file | A workspace Owner or Editor | One file at a time. A read-only workspace keeps every file. |
| Close a whole team workspace | A workspace Owner, or CaptionPass staff with the Owner role on the customer's written request | Everyone in the workspace is emailed. Team API keys, invitations and access links stop at once and the workspace turns read-only. For 14 days everything can still be read and downloaded, and any owner can cancel. After that, its files, signed records, results, vendors, fix requests, connected channels and keys are deleted. Each member keeps their own account. |
| Download the library report | Anyone who can read the workspace | CSV or JSON. |
| Download a signed record | Anyone who can read the workspace | One JSON file per caption file. |
| Download the ACR caption rows | Anyone who can read the workspace, on the audit, Program and contracts | Rows drawn from the library. |
| Download your caption files | A workspace Owner, or a person for their own library | Every caption file with its signed record, in zip parts, including from a read-only workspace. Each link works for 300 seconds and an export can be fetched for 24 hours. A storage rule then destroys it within 4 days of starting. |
| Download a copy of account data | The person | Holds the profile and API key names only, not caption files. |
An export can be checked without CaptionPass: each part carries a list of fingerprints, so you can prove every file matches its record and that nothing in the part has changed. Whether a record really came from CaptionPass is a different question. Its signature can only be checked against our key, at our verify page.
When a workspace closes, database backups keep a removed row for 35 days and the file store keeps an earlier version of a removed file for 35 days; neither can be emptied for one customer. The confirmation we email gives the date they end. What stays is the record that the close-out happened, our account record of the access we gave, our contact record of the people we dealt with, and the log of what our staff did. On a written request we also remove the contact details when the workspace closes.
Some records are kept when an account goes, such as our record of who we have dealt with; the privacy policy says which and why. Records you already gave to someone keep verifying after you leave or close a workspace, though the link to our hosted copy stops working.
Where checks and verification run
Caption files are checked, and records verified, on CaptionPass's own servers.
Anyone can check a receipt on our verify page or through the verify API, with no account — including one we hold no copy of — and nothing sent to it is stored.
The check runs on our server against our signing key: it shows a receipt is unchanged since CaptionPass issued it, and it is not something anyone can confirm without us. So verification depends on CaptionPass continuing to operate. Where a person samples accuracy, they watch the institution’s own video in their browser, and the video never passes through CaptionPass.
Our own accessibility
Of its 50 criteria, none is currently marked Does Not Support: two are marked Supports, eleven Not fully evaluated and 37 Not evaluated, each with its reason on the page.
Read our Accessibility Conformance Report.
What large buyers ask for that is not built
Each of these is answered in writing before anything is agreed.
| The requirement | Today |
|---|---|
| Single sign-on with your identity provider (SAML or OIDC), and SCIM provisioning | Sign-in is Google or email and password. |
| An isolated deployment in your own AWS account or a dedicated environment | CaptionPass runs as one shared SaaS deployment. Accounts are separated in the data, not by infrastructure. |
| Data held in a region you choose | Customer data is stored in one AWS region in the United States. |
| Audit logs you can read and export | We keep an internal activity log to run the service. There is no customer-facing audit log or export. |
| An uptime SLA, with SLA reporting | There is no SLA. The published Terms make no uptime commitment. |
| Entitlements that work offline or on premises | Every entitlement is checked online by the hosted service. |
| A usage export for reconciling invoices | The audit and Program are each billed on one invoice. There is no usage export. |
Send us your questionnaire
Send it through the enquiry form, and we will answer what we can from this page.
Where the honest answer is no, we will say no. We do not promise a response time.