Skip to content
AttendSure
Home/Security & Privacy

Privacy & security

Your data is protected.
By design.

AttendSure watches camera status, shows you the live session and records Presence Check replies - and records none of your meeting video or audio. Privacy by design, and security practices that protect your organisation’s data and every participant in the room.

No card needed. Cancel anytime.
Data encrypted
TLS in transit. Zoom tokens encrypted at rest with AES-256-GCM.
Infrastructure
Hosted on secure cloud infrastructure.
Access control
Role-based access: Owner, Admin, Member.
Password & session security
Passwords hashed with bcrypt. Sessions are random tokens, stored only as SHA-256 hashes.
Data residency
Hosted on secure cloud infrastructure. We will tell you where your organisation’s data is held on request - see our Privacy Policy, or contact us.

Built on trust. Backed by real practices.

No badges to take on faith - here is exactly how AttendSure protects your data.

Encryption in transit, and for secrets at rest
All traffic is encrypted with TLS. Zoom access and refresh tokens, and any meeting passcode you save, are encrypted at rest with AES-256-GCM.
Password & session security
Passwords are hashed with bcrypt. Sessions are random tokens, stored only as SHA-256 hashes - never in plain text.
Organisation-scoped data
Application queries are scoped to one organisation. Two things sit outside that by design: a certificate verification link, which answers anyone holding it, and our own support console - see below.
Role-based access
Owner, Admin and Member roles control who can change things: deleting sessions, inviting or removing people, and billing are restricted to Owners and Admins. Reading and exporting session reports is available to every member of your organisation - the data is scoped to the organisation, not to the individual.
Configurable retention
Session records are removed automatically once they pass your organisation's retention period. Certificates you issue are the exception - a document someone may already hold a copy of is kept until the organisation is deleted. Withdrawing one marks it invalid rather than erasing it.

What we do (and don't)
do with your data

Full transparency on exactly how AttendSure handles information from your sessions.

We do
Monitor camera on/off status, with timestamps
Show the live session to authorised users in Live View, without storing it
Send Presence Checks and record whether each was confirmed, missed or exempt
Use that data to generate reports, evidence and alerts
Protect data with encryption and access controls
Let you export or delete your data, from your account settings
We don't
Record or store video - Live View shows the session live, and keeps none of it
Record or store audio
Transcribe or analyse conversations
Use facial recognition, expression analysis or biometric identification
Claim a participant was continuously attentive
Sell or use your data for advertising

On Microsoft Teams and Google Meet, an AttendSure guest joins the meeting through Recall.ai, our independently audited meeting-bot provider, and the host admits it from the lobby. It is set up with no video, audio or transcript recording and with zero retention, so nothing from the meeting is kept by Recall.ai afterwards. It reads the meeting chat only to recognise replies to a Presence Check, and never stores the message text. On Zoom, AttendSure does not read the meeting chat at all. Read the Privacy Policy.

Your meeting
Video
Audio
Meeting chat content
Screen share
Files
Never recorded or stored
What AttendSure monitors
Camera on / off
Timestamps
Participant name
Session info
Alerts & reminders
Presence Checks & response times
Status only, never content

Security at every layer

Encryption
TLS 1.2+ in transit. Zoom access and refresh tokens encrypted at rest with AES-256-GCM.
Secure infrastructure
Hosted on secure, managed cloud infrastructure.
Access controls
Role-based access control over destructive and administrative actions - deleting sessions, managing people and roles, retention and billing. Session reports themselves are visible to everyone in the organisation.
Password hashing
Passwords are hashed with bcrypt and never stored in plain text.
Session security
Sessions are random tokens, stored only as SHA-256 hashes - never as reusable plain-text secrets.
Organisation isolation
Application queries are scoped to one organisation, enforced in the application layer. A certificate verification link is keyed on an unguessable token instead, so it can answer someone with no account; our support console reads across organisations, and every read of customer data it makes is written to an audit log first - if the log cannot be written, the read is refused.
Privacy built in. Accountability proven.
Protect participant privacy while getting the visibility your organisation needs.