What data Attensa stores

The data Attensa keeps for your workspace, how long it is kept, and how Google data is protected. The privacy policy is the full legal statement.

Updated October 29, 2026

On this page

Note

This page summarises the privacy and data protection policy. If the two ever differ, the policy is the authoritative statement.

What Attensa stores

Data	What it includes
Account	Your name, email address, profile photo, and Google account ID, from Google sign-in.
Attendance	For meetings organized by the connected Google account: meeting time and code, its Calendar event title, link, and ID, and each participant’s display name and join and leave times. Email addresses and photos are kept where Google provides them.
Workspace	Workspace name, members and roles, invitations, settings, issued certificates, and certificate logos you upload.
Billing	Plan, subscription status, invoices, and the billing details you give Stripe. Card details stay with Stripe.
Support and contact	Messages you send through the contact form or the in-app support window.
Security records	Sign-in sessions, audit events, and request logs used to keep accounts safe.

Meeting audio, video, recordings, chat messages, transcripts, or shared screens.
Your Gmail, your other Drive files, or calendars and contacts beyond what is needed to label and identify meeting attendees.
It never creates, edits, or deletes calendar events, contacts, or meetings.

Google data is not sold, not used for advertising, and not used to train AI models.

Imported attendance and certificates are kept for as long as your workspace keeps them: until you erase an attendee, delete the workspace, or delete your account. Google deletes its own Meet records after about 30 days, so Attensa’s copy is your lasting record.
Your plan limits what is shown, not what is kept. On Basic, older meetings are hidden until you upgrade.
Google tokens are kept until you disconnect Google or delete the workspace, and are revoked at Google then.
Other kinds of data, such as contact messages, support cases, security events, and invoices, have their own retention periods listed in the policy’s retention table.

All traffic is encrypted in transit (HTTPS), and data is encrypted at rest by Attensa’s hosting providers.
Google access and refresh tokens are additionally encrypted by Attensa before they are stored, and are never returned to your browser.
Each workspace sees only its own data.

Signed-in customers can open a request from inside the workspace with Ask Attensa. Otherwise, send us a message and we will reply by email.