Trust and security
A certification project holds other firms’ drawings, reports and calculations. This page says, in plain terms, how GreenTrack keeps them where they belong.
Last updated 15 Oct 2026
Who can see what
You sign in with Google, Microsoft or an email address and password. Accounts are handled by Clerk, so GreenTrack never stores a password.
Every workspace, personal or firm, is separate. When you use GreenTrack, the application reads and writes the database as you, and row-level rules in the database decide what you may read or change. The server checks the product’s permission rules before every write, and the database checks again.
A few server tasks use a privileged connection instead, because they act before you are a member or across workspaces: publishing and maintaining rating libraries, keeping your name and email in step with your sign-in, and joining you to projects you were invited to by email. Each runs only after the server has checked who is asking, and none of them touches a project’s deliverables, evidence or comments.
- Everyone on a project reads everything on it, as on site.
- A consultant changes only deliverables their discipline leads or supports, and submits only as lead.
- Project admins set up the project, choose routes, review evidence, run the stage gate and manage the team. Workspace admins also manage members and the workspace’s own libraries.
- Someone invited to a single project sees that project and nothing else in the workspace, even if their own firm uses GreenTrack too.
Where your data lives
GreenTrack is built on a small number of providers, each with one job. Everything is encrypted in transit, and the database and files are encrypted at rest.
| Provider | What for | What they hold | Where |
|---|---|---|---|
| Clerk | Accounts, sign-in, workspaces and invitation emails | Name, email, profile picture, workspace memberships, session | United States |
| Supabase | Database and file storage | Projects, deliverables, comments, evidence files, libraries and manuals | India (Mumbai region), encrypted in transit and at rest |
| Vercel | Hosting the application and running its scheduled jobs | Request logs (address, browser, time, page) | United States and edge locations |
| OpenAI | AI features, once they launch: reading and explaining your project's content on request | Only the content needed for that request; not used to train models under OpenAI's API terms | United States |
No analytics or advertising services run on GreenTrack, and no data is sold or shared for anyone else’s purposes.
Evidence files
Evidence lives in a private bucket. Nothing in it has a public address. A file reaches storage through a one-time upload link the server issues only after checking that the person may upload to that deliverable, and is read back through a download link that expires after one minute. Rating manuals open through links that last long enough to read them and no longer.
Files are limited to 50 MB each. A file that is replaced or removed stops being current evidence but stays in the deliverable's history, where the team can still download it (see the next section).
Nothing disappears
A certification is an audit trail, so GreenTrack never deletes a deliverable, a piece of evidence or a comment. When a rule stops applying, a deliverable becomes inactive; when a file is replaced or removed, the earlier version stays in the history and can still be downloaded. Every change, with who made it and when, is written to the project’s activity log.
Advancing a phase locks every earlier deliverable for everyone. An admin can reopen one at a time, with a reason that goes on the record.
What your browser holds
- A session cookie from Clerk, so you stay signed in.
- A cookie that remembers whether the sidebar is open.
- Two entries in local storage: the theme applied in this browser (light, dark or system) and the account it belongs to, so a shared computer shows each person their own choice. Your preferences themselves are saved on your account.
Page data is cached in your browser for one minute so moving between screens is instant. A build check refuses to ship the application if any secret would reach the browser.
AI features
AI features are not live yet. When they arrive they will read, explain, draft and flag, and nothing more. They never compute points, ratings, buffers, risk, due dates or statuses, and they never change anything on their own: a person confirms every write. Every AI-written block is labelled as such, and the numbers next to it come from the product’s own calculation, which the screen says.
A request sends OpenAI only the content needed to answer it, under API terms that exclude using it to train models. We will update this page and the privacy policy before the first AI feature ships.
Operators and support
GreenTrack staff maintain the standard rating libraries. They hold no role in your workspace and do not appear on your projects. Our operators can reach the database to run and maintain the service; they do so only to keep it running, to fix a problem you have reported, or when the law requires, and never to read your projects for any other reason.
Report a problem
If you find a security problem, tell us before anyone else and give us a reasonable time to fix it. We will acknowledge your report and keep you informed. Please do not test against workspaces that are not yours.
Write to hello@greentrack.app.