Who we are
AI Security Engineering is run, built and funded by Vero Security Inc. (“Vero”, “we”), under a public charter. Vero is the controller of the personal data described here.
For anything on this page, write to privacy@aisecurityengineering.org. We answer within one month.
What we collect, and why
We collect what you type into a form, a few technical items, and, only if you accept analytics cookies, how you use the site.
| What | When | Why | Legal basis |
|---|---|---|---|
| Your work email | Every form, and signing in | To do what you asked: add you to the list, the waitlist or an event, send the hiring kit, sign you in | Doing what you asked (Art. 6(1)(b) GDPR) |
| Your role | Joining, credential waitlists, event registration | To send the right path and plan events | Doing what you asked |
| Your city, optional, and whether you can host | Events and chapters | To count members per city, start chapters and find rooms | Doing what you asked |
| Your security team size | The hiring kit | To understand who uses the kit | Our legitimate interest in improving it |
| The event, project or credential you chose, and a note, optional | Event, project and waitlist forms | To know what you signed up for and read what you wrote | Doing what you asked |
| Your project repository URL | Project submissions | To review the project you built | Doing what you asked |
| Your name as it should appear on a certificate | Claiming a credential | To issue the certificate and its public record | Doing what you asked |
| Community emails you signed up for | The join and newsletter forms, which say “We’ll email you community updates. Unsubscribe anytime.” | To send a welcome email, event invites and the weekly update | Your consent, given by sending one of those forms. Withdraw it any time with the unsubscribe link or by writing to us |
| A record of the notice you saw | Every form | When you sent it, which form, and the exact text shown next to the button, so we can show what you were told and what you agreed to | Our legitimate interest in showing what you were told |
| Company totals: how many people signed up from each email domain | Every form | So Vero can see which companies take part, without seeing who (see the charter) | Our legitimate interest. You can object |
| A keyed hash of your IP address | Every form, and signing in | To limit how often one connection can send a form | Our legitimate interest in stopping abuse |
| Request logs: IP address, browser, page, time | Every page you open | Hosting, security and fixing errors | Our legitimate interest in running a safe site |
| Page counts: pages viewed, referrer, device type, country, with no cookies and nothing that identifies you | Every page | To see which pages people use | Our legitimate interest in improving the site |
| Usage analytics: pages viewed, how you got here, device type, approximate location, and actions such as sending a form or finishing a quiz (never names, emails or what you typed) | Only if you accept analytics cookies | To learn which pages help people and fix the ones that do not | Your consent |
| What you write to us by email | When you email any of our addresses | To answer you and handle reports | Our legitimate interest in answering |
Forms only need your email. Everything else is optional unless the form says so. We never ask for sensitive data, and we do not make automated decisions about you.
We store a keyed hash of your IP address, not the address itself. Our hosting provider’s request logs do hold IP addresses for a short time (see below).
Who handles it
These companies run parts of the site for us, under contracts that limit them to our instructions:
| Company | What it does | Where |
|---|---|---|
| Vercel Inc. | Hosts the site and runs its code; keeps request logs; counts page views without cookies (Web Analytics) | Frankfurt, Germany, with a US parent |
| Neon (Databricks, Inc.) | Database for forms, accounts and saved progress | Frankfurt, Germany, with a US parent |
| HubSpot, Inc. | Keeps a copy of community sign-ups: a contact and a record of each form you sent (email, role, city, which credential waitlist, the form, the page you sent it from, when, and the notice record; we send it no IP address or cookie). Notes, team size, repositories and event choices stay in our database. It also sends community email, in an account used only for this community | EU data centers, with a US parent |
| Google LLC (Google Analytics) | Usage analytics, only after you accept | US and other countries |
| Resend (Plus Five Five, Inc.) | Sends sign-in emails, once sign-in is on | US |
| Slack Technologies, LLC | Posts a notice of each sign-up (email and which form) in a private channel for the community team | US and other countries |
| Google LLC (Google Workspace) | Receives mail sent to our hello@, privacy@, security@ and charter@ addresses and passes it to the few people who run the community | US and other countries |
Two more services see your IP address when your browser loads them: Google Fonts (the site’s fonts) and Wikimedia Commons (some photos).
Inside Vero. The few people who run the site and the community team can see form submissions and the community’s HubSpot account, so they can answer you and keep the site working. Sign-up notices go to a private channel in Vero’s internal Slack that only the community team can see. Vero’s sales team sees company totals only and never names or emails. That is a charter rule, and the HubSpot account above is separate from Vero’s sales systems.
The public. If you earn a credential, its record is public: credential ID, your name, level, lab revision, issue and renewal dates, and status. Nothing else you give us is public.
We do not sell your personal information, and we do not share it for targeted advertising. We may disclose it if the law requires it, or to a buyer if the community changes hands, under the same promises.
Emails we send
- Welcome email, event invites and the weekly update: only if you joined the community or signed up for the newsletter, which is your consent to them. Other forms, such as a credential waitlist, the hiring kit, events, chapters or projects, never add you to these emails.
- Sign-in links: only when you ask for one.
Every community email has an unsubscribe link. Unsubscribing stops them straight away.
Transfers outside Europe
Vero is a US company, and some of the companies above are in the US or have US parents. Where personal data from the EU, EEA, UK or Switzerland goes to the US, we rely on the EU-US Data Privacy Framework (and its UK and Swiss extensions) for companies certified under it, and otherwise on the European Commission’s standard contractual clauses (with the UK addendum). Ask us for a copy of the safeguards at the address above.
How long we keep it
| What | How long |
|---|---|
| Form submissions | 2 years, then deleted, or sooner if you ask |
| Your account and saved progress | Until you ask us to delete it, or 2 years after your last sign-in |
| Public credential records | For as long as the credential is valid, plus its renewal period, unless you ask us to remove it |
| Community sign-ups and form records in HubSpot | Until you unsubscribe or ask us to delete them, and at most 2 years after your last sign-up |
| IP hashes for rate limiting | 30 days |
| Sign-in links | Stored only as a hash; a link works once, for 20 minutes, and is deleted a day after it expires |
| Hosting request logs | As short as Vercel’s logs allow, at most 30 days |
| Google Analytics data | Event data 2 months; data tied to an analytics cookie 14 months after your last visit; totals longer |
| Email to our addresses and conduct reports | As long as we need to handle the matter, then deleted within 2 years |
Cookies and browser storage
Cookies that keep the site working are always on. Analytics cookies are off until you accept them.
| Name | Type | Lasts | What for |
|---|---|---|---|
ase_m |
Needed | 90 days | Keeps you signed in, only if you sign in |
ase_a |
Needed | 8 hours | Admin view, only for the people who run the site |
ase_s |
Needed | 30 days | Remembered the preview password before launch; no longer set |
_ga, _ga_F8PCRNNY9B |
Analytics | 13 months | Google Analytics, only after you accept |
The site also uses your browser’s local storage, under keys that start with ase:, for your roadmap and field map progress, checklists and quiz answers. That stays in your browser and never reaches us, unless you sign in, in which case we save your progress to your account so it follows you to other devices. We also remember your cookie choice in your browser (ase:consent). Until you accept, no Google Analytics code loads at all. Google signals and ad personalisation are off.
To change your choice, use Cookie choices at the bottom of any page. Clearing this site’s data in your browser removes everything stored there.
Your rights
Depending on where you live, you can ask us to:
- see the data we hold about you and get a copy, including in a reusable format;
- correct it;
- delete it. We delete your form submissions, account, saved progress, and your contact and form records in HubSpot. If you hold a credential, tell us whether to remove its public record too;
- restrict how we use it while we look into a complaint;
- object to uses based on our legitimate interest, including being counted in company totals;
- withdraw consent at any time, for analytics through Cookie choices and for email through the unsubscribe link. This does not affect what we did before.
Write to privacy@aisecurityengineering.org, ideally from the email you used. We may ask you to confirm the address is yours. We answer within one month, and tell you if we need longer for a complex request.
If you are unhappy with our answer, you can complain to your data protection authority: in the EU, the one where you live or work; in the UK, the Information Commissioner’s Office. We would like the chance to fix it first.
California residents have the rights to know, delete and correct personal information, and to not be treated differently for using them. We do not sell or share personal information and do not use sensitive personal information. The categories we collect are the ones in the first table above.
Security
Data travels over HTTPS. Database and admin access is limited to the people who run the site. Sign-in links and IP addresses are stored only as hashes. No system is perfectly secure; if a breach affects you, we will tell you as the law requires. Report a security problem to security@aisecurityengineering.org.
Children
This site is for working professionals. It is not meant for anyone under 16, and we do not knowingly collect their data.
Changes to this policy
When this policy changes, we update it here and change the date at the top. If a change affects how we use data you already gave us, we will tell you by email before it takes effect.