The short version
This website sets no cookies and carries no third-party trackers — no advertising pixels, no analytics SDK, nothing that follows you to another site. We do not sell personal data, and we never have. Candidate data belongs to the employer who collected it; we process it on their instructions and hand it back or delete it on request.
Visitors to this website
Our analytics are first-party and built in-house, precisely so that measuring our own marketing does not mean handing your browsing to somebody else. Concretely:
- No cookies. A random identifier is stored in your browser's local storage for this site only. It means nothing on any other website and is not shared with anyone.
- We do not store your IP address. Your address reaches our servers, as it must for any website to answer you at all. We use it at that moment to work out the country, region and city you are in, which network operator you are using, and — if you are on a company network rather than a home one — which company that network belongs to. Then it is discarded. We do not write it down, and we keep nothing from it that could distinguish you from anyone else on the same network.
- No advertising or tracking companies. No Google Analytics, no advertising network, no session recorder, no heatmap tool, no social pixel, and no service that sells identification of website visitors. Nothing we collect follows you to another website, and we do not buy data about you from anyone.
What we do record, for our own pages only: which pages you opened, how far down them you read, which links you clicked, how much of the demo film you watched, and roughly how long you were actively reading. If you arrived from one of our emails, the link carries a code that tells us which campaign it was and, because we sent it to you, who opened it.
We also record what your browser reports about itself — its name and version, your operating system, whether you are on a phone, tablet or computer, your screen and window size, your language and time zone, and a few similar details. We use them to know what to build and test for, and together they help us recognise your return visits. If that is more than you want to share, the last paragraph of this section applies. These particular details are deleted after 90 days; the record of what you read is not, because that is the history our sales team works from.
What this adds up to. If you visit from a company network, we are likely to know which company — that is the point of it, because knowing which businesses are interested in us is how a company our size sells anything. If you visit from home or from a phone, we will almost certainly not know who you are unless you tell us, by booking a demo or following a link from an email we sent you.
If you would rather we did not, block /analytics.js, use your browser's
do-not-track or content blocker, or email us and we will delete everything tied to you.
Sharing a link to us
If you use one of the share buttons on this site, the link you send carries a short code that says it came from you. We cannot see who you sent it to — your phone's share menu and your email program do not tell us, and there is no way for us to find out. What we do see is when somebody opens that link, and if that person later books a demo or gives us their email, we will know it was you who passed us on.
Practically: we can tell you that three people opened your link and name the one who booked. We can never tell you the other two, or who you sent it to. If you would rather not be identified as the sender, copy the address out of your browser's address bar instead of using the button — the code is removed from it deliberately, so the link you copy that way carries nothing.
Booking a demo
The booking form collects your name, work email, company and, optionally, your monthly requisition volume. We use it to hold the meeting and to follow up about it. Booking places a calendar invitation on your calendar and ours, sends you that invitation and a confirmation email from us, and notifies our team. We do not add you to a marketing list you did not ask for.
Calls with our AI sales agent
If you start a voice call from this site, the call is recorded and transcribed. You are told at the start, the agent will confirm it if you ask, and you can end the call at any moment. We keep the recording and transcript to improve the agent and to remember what we discussed. Ask us and we will delete both.
Candidate data
The employer is the controller; we are the processor. When an agency or a hiring team uses Fasmac, they decide what to collect and why. We act on their instructions. If you are a candidate and you want your data removed, the employer who invited you is the right first stop — but write to us as well and we will help rather than send you away.
Depending on what that employer asks for, we process:
- The résumé or CV you submitted, and what our extraction reads out of it — contact details, work history, education, skills.
- Your application, its status, and the scores our screening produced against that employer's criteria.
- If you take an AI screening call: the audio, a transcript, and the scores derived from them. You are told before the call begins, and taking it is a decision you make.
Who else touches the data
We use a small number of sub-processors. We do not use an advertising network, a data broker or an enrichment vendor that resells personal data.
| Who | What for |
|---|---|
| Cloudflare | Hosting, CDN, and the databases behind this site |
| Supabase | The main application database |
| Backblaze B2 | Stored files and call recordings |
| Language models used for extraction and screening | |
| Groq | Language models used for extraction and screening |
Your rights
Wherever you live, and regardless of which law happens to apply to you, we will: tell you what we hold about you, correct it if it is wrong, give you a copy, and delete it. We would rather honour a request than argue about whether we are obliged to.
Ask at hello@fasmac.co. If you are a candidate, say which employer you applied to and we will find you faster. One caveat we will be straight about: where a record is part of a hiring decision an employer must retain, we may have to keep it for the period the law sets for them — see Fairness & compliance, which explains why records of automated decisions are kept.
Security
Data is encrypted in transit and at rest. Access is scoped to the company that owns it, and our tests fail the build if a query that should be company-scoped is not. Credentials are held as managed secrets, never in the codebase.
Changes, and how to reach us
If we change this page in a way that materially affects you, we will say so here and date it rather than editing quietly. Questions, requests and complaints: hello@fasmac.co.