About your data.

Contact, demo and pricing inquiries store your name, organization, email, message and any preferred times or packages so the site owner can follow up.

What is saved in your browser

Your theme and high-contrast preferences are saved locally on your device. The interactive presentation example is temporary and resets on reload. This version does not include analytics or advertising tools.

Account details

Your account holds your name, organization, email and consent. You sign in with Qlave ID, Microsoft or Google; Studio creates no passwords of its own. Accounts from the start of the preview may still have an earlier password stored as a salted hash, but it can no longer be used to sign in. Sign-in uses a session cookie that JavaScript cannot read. Confirmation emails are sent via Microsoft 365.

Signing in with Apple, Google, Microsoft and Qlave ID

When you sign in with Google, Studio asks only for the basic openid, email and profile permissions. It receives your Google account ID, name, email address and whether the address is verified, and uses them only to sign you in and to create or link your Studio account. Signing in gives no access to Gmail, calendar, contacts or files at Google, and Studio keeps no Google tokens from it.

If you connect Google Calendar on the meetings page, Studio also asks to see your calendar list (calendar.calendarlist.readonly) and to see, create, change and delete events in your calendars (calendar.events). If you allow it, Studio can also see when the people you invite are busy (calendar.events.freebusy), and then reads only times, never what the events are about. Studio uses this access only to show your events next to Studio’s meetings and for what you do in Studio yourself: new events, changes, replies to invitations and meetings you choose to link. Studio stores an encrypted refresh token per connected Google account, the calendars’ names, colors and permissions, and your own color and visibility choices. Your events are not stored in Studio. For meetings you create or link from Studio, Studio keeps the event’s ID and the title, description, location, time and attendees you enter, to keep the meeting and the calendar in sync. The data is not sold, not passed on, not used for advertising and not read by people without your consent, except where needed for security or required by law. Qlave Studio’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Disconnecting the account on the meetings page revokes Studio’s access at Google and stops showing the calendars. You can also remove the access under third-party apps in your Google Account.

With Microsoft, Studio asks for the same basic details and also for read access to your Outlook contacts for contact search. If you approve, Studio stores an encrypted refresh token for that feature only. Presence and Teams chat are connected separately, and the permissions can be revoked in your Microsoft account. Qlave ID is Qlave’s own sign-in at id.qlave.se; from it Studio receives your account ID, name, email and organization.

With Apple, Studio receives your Apple account ID, your name the first time you sign in and your email address, or a forwarding address from Apple if you choose to hide it. Studio stores an encrypted token from Apple that is used only to revoke the sign-in when you delete your account.

Deleting your account

You can delete your account yourself under Edit profile on the web or under Your account in the app. The account is deleted immediately: you are signed out everywhere, the sign-ins are disconnected and your profile details are removed. Workspaces where you are the only member are closed. Meetings and documents in other workspaces remain under “Deleted user”.

Inquiries and data questions

To limit abuse, a short-lived hashed network identifier is used for rate limiting. Full operator details, retention periods and the final privacy policy must be established before commercial launch. Do not submit sensitive personal data in the forms.