Privacy

Two kinds of thing. Account data is the email address and name of whoever signs in, handled by our authentication provider. Crew data is the names, roles, sites and certification dates you enter, plus any scans or photos of certificates you attach.

If you sign in with Google, Google sends us your name, email address and profile picture, and we use them only to sign you in. We never receive your password or anything else in that account.

Crew data is about your employees, not our users. You are the controller of it; we process it on your behalf.

Run the product: show you the board, work out what is expiring, send the warning emails you asked for, help you with support and billing, and read the feedback you send. That is the whole list.

We do not sell it, share it with other customers, or use it to train anything.

Every customer’s records are isolated at the database level, enforced by the database itself rather than by application code remembering to filter. A query that forgets its filter returns nothing rather than another company’s crew.

A scan or photo you attach to a credential is kept in private file storage with our hosting provider. It has no public link. It opens only for someone signed in to your account, and only after we check the record belongs to your company.

Replace or remove a scan and the old file is deleted. Delete a credential record, a person or the account and their scans are deleted with them. Currity staff see how many scans an account holds, not the files.

When a crew member sends a photo of a card through their link, or you use Scan a card, the photo is sent through Vercel AI Gateway to an AI model provider (currently Anthropic) to read the name, dates, number and issuer off it. We ask for zero data retention on that request, so the provider does not keep the photo. It is not used to train anything.

What we store is the photo, in the same private file storage as other scans, and the details the reader suggested next to the details the person confirmed. Nothing goes on the board until someone on your account approves it. A card sent back is deleted; an approved one becomes an ordinary certificate scan.

A card link works for 14 days and shows only your company’s name, the person’s first name and the cards they owe.

When you send feedback, from Send feedback in the app or from the Request a feature page, we store what you wrote with your email address, so Chris can reply. In the app we also keep the page you were on and your browser’s name (Chrome, Safari), nothing more about your device.

It is never shared. Nobody else on your account can see what you sent, only you and Currity staff. If you untick “You can email me about this”, or leave the address off the public form, nobody will write back.

If you print a hard hat sticker for someone on your crew, its code opens a page for whoever scans it, with no login. That page shows the worker’s name, role, site and company, whether they are cleared to work today, and for each card they need its status, its expiry date and the day your team recorded checking it, if they did. Nothing else: no email, phone number, employee number, card number or scan.

We do not record who scanned a sticker, or when. A sticker stops working when you replace or stop it, or when the person leaves your active crew.

Currity staff can access account data to answer a support request or to sort out billing. They do not look at it for any other reason.

Every such access is recorded in an internal log, saying who looked, at what, and when.

If support changes anything in your account, the change appears in your own audit log, alongside the changes your team makes.

Your crew’s names are shown to staff only when a support request needs them.

The companies that run parts of Currity for us. Each gets what it needs for its one job, and nothing more from us:

• Vercel hosts the site and keeps the scans, card photos and project packets in private file storage.
• Vercel Web Analytics counts visits to the public pages of this site: which page, the site that linked to it, and the visitor’s country, browser and device type. It sets no cookies. Pages inside the app, and the private links sent to crews and general contractors, are never counted.
• Neon runs the database that holds your account and crew records.
• Clerk handles signing in: the name and email address of everyone on your account, and their sign in sessions.
• Resend delivers the emails Currity sends, so it sees who each one goes to and what it says, crew names and card dates included.
• Stripe takes payment. It gets your company name, the owner’s email address and the card you pay with. We never see the card number.
• Vercel AI Gateway and Anthropic read a card photo when one is sent to be read, as described above.
• GitHub and Cloudflare each keep an encrypted copy of the daily database backup (see below).
• Sentry receives a report when something in the app breaks: what failed and on which page. It is set not to collect IP addresses or cookies.
• Zoho Mail hosts hello@currity.com, so an email you send us, or a reply to a warning, is stored there.

For as long as your account is open. Delete a person and their record goes; close the account and we remove your data within 30 days, after giving you a chance to export it.

We back up the database every day. Each backup is encrypted and kept for up to 12 months, then deleted. A record deleted from the live database can stay in the backups made before it was deleted until they run out.

Ask us for a copy of what we hold, a correction, or deletion, and we will do it. Email is the fastest route. There is no form to fill in.