Privacy
Our commitment to privacy is built on these 10 foundations
Authenticate, not recognize. Verify, not identify.
That’s the difference between the Rock and facial recognition.
Facial recognition systems are designed to identify people — even if they never agreed to be scanned — and often connect that identity to names, photos, or other personal details. That’s what enables surveillance, tracking, and profiling.
The Rock is different. It only authenticates people who have opted in and enrolled.
Your face is then matched to a one-way encrypted Facial Signature stored securely on the Rock device itself — not in the cloud by default.
Enrolled + Face (converted to 0s and 1s) + Badge numbers = Authenticated, and the door unlocks. Not Enrolled = Ignored, and the door stays locked.
The Rock simply checks: Are you enrolled? Are you really you? If yes, it tells the access control system to unlock the door.Quick. Private. Secure.
Facial recognition systems are designed to identify people — even if they never agreed to be scanned — and often connect that identity to names, photos, or other personal details. That’s what enables surveillance, tracking, and profiling.
The Rock is different. It only authenticates people who have opted in and enrolled.
Your face is then matched to a one-way encrypted Facial Signature stored securely on the Rock device itself — not in the cloud by default.
Enrolled + Face (converted to 0s and 1s) + Badge numbers = Authenticated, and the door unlocks. Not Enrolled = Ignored, and the door stays locked.
The Rock simply checks: Are you enrolled? Are you really you? If yes, it tells the access control system to unlock the door.Quick. Private. Secure.
What the Rock DOES?
- Authenticate enrolled users only.
- Require explicit consent before enrollment.
- Store Facial Signatures, not photos.
- Match locally on the device.
- Tie Facial Signatures to badge numbers, not names.
- Use AES-256 encryption in storage and TLS in transit.
- Support liveness detection.
What the Rock DOES NOT?
- Identify strangers or mine public images.
- Track mood, behavior, or personal habits.
- Send biometric data to third parties.
- Sell, share, or aggregate biometric data
- Operate without consent.
- Let Alcatraz “spy” on you.
We built the Rock to do one thing — authenticate the right person at the right door — and to do it better than anyone else.
Authenticate, Don’t Recognize FAQs
Authenticate, Don’t Recognize FAQs
Q: How is authentication different from facial recognition?
Authentication checks if you are who you say you are — only if you’ve opted in and enrolled. Facial recognition tries to identify people, even if they never agreed, and often links them to names, photos, or personal details. The Rock is built for authentication only.
Q: Does the Rock scan everyone who walks by?
No. If you aren’t enrolled, the Rock ignores you. It won’t create a profile, capture a photo, or try to figure out who you are.
Q: Could my employer or Alcatraz use the Rock to track me around the building?
Not without tying it into the building’s access control system — and even then, it can only log door events, not continuous location tracking. By design, the Rock cannot run in “surveillance mode.”
Q: Does the Rock store my face as a picture?
No. Your face is converted into a one-way encrypted Facial Signature (a long string of numbers). The photo is deleted instantly. That Facial Signature is stored only on the Rock, paired with your badge number — not your name.
Q: Could hackers get my photo or personal info from the Rock?
No. Even if someone broke through AES-256 encryption (which is virtually impossible), all they’d see is an encrypted string of numbers. There are no photos, names, or unencrypted biometrics to steal.
Q: Can the Rock be hacked to do “bad” things like public surveillance?
No. It’s built so those misuses aren’t even possible. The Rock can’t scan random people, search public databases, or identify strangers — even if someone wanted it to.
Consent comes first.
Enrollment into the Rock is always opt-in. It can’t happen without your permission — ever. Your facial signature isn’t just another photo; it’s a unique biometric marker. We treat it like it’s yours, because it is.
Consent isn’t just a policy. It’s baked into the technology. The Rock can’t create a Facial Signature for you until your Solution Owner (employer or building operator) has confirmed you’ve said “yes” to enrollment. That confirmation happens through their own systems — whether that’s part of new-hire onboarding, visitor registration, or another internal process.
From a technical standpoint, here’s how it works:
Consent isn’t just a policy. It’s baked into the technology. The Rock can’t create a Facial Signature for you until your Solution Owner (employer or building operator) has confirmed you’ve said “yes” to enrollment. That confirmation happens through their own systems — whether that’s part of new-hire onboarding, visitor registration, or another internal process.
From a technical standpoint, here’s how it works:
- No “silent” enrollment – The Rock will not capture or store your face until the Solution Owner’s system gives it an explicit “go.”
- Access Control System (ACS) safeguard – The ACS integration ensures consent is confirmed before the enrollment process can even start.
- Optional DocuSign consent – If the Solution Owner uses our consent module, you’ll be shown a clear consent form before any data capture.
- One-way only – Once you’re enrolled, your face is converted to an encrypted Facial Signature, and the image is deleted immediately.
This design means there’s no “default” or automatic enrollment, no secret image capture, and no way to bypass the consent step.
So how does this work in practice?
So how does this work in practice?
- New Employee? Consent comes first. You join a company using the Rock for secure entry. Before you can walk up and be recognized, you’ll be asked to complete the enrollment process — either in person or through a secure web link. If you don’t agree, the process stops there.
- Contractor or Visitor? Consent comes first. Even if you’re on-site for just a week, the same rule applies. You can’t be scanned into the system without saying “yes” to enrollment.
- Changed Your Mind? Consent comes first. If you previously gave consent but later withdraw it, your Solution Owner can delete your facial signature from the Rock. Once removed, you’ll no longer be recognized — you’ll need another way to access the building.
There’s nothing to match without your enrollment, and the door stays shut.
Consent Comes First FAQs
Consent Comes First FAQs
Q: Can the Rock enroll me without my permission?
No. Enrollment into the Rock is always opt-in. It can’t happen without your explicit consent. If you don’t agree to enrollment, the process stops, and the Rock will never recognize you.
Q: What exactly am I consenting to?
Generally, you’re consenting to have your face scanned and converted into a one-way encrypted facial signature. This signature is paired with an anonymous badge number — not your name, photo, or personal details — and stored securely on the Rock and/or your Solution Owner’s system.
Q: What happens if I don’t consent?
If you don’t enroll, the Rock has nothing to match when you walk up to it. That means it won’t unlock the door for you, and you’ll need to use another form of access, like a badge or PIN.
Q: Does the Rock take a picture of me if I haven’t enrolled?
No. If you are not enrolled, the Rock does not capture or store any image of you. It only “looks” to see if you are in its authorized user list, and if not, it moves on.
Q: Can I withdraw my consent later?
Yes. If you change your mind, you can contact your Solution Owner (your employer or building operator) and request removal from the system. Once your facial signature is deleted, you will no longer be recognized by the Rock.
Q: Who decides how enrollment works?
Your Solution Owner sets the process — whether it’s in person enrollment, secure web-based enrollment, or another approved method. But in every case, consent is required before enrollment can happen.
Q: Does Alcatraz store or control my personal information?
Your Solution Owner sets the process — whether it’s in person enrollment, secure web-based enrollment, or another approved method. But in every case, consent is required before enrollment can happen.
Collect less
Many systems vacuum up far more personal data than they need — full names, birthdates, ID numbers, even raw images- and then store them all together in a single place. That’s a recipe for privacy risk.
The Rock was built on the opposite principle: Only collect the minimum data necessary to verify that you are you, in that moment, for that door. We do this by separating biometric templates (Facial Signatures) from personal identifiers and storing only an anonymous badge number with your encrypted Facial Signature. No names, no emails, no raw photos, and nothing we could use to “look you up.”
This minimal-collection design means there’s no central vault of personal details waiting to be hacked. Even if someone got access to the Rock’s encrypted files, all they would find is a jumble of one-way encrypted templates paired with anonymous numbers — not something they can reverse-engineer into a usable identity.
Collecting less also reduces legal and compliance headaches for Solution Owners. By keeping personal identifiers out of our system, we make it easier for them to comply with privacy laws like Texas CUBI, Illinois BIPA, California CCPA/CPRA, and Europe’s GDPR — and we do it in a way that’s future-proof, ready for privacy rules that haven’t even been passed yet.
Collect Less FAQs
The Rock was built on the opposite principle: Only collect the minimum data necessary to verify that you are you, in that moment, for that door. We do this by separating biometric templates (Facial Signatures) from personal identifiers and storing only an anonymous badge number with your encrypted Facial Signature. No names, no emails, no raw photos, and nothing we could use to “look you up.”
This minimal-collection design means there’s no central vault of personal details waiting to be hacked. Even if someone got access to the Rock’s encrypted files, all they would find is a jumble of one-way encrypted templates paired with anonymous numbers — not something they can reverse-engineer into a usable identity.
Collecting less also reduces legal and compliance headaches for Solution Owners. By keeping personal identifiers out of our system, we make it easier for them to comply with privacy laws like Texas CUBI, Illinois BIPA, California CCPA/CPRA, and Europe’s GDPR — and we do it in a way that’s future-proof, ready for privacy rules that haven’t even been passed yet.
Collect Less FAQs
Q: What does “Collect Less” mean?
It means the Rock only gathers the minimum information needed to verify you and open the door — nothing extra. We don’t keep your name, email, Social Security number, or other personal identifiers in the Rock’s database. Instead, we store a one-way encrypted Facial Signature paired with an anonymous badge number.
Q: Why don’t you store my name or other details with my Facial Signature?
Keeping personal identifiers separate from biometric templates adds an extra layer of protection. If someone ever got access to the Rock’s data, all they’d see is something like: 00110111001010101100011100001010101111000101011000011010... (and it goes on for a long, long time) — not “Jenny Smith” or “Employee #8675309.”
Q: Why not just store names and photos like other systems do?
Because extra data means extra risk. Our approach is simple: If the Rock doesn’t need it to verify you, it doesn’t collect it. That way, there’s nothing extra to lose, leak, or misuse.
Q: Does collecting less still meet legal requirements?
Yes. In fact, it often makes compliance easier. By minimizing the amount of personal data we store, we help Solution Owners meet the strict requirements of Texas CUBI, Illinois BIPA, California CCPA/CPRA, the EU’s GDPR, and other privacy laws — even in jurisdictions where they don’t currently operate. This forward-thinking approach helps Solution Owners avoid costly redesigns when new laws pass.
Q: What does “anonymous badge number” really mean?
When you’re enrolled, the access control system assigns you a random badge number. The Rock pairs that number with your encrypted Facial Signature. Without access to the Solution Owner’s system, there’s no way to figure out who you are from that number alone.
No hidden uses
The Rock is built with one purpose:
To verify you quickly and securely—nothing else.
To verify you quickly and securely—nothing else.
- Focused by design. Every feature is designed for physical access authentication. We don’t add secret capabilities, and nothing operates outside the scope of that mission.
- No side hustle for your data. We never use biometric information for marketing, AI training, or unrelated analytics—and we don’t ask to.Clear and open. We publish how the Rock works in our Privacy Policy and technical docs, so there are no surprises.
- Built to protect, not to pry. The Rock stores only a one-way encrypted Facial Signature paired with an anonymous badge number. Without the Solution Owner’s separate access control records, that code can’t be connected to your name, photo, or personal details.
- Limits that work both ways. Even the Solution Owner can’t use the Rock by itself to identify you or track your movements—because the solution doesn’t have that information.
- We never sell your data. Not now. Not ever.
By keeping the Rock’s purpose narrow, its protections strong, and its operations transparent, we make sure your biometric data is never a liability, only a key to getting where you need to go.
No Hidden Uses FAQs
No Hidden Uses FAQs
Q: Does the Rock secretly record or watch me?
No. The Rock only captures the data it needs for biometric authentication in that moment—then either confirms or denies access. It is not a surveillance camera, it does not “watch” you after you walk through the door, and it does not run unrelated analytics in the background.
Q: What exactly is stored on the Rock?
A one-way encrypted facial signature paired with an anonymous badge number. That’s it. The facial signature is a proprietary code that can’t be turned back into a photo of you. Without the Solution Owner’s separate access control records, that code has no name, no email, no personal details.
Q: Can Alcatraz identify me if law enforcement or anyone else asks?
No. Even if a subpoena demanded “Jenny Smith’s” entry history, we couldn’t produce it. The Rock doesn’t store names or photos—just that encrypted facial signature and anonymous badge number. Without the Solution Owner’s access control data, we couldn’t connect it to a person.
Q: Can the Solution Owner use the Rock to track me everywhere?
Not with the Rock alone. They would need to match the Rock’s anonymous badge number with their own access control logs. The Rock is designed so that it cannot be used as a stand-alone tracking tool.
Q: Does Alcatraz ever sell my data?
No. Not now, not ever. We don’t sell biometric information, and we don’t use it for marketing, AI training, or product analytics.
Q: Where can I read more about how my data is handled?
You can review our full Privacy Policy, which explains in plain language how the Rock works, what data is collected, and the protections in place.
Encrypt everything
At Alcatraz, encryption isn’t a bolt-on feature — it’s baked into every step of the Rock’s privacy-first design.
From the moment you enroll, your face is transformed into an encrypted mathematical template using a proprietary algorithm that blends your facial measurements with organization-specific cryptographic keys (your “Facial Signature”). This is a one-way derivation — the result can never be turned back into a photo.
The original image is processed in memory for only a long enough time to create the Facial Signature, and then it’s instantly discarded. What remains is stored locally on the Rock and linked only to a badge ID — no names, emails, or other personal identifiers. That encrypted template is shared securely with other Rocks in your organization so you enroll once and can authenticate anywhere you’re authorized. Every transfer is protected by TLS 1.2/1.3 and every stored file by AES-256 encryption. And no identity-linked information is passed to Alcatraz via API or other system integration, preventing unauthorized or accidental correlation between biometrics and personal data.
If an encrypted template were intercepted, it would be meaningless without your organization’s unique cryptographic keys. The Rock’s security model makes the data useless outside your system, ensuring that your biometric data stays yours.
Encrypt Everything FAQs
From the moment you enroll, your face is transformed into an encrypted mathematical template using a proprietary algorithm that blends your facial measurements with organization-specific cryptographic keys (your “Facial Signature”). This is a one-way derivation — the result can never be turned back into a photo.
The original image is processed in memory for only a long enough time to create the Facial Signature, and then it’s instantly discarded. What remains is stored locally on the Rock and linked only to a badge ID — no names, emails, or other personal identifiers. That encrypted template is shared securely with other Rocks in your organization so you enroll once and can authenticate anywhere you’re authorized. Every transfer is protected by TLS 1.2/1.3 and every stored file by AES-256 encryption. And no identity-linked information is passed to Alcatraz via API or other system integration, preventing unauthorized or accidental correlation between biometrics and personal data.
If an encrypted template were intercepted, it would be meaningless without your organization’s unique cryptographic keys. The Rock’s security model makes the data useless outside your system, ensuring that your biometric data stays yours.
Encrypt Everything FAQs
Q: What exactly happens to my facial scan during enrollment?
The Rock captures your facial geometry, runs it through a proprietary mathematical algorithm, and combines it with organization-specific cryptographic keys to produce a non-reversible biometric template. The original image is processed in memory only and discarded instantly.
Q: Can the biometric template be used to recreate my face?
No. The template is a one-way mathematical derivation, not an image. No method — by us or anyone else — can reverse it into a recognizable face.
Q: Could this template be matched with another company’s database?
No. Templates are bound to your organization’s unique cryptographic environment. Even if another company uses the Rock, their encrypted templates are incompatible.
Q: Why use AES-256 encryption?
AES-256 is a global standard for securing highly sensitive data, used by governments, banks, and security agencies. The “256” refers to the key length, which makes brute-force attacks virtually impossible with current technology. We use AES-256 to protect biometric templates at rest, ensuring that stored data is indecipherable without the correct cryptographic keys.
Q: How is data protected during transmission?
When templates are sent between Rocks or to the platform, they’re encrypted with TLS 1.2 or 1.3 — the same secure transport protocols used in online banking — to protect against interception.
Q: How does one-way encryption differ from two-way encryption?
One-way encryption (hashing) transforms your data into a fixed, unique code that cannot be turned back into the original. The Rock uses one-way encryption so your Facial Signature can be compared for authentication, but never reconstructed into an image. Two-way encryption, like AES-256 or RSA, scrambles data to be decrypted later with the right key — useful for documents or messages, but not appropriate for storing Facial Signatures.
Analogy: One-way encryption is like baking a cake from a recipe — you can’t get the original ingredients back.
Two-way encryption is like locking the ingredients in a container — you can open it later if you have the key.
Two-way encryption is like locking the ingredients in a container — you can open it later if you have the key.
Process on the Rock
Many older biometric systems — from fingerprints to facial recognition cameras — send raw or partially processed images to a central server for verification. They may store them alongside names and other personal details, and often rely on outdated, unencrypted protocols. That’s an open invitation to hackers.
The Rock works differently. Our algorithm runs right on the device at the door, using your encrypted Facial Signature stored locally. The decision is made instantly, without sending raw images or personal details anywhere — not to our cloud, your employer’s corporate servers, or any third-party provider. Even if someone could break through AES-256 encryption, there’s nothing in transit to steal.
Imagine you’re in Dallas, Texas, about to enter a secure room. With older systems, your face scan might travel across the internet to a remote server, introducing delay and risk at every hop. With the Rock, verification happens at that door — the data never leaves the device during authentication. That means a hacker intercepting transmissions wouldn’t get a photo, a name, or any unencrypted data.
The Rock works differently. Our algorithm runs right on the device at the door, using your encrypted Facial Signature stored locally. The decision is made instantly, without sending raw images or personal details anywhere — not to our cloud, your employer’s corporate servers, or any third-party provider. Even if someone could break through AES-256 encryption, there’s nothing in transit to steal.
Imagine you’re in Dallas, Texas, about to enter a secure room. With older systems, your face scan might travel across the internet to a remote server, introducing delay and risk at every hop. With the Rock, verification happens at that door — the data never leaves the device during authentication. That means a hacker intercepting transmissions wouldn’t get a photo, a name, or any unencrypted data.
Legacy Biometric Systems
- Sends raw or partially processed images over a network to remote servers.
- Often stores names, photos, and other personal identifiers alongside biometric data.
- Vulnerable to network interception and outdated protocols.
- Central servers can be a single point of failure or attack.
- Verification speed can depend on network conditions.
The Rock
- Processes facial authentication locally on-device.
- Stores only encrypted Facial Signatures, with no attached personal identifiers.
- No biometric data in transit during authentication;
- AES-256 encryption at rest, TLS 1.2/1.3 in transit (when needed).No cloud dependency for authentication — even in a cloud-managed environment.
- Instant verification at the door.
When you combine on-device processing with our encryption approach, you get a closed security loop. Biometric templates never travel the network during authentication, and even the data stored locally is locked with AES-256 encryption. This drastically reduces your attack surface compared to legacy systems that transmit or store raw biometric images. Processing on the Rock isn’t just about speed — it’s about cutting out unnecessary risk from the ground up.
Process on the Rock FAQs
Process on the Rock FAQs
Q: Why is processing on the Rock more secure than other systems?
Many older biometric systems — from fingerprints to facial recognition cameras — send raw or partially processed images to a central server for verification. They may store those images alongside names and other personal details, often relying on outdated or unencrypted protocols. That’s an open invitation to hackers.
The Rock does it differently. Your authentication happens entirely on the device at the door. No raw images, no personal details, and no unencrypted data are ever sent across the network. Even if your employer uses our cloud service, your Facial Signature doesn’t leave the Rock during authentication.
The Rock does it differently. Your authentication happens entirely on the device at the door. No raw images, no personal details, and no unencrypted data are ever sent across the network. Even if your employer uses our cloud service, your Facial Signature doesn’t leave the Rock during authentication.
Q: What information does the Rock store about me?
The Rock uses a proprietary algorithm to convert your facial geometry into a one-way encrypted template and pairs it with an anonymous badge number. No names, no emails, and no photos are stored.
So, when you walk through the door, you’re not “Jenny Smith” or “Employee 8675309” to the Rock — you look like:
0011001100010011111000001100101010111010001110100010110000100111010111000100101000110101...
…and that string goes on for a long, long time. It can’t be reverse engineered into a face, and it’s meaningless outside the Rock’s internal matching process.
So, when you walk through the door, you’re not “Jenny Smith” or “Employee 8675309” to the Rock — you look like:
0011001100010011111000001100101010111010001110100010110000100111010111000100101000110101...
…and that string goes on for a long, long time. It can’t be reverse engineered into a face, and it’s meaningless outside the Rock’s internal matching process.
Q: Does the Rock ever send my biometric data to the cloud?
No. Authentication decisions are made locally on the Rock, right at the door. Even in our cloud-managed deployments, only anonymous badge numbers and event logs are sent to the cloud — never your biometric template.
Q: What if someone hacks the transmission from the Rock to the access control system?
First, there’s almost nothing to steal. The Rock only transmits an encrypted badge number to the access control panel. That number by itself is useless without the matching template stored locally on the Rock. And for systems using the latest OSTP protocol, even that communication is encrypted end-to-end.
Q: Why don’t legacy biometric systems do this?
Legacy systems often rely on a “central brain” — sending all biometric data to a server for verification. That creates multiple points of vulnerability:
• Data in transit can be intercepted.
• Centralized databases can be hacked.
• Personal identifiers can be exposed alongside biometrics.
With the Rock, there’s no central biometric database to hack, and nothing sensitive travels across the network during authentication.
• Data in transit can be intercepted.
• Centralized databases can be hacked.
• Personal identifiers can be exposed alongside biometrics.
With the Rock, there’s no central biometric database to hack, and nothing sensitive travels across the network during authentication.
Limit Retention FAQs
Many older biometric systems — from fingerprints to facial recognition cameras — send raw or partially processed images to a central server for verification. They may store them alongside names and other personal details, and often rely on outdated, unencrypted protocols. That’s an open invitation to hackers.
The Rock works differently. Our algorithm runs right on the device at the door, using your encrypted Facial Signature stored locally. The decision is made instantly, without sending raw images or personal details anywhere — not to our cloud, your employer’s corporate servers, or any third-party provider. Even if someone could break through AES-256 encryption, there’s nothing in transit to steal.
Imagine you’re in Dallas, Texas, about to enter a secure room. With older systems, your face scan might travel across the internet to a remote server, introducing delay and risk at every hop. With the Rock, verification happens at that door — the data never leaves the device during authentication. That means a hacker intercepting transmissions wouldn’t get a photo, a name, or any unencrypted data.
The Rock works differently. Our algorithm runs right on the device at the door, using your encrypted Facial Signature stored locally. The decision is made instantly, without sending raw images or personal details anywhere — not to our cloud, your employer’s corporate servers, or any third-party provider. Even if someone could break through AES-256 encryption, there’s nothing in transit to steal.
Imagine you’re in Dallas, Texas, about to enter a secure room. With older systems, your face scan might travel across the internet to a remote server, introducing delay and risk at every hop. With the Rock, verification happens at that door — the data never leaves the device during authentication. That means a hacker intercepting transmissions wouldn’t get a photo, a name, or any unencrypted data.
Q: Where is my Facial Signature stored?
It’s stored securely on the Rock device itself, not in the cloud by default. The Signature is encrypted using AES-256, tied only to a badge number, and never to your name or photo unless your Solution Owner chooses to link them in their own access control system
Q: What are the state retention laws relating to biometrics?
Below are examples of biometric retention rules in different jurisdictions. Your Solution Owner (employer or building operator) is responsible for setting a retention policy that meets these rules and matches their access control system’s retention schedule.
Jurisdiction
Retention Requirement
Illinois (BIPA)
Must have a public retention & destruction policy. Destroy biometric identifiers
Texas (CUBI)
Must destroy biometric data within a “reasonable time,” and no later than 1 year after the purpose for collection ends.
Washington (RCW 19.375)
Must give notice/consent for enrollment (with limited security-purpose carve-outs) and retain data no longer than reasonably necessary for the stated purpose, fraud prevention, or legal compliance.
California (CPRA)
No biometric-specific timeline, but sensitive data can only be kept if reasonably necessary and proportionate to the disclosed purpose. Retention periods (or criteria) must be disclosed at collection.
Colorado (CPA + HB 24-1130)
No biometric-specific timeline, but sensitive data can only be kept if reasonably necessary and proportionate to the disclosed purpose. Retention periods (or criteria) must be disclosed at collection.
GDPR (EU)
Treats biometric data for unique identification as “special category” data. Must limit retention, assist in compliance, and delete as soon as it’s no longer necessary for the stated purpose.
Q: What does “the purpose” refer to when laws talk about destroying biometric data once it's no longer needed?
In these laws, “the purpose” is the specific reason biometric data is being collected. It typically means the operational need for access control or identity verification. Once that reason no longer exists, such as an employee leaving or a job role changing, the biometric data must be destroyed within a legally defined timeframe.
We don’t own the data
We Don’t Own the Data…
So We Don’t Act Like We DoSome companies treat the data their products collect like it’s theirs to keep, mine, or monetize. We don’t.
When you use the Rock, the biometric data belongs to the Solution Owner — the business, building, or organization that installed it. We built the Rock to respect that boundary in both technology and practice.
That means:
So We Don’t Act Like We DoSome companies treat the data their products collect like it’s theirs to keep, mine, or monetize. We don’t.
When you use the Rock, the biometric data belongs to the Solution Owner — the business, building, or organization that installed it. We built the Rock to respect that boundary in both technology and practice.
That means:
- We can’t pull up your profile. The Rock stores a one-way encrypted mathematical template paired with an anonymous badge number — no name, no photo, no personal record we could “look up.”
- We never use it for anything else. Biometric data collected by the Rock is used only to authenticate you for access. It’s never repurposed for marketing, product training, analytics, or any other secondary use — and we don’t ask Solution Owners for permission to do so.
- We can’t hand it over. Even if asked, we have nothing useful to give a third party because we don’t hold your raw biometric data.
- We never sell your data. Not now, not ever. Selling personal data isn’t part of our business model — and never will be.
If you want to change, delete, or access data about you, you’ll need to contact the Solution Owner directly. They have full control over their Rock system and all associated data — and only they can act on those requests.
By not owning your data, we avoid the temptation (and the risk) of acting like we do. It keeps our focus where it should be: Making the most secure, privacy-first access control technology possible.
By not owning your data, we avoid the temptation (and the risk) of acting like we do. It keeps our focus where it should be: Making the most secure, privacy-first access control technology possible.
Data Ownership FAQs
Q: Does Alcatraz know who I am?
No. The Rock doesn’t store your name, photo, or other personal identifiers in a way we can “look you up.” It stores a one-way encrypted mathematical template of your face, paired with an anonymous badge number, and that record belongs to your employer (the Solution Owner).
Q: If I want my data deleted, can I contact Alcatraz directly?
No. Because Alcatraz doesn’t own or control your biometric data, we cannot access or delete it. You’ll need to contact your employer or the organization that owns the Rock system you use. They are the data controller and have the tools to act on your request.
Q: What does “We don’t own your data” really mean?
It means we designed the Rock so that biometric data stays with the Solution Owner — and we can’t use it for anything beyond authenticating you for access. We never repurpose, mine, or monetize that data.
Q: Could Alcatraz sell my biometric data?
No. We do not use biometric data collected by the Rock for product development, marketing, analytics, or AI training. We don’t even ask Solution Owners for permission to do this.
Q: If law enforcement asked Alcatraz for my biometric data, could you hand it over?
No. Because we don’t own or store raw biometric data tied to your identity, we have nothing meaningful to give. Any such request would need to go directly to the Solution Owner, who controls the system.
One system, one purpose
In many biometric systems, templates are portable. A facial scan enrolled in one building can be copied to a different site, uploaded to a central database, or even searched against unrelated datasets. That portability can make it easier for the bad stuff to happen:
- Surveillance creep. Using the same template to track someone across multiple locations without new consent.
- Data spillover. A breach in one system could expose biometric templates for use in another.
- Mission drift. Templates end up being used for purposes far from their original intent, sometimes without the person’s knowledge.
Even biometric vendors that promise not to misuse data can’t always stop a system owner from doing so if the technology itself makes cross-system sharing possible.That’s why the Rock’s Face Signatures are cryptographically tied to a single, specific Alcatraz AI Solution Owner’s environment. They cannot be exported, shared, or reused in another customer’s system — and there’s no “master database” to pull from. That means:
- A Face Signature from Building A cannot work in Building B unless it’s re-enrolled with fresh consent.
- A breach in one deployment has no effect on any other deployment.
- There’s no way to silently connect the dots between different systems.
We designed the Rock this way on purpose: To eliminate the risks of cross-system abuse before they start.
One system. One purpose.Are you enrolled? Are you really you? If yes, unlock the door.
One system. One purpose.Are you enrolled? Are you really you? If yes, unlock the door.
One System. One Purpose. FAQs
Q: What is “cross-system use” in biometrics?
Cross-system use means taking someone’s biometric template — like a Facial Signature — from one system and using it somewhere else. That could mean importing it into a different deployment, sharing it with another company, or running it against a bigger shared database. It’s essentially reusing the same biometric data across unrelated systems.
Q: Why is cross-system use a privacy concern?
Because it can enable tracking, profiling, or surveillance without a person’s knowledge or fresh consent, if your template works in multiple places, you can be recognized and logged across them — even if you never agreed to that in the first place.
Q: What do privacy laws say about it?
• Illinois (BIPA): You can’t share, disclose, or reuse biometric identifiers for another purpose or in another system without new, informed written consent. Each use must be disclosed with its specific purpose and retention period.
• Texas (CUBI): Limits biometric use to the purposes specified in the consent given; new purposes require new consent.
• California (CPRA): Restricts sensitive data (including biometrics) to disclosed, compatible uses. Profiling, identification, or system expansion must be disclosed and subject to opt-out or consent.
• Texas (CUBI): Limits biometric use to the purposes specified in the consent given; new purposes require new consent.
• California (CPRA): Restricts sensitive data (including biometrics) to disclosed, compatible uses. Profiling, identification, or system expansion must be disclosed and subject to opt-out or consent.
Q: How do other biometric systems handle cross-system use?
Many are built to allow it — so even if their policy says they won’t, the technology makes it possible to import or share templates. That means your privacy depends on policy, not system architecture.
Q: How does Alcatraz handle it?
We don’t allow it, period. Your Facial Signature is cryptographically tied to one specific Solution Owner’s deployment and can’t be reused elsewhere. If a different system wants to use biometrics, you’d have to enroll again and give fresh consent.
Q: How does blocking cross-system use protect me?
1. Prevents tracking — Nobody can use your template to follow you between sites.
2. Contains breaches — The stolen template won’t work anywhere else if one system is compromised.
3. Stops profiling — No one can piece together your activity across different places without a cross-system database.
2. Contains breaches — The stolen template won’t work anywhere else if one system is compromised.
3. Stops profiling — No one can piece together your activity across different places without a cross-system database.
Q: What if my company has multiple buildings?
Your enrollment works across those doors if they’re on the same access control system (ACS) within the same deployment. Different systems require separate enrollment and consent.
Check ourselves
We don’t expect you to just take our word for it — we prove it. The Rock and its platform are held to the highest privacy and security standards, and we invite independent experts to verify we meet them. That means our claims aren’t just marketing copy. They’re tested, measured, and validated.
Independent Technical Testing
Our facial authentication algorithm has been rigorously evaluated by the National Institute of Standards and Technology (NIST), the U.S. government’s gold standard for biometric system testing. NIST confirmed our high accuracy and the negligible risk of misidentification across all demographics.In addition, the Rock’s hardware and software have earned globally recognized certifications from the International Organization for Standardization (ISO), including ISO 27001, ISO 27017, and ISO 27018 — benchmarks for information security, cloud security, and personal data protection.
Expert Legal Oversight
We also invest heavily in ongoing reviews from leading data privacy lawyers. These specialists focus on some of the strictest privacy laws in the world — including the General Data Protection Regulation (GDPR), California Consumer Privacy Act and California Privacy Rights Act (CCPA/CPRA), Illinois Biometric Information Privacy Act (BIPA), and Texas’s Capture or Use of Biometric Identifier Act (CUBI). They guide us in embedding Privacy by Design into every Rock, reviewing product features for legal compliance, running Data Protection Impact Assessments, and helping ensure our consent flows and policies meet — and often exceed — these legal standards. We are built to comply even if we don’t currently operate in a particular jurisdiction. This forward-thinking approach keeps the Rock ready for the future and compliant wherever our customers do business.
Continuous Accountability
Our certifications aren’t one-time achievements. We maintain them through regular audits, fresh rounds of testing, and constant legal review. If technology evolves or privacy laws change, we adapt quickly — guided by experts who keep us accountable.
Bottom line: Privacy at Alcatraz isn’t just a promise. It’s a proven, verifiable standard we test and retest with the most credible voices in the field — technical, legal, and operational.
How We Check Ourselves FAQs
Q: Who checks your privacy and security claims?
In addition to our internal Rockstars, we undergo testing by independent, respected organizations like the National Institute of Standards and Technology (NIST) and maintain ISO 27001, ISO 27017, and ISO 27018 certifications. These outside evaluations confirm that our security and privacy protections meet — and often exceed — global standards.
Q: Do you meet all privacy laws?
Yes — including GDPR, CCPA/CPRA, BIPA, and Texas CUBI. Even in regions where these laws aren’t in effect, the Rock is built to comply from day one.
Q: What if a law changes or a new one passes?
We don’t wait to be caught off guard. Alcatraz is a proud member of the Security Industry Association (SIA), which keeps us plugged into legislative and regulatory developments as they happen. Our dedicated privacy counsel and officers are privacy law nerds — they track proposed rules and bills before they even reach the House floor. This means we’re already planning and adapting the Rock to stay compliant well before new requirements take effect, no matter where in the world they originate.
Q: Can I see the results of your testing?
While we can’t share all technical details for security reasons, certification status is public, and we provide summaries of our compliance upon request.
Q: Are these tests ongoing?
Yes. We re-certify and retest regularly, ensuring our privacy and security protections stay current.
Disclaimer:
This page explains how the Alcatraz Rock Solution works, especially around privacy and security. It’s not legal advice and reading it doesn’t create a lawyer-client relationship with Alcatraz. Check with your HR or legal team for legal questions about your workplace policies. We work to keep this info current, but details may change, and we may link to sites we don’t control. Have a question you think we should cover in our FAQs? We’d love to hear it — email privacy@alcatraz.ai.