Privacy Policy

This Privacy Policy explains how Simplisik LLC (“Simplisik”, “we”, “us”) handles personal information through AtriumKit: the Chrome extension, the dashboard and API at app.atriumkit.com, the demos, guide pages and demo collections we host at atriumkit.com, demos embedded on other websites, and this website (together, the “Services”). It covers AtriumKit only; Simplisik’s other products have their own privacy policies. It is effective as of October 22, 2026. For accounts opened before October 22, 2026, the changes in this version take effect on November 18, 2026, except that what it says about HTML copies, knowledge kits, AI and voice features, personalization and AI assistants applies as soon as you use them.

1. Who we are and our role

AtriumKit is a product of Simplisik LLC, a Tennessee limited liability company based in the Nashville area. Our contact details are in section 16.

• Where we decide: for your account, billing, support, the security of the Services and this website, we decide how information is used. For people in the EEA, the UK and Switzerland, we are the “controller” of that information.
• Where our customers decide: for the content a workspace creates (recordings, HTML copies, demos, guides, voice recordings and the files in its knowledge kits, including information about other people in them, such as its own customers or someone whose voice is in an upload), the people it creates personalized links for, and the information its demos and guides collect from viewers (analytics and leads), we act on behalf of the company that owns the workspace. That company is the controller (or “business”), we are its processor (or “service provider”), and its own privacy policy governs how it uses the information. If you viewed a demo or received a personalized link and have a question about your information, contact the company that shared it. We will help them respond.

2. Information we collect

Information you give us

• Account: your name, email address and password. We store the password only as a salted hash. When you sign up, reset your password or change your email address, we email you a single-use link to confirm the address and store only a hash of it, along with when your address was confirmed.
• Workspace: the workspace name, members and their roles, folders, brand kits (logos, colors, fonts, button and page styles, and the address of a website you import them from), demo collections, and the integrations an admin connects (destination addresses, which we store encrypted, form IDs and a log of recent deliveries). When an admin invites someone, we store the invitee’s email address and role and email them the invitation, with the admin’s name and a reply-to address.
• Knowledge kits: what you tell AtriumKit about your product in a brand kit (its description, audience, voice, glossary, links and notes) and the files you upload to it, such as sales decks and price sheets (see section 5).
• Access tokens and AI assistants: the name, workspace, permissions and expiry you choose for an access token, and the AI assistants you approve, with the name and web addresses each one gives about itself, as described in section 5.
• Billing: plan, billing period, seat count and subscription status. You enter card details on Stripe’s pages and Stripe handles them. When you open the billing page we show the card brand, last four digits and expiry date, and your recent invoices, retrieved from Stripe at that moment. We do not store them.
• Support: what you send us when you contact us, including your name, email address, company and message when you use the contact form on this website (it reaches us by email; we don’t keep a separate copy on our servers).
• Abuse reports: if you report a demo, a guide or a collection page, the reason, any details you add, your email address if you give it, where you reported from and the referring website. Instead of your IP address, we store a keyed hash of it, which lets us spot repeat reports without keeping the address.

Content you create

Recordings and demos: screenshots and HTML copies of the pages you recorded, page addresses and titles, the text and position of elements on those screens, what you typed while recording, tooltip and card copy, the choices and paths in guided demos, guide wording, edits, blur areas, settings, presenter notes, translations, personalization variables, narration scripts, voice recordings and audio uploads with their transcripts and captions, AI settings, and the published versions of your demos. Each demo keeps a version history of its draft, which notes changes made through an AI assistant with the assistant’s or token’s name (see section 11). Pages you record often show information about other people, such as your own customers, and that information becomes part of your content. When you edit a screen, we keep its original capture privately in your workspace so you can change the edit later, and only the edited version appears in your published demo. Section 3 describes what the extension captures in detail.

Personalized links: the label of each link and the details you enter, or map from a spreadsheet you upload, for the person it is for, such as their name, company, job title, email address and other values you define. Columns of a spreadsheet that you don’t map are not uploaded. Every member of the workspace can see links and their details.

Information collected automatically

• Every request to the Services passes through our hosting provider, Cloudflare, which processes your IP address, browser and device details to deliver and protect the Services. Cloudflare keeps operational logs of these requests, including the addresses requested, for a short period (see section 11).
• To limit repeated attempts to sign up, sign in, reset a password, send invitations, submit lead forms, connect AI assistants, report demos or send messages through our contact form, we store your IP address (and, for password resets, the email address entered) for up to two days. We do not store IP addresses with your account, your sessions or demo analytics.
• We record when your sessions were created and last used, so we can keep you signed in and expire old sessions.
• When you use an AI or voice feature, we record who used it, when, which feature, the provider and model, and how much text or audio it processed, to count your workspace’s AI credits and voice allowance. These records do not contain the text sent or the reply, although an error message from the provider can be kept.
• When an access token or a connected AI assistant is used, we record when, and the country it was used from.

This website

The atriumkit.com marketing pages use Google Analytics to count visits and see which pages people find useful. Google receives the page you are on, the page you came from, your browser and device details and your IP address (from which it works out your approximate location). In the European Economic Area, the UK and Switzerland it sets cookies only if you accept them in the cookie banner, and until you choose it receives that information without cookies. Elsewhere it sets its cookies by default. Wherever you are, you can change your choice at any time with Cookie settings at the bottom of every page. If you decline, or your browser sends a Global Privacy Control or Do Not Track signal, Google Analytics does not load at all. Advertising features are off, and these pages use no advertising tools. Fonts on our pages are loaded from Google Fonts (see section 8). If a page shows a live AtriumKit demo, the player collects the analytics described in section 4, for us as the demo’s owner.

3. The Chrome extension

The extension exists to record demos of web apps. This section covers everything it collects.

When it runs

• It does not read the pages you visit until you start a recording, and it stops when you click Done or Discard. If you choose “Whole window”, it records whichever tab you switch to in that window while you record.
• A small script runs on app.atriumkit.com at all times so the dashboard can tell which account the extension is signed in to. It does not read the page.

What it captures while you record

• Screenshots of the tab you record, or of whichever tab is active in the window if you choose “Whole window”.
• An HTML copy of each page, unless you turn on “Screenshots only”: the page’s text and markup, its styles, the images and fonts it shows, the values in its form fields, and frames from the same website. The copy contains no scripts. It covers the whole page, including parts outside the visible window, but not content the page hides completely. To copy images, styles and fonts, the extension downloads them from the websites that host them through your browser, including your sign-in to those websites.
• The page address (including any query string) and title, and the size of the browser window.
• Where you click, and the label, role, link address and position of the element you clicked.
• Visible text on the page with its position and styling, and the labels and link addresses of visible buttons and links, so you can edit them later.
• The value you typed into a field you clicked, and hover states if you turn them on. It does not log individual keystrokes or record mouse movements.

It does not save what is in password fields (an HTML copy shows x’s in their place) or hidden fields, or the values of fields that a website marks as card details or one-time codes using the standard autocomplete attributes (an HTML copy shows placeholder characters). Screenshots, however, show every field as it appears on screen. Fields a website does not mark this way are read like any other field, so record with test accounts and sample data.

Blurring

• Auto-blur is on by default. It covers email addresses, phone numbers, names in profile-like parts of the page, email, phone, name and address fields, and anything a website marks with data-atriumkit-blur. You can turn it off in the extension’s popup (“Auto-blur emails and names”).
• Auto-blur, and any “Blur area” you draw, is applied on your device before anything is saved or uploaded: it pixelates screenshots, and in HTML copies it replaces the text with placeholder characters and blanks the images. The original text and images of those areas are never part of an HTML copy.
• With auto-blur on, when you type into a field that looks personal, the extension saves only what kind of value you typed (for example, a name), not the value itself.
• The page text, link addresses, page titles and typed text described above are uploaded without blurring, including text under blurred areas, and kept privately in your workspace. They are not published, and text under blurred areas is never sent to AI models. The editor uses page titles and typed text to draft screen names and tooltips, which you can change before you publish.
• Auto-blur cannot recognize every kind of personal information (it does not detect card numbers, postal addresses in ordinary text or photos, for example), and an HTML copy includes parts of the page you may not have seen on screen. Review your screens, and use the editor’s blur, hide and edit tools for anything it missed.

Storage, uploads and permissions

• Recorded steps, HTML copies and the images and styles they use stay in the extension’s storage on your device until you upload them, discard them or start a new recording. You can review, remove or discard any step before uploading.
• The extension stores a sign-in token, your name, email address and workspaces, and your recording settings, so it can upload to your workspace. The token expires 180 days after it was last used.
• It sends recordings only to AtriumKit. It contains no analytics or advertising code and loads no remote code. Its popup and side panel load fonts from Google Fonts.
• It asks Chrome for permission to read, capture and copy the tabs you record on any site (tabs, scripting and access to all sites, which also lets it download a page’s images, styles and fonts for HTML copies), to store recordings on your device (storage and unlimitedStorage) and to show its review panel (sidePanel).

Our use and transfer of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use it only to provide and improve AtriumKit’s recording and demo features. We transfer it only to service providers that help us run those features (see section 8), as you direct (for example, when you publish a demo or connect an AI assistant), to comply with the law, or to protect against malware, spam, phishing, fraud or abuse. We do not sell it; use or transfer it for personalized advertising; transfer it to advertising platforms, data brokers or other information resellers; or use or transfer it to determine creditworthiness or for lending. If AtriumKit is part of a merger, acquisition or sale of assets, we will transfer this information only with your explicit prior consent. Our people do not read it unless you ask us to (for example, for support), it is needed for security or to investigate abuse, or the law requires it.

4. People who view demos and guides

When someone views a demo, a guide page or a demo collection, on atriumkit.com or embedded on another website, we collect the following on behalf of the demo’s owner:

• Activity: views, the steps or screens seen, hotspot and button clicks (including the link a button opens), the options picked in demos that ask a question (such as “What brings you here?”), whether the demo was completed, how much of each narration was heard and whether sound and captions were turned on, the language shown, and which published version was shown. On a collection page: which demos were opened and where a button was clicked. On a guide page: views, the steps reached, and whether the guide was copied, downloaded or printed.
• Identifiers and context: a random visitor identifier kept in the browser’s local storage until the browser’s storage is cleared, a new identifier for each visit, the domain of the referring website, whether the demo was embedded, which personalized link was opened, if any, and an approximate country that Cloudflare derives from the IP address. IP addresses are not stored with analytics.
• Details you submit: if a demo, guide or collection asks for them (an email gate or a lead form), your email address and any other details you enter, such as name, company or phone number, together with your country and the referring website. On a collection page, one email unlocks every demo in it, and your details are stored with what prompted the request (for example, unlocking a demo), which demos in the collection you watched and how far. In the owner’s dashboard these details are linked to your earlier visits to that demo and to the personalized link you used, if any. The owner can export them and may send them to its own systems, such as a CRM or a chat tool, with whether you finished the demo or clicked its buttons (and the option you picked), what you watched in a collection, and the address of the page the demo was embedded on. If the embedding website passes on its HubSpot visitor identifier, we forward it with your details to the systems the owner connected. We store your IP address for about 24 hours to limit repeated submissions.
• The embedding website: when a demo is embedded, the player tells the page it is on when the demo is ready, when the step changes, when it is completed, when a lead form is submitted, and whether sound and captions are on. It does not pass on the details you entered.

When someone at the company presents a demo to you on a call (presenter mode), the player collects no analytics, and any details the presenter types to personalize it stay in the presenter’s browser.

Guide pages

Each published demo can also have a step-by-step guide page, unless the company turns it off. A guide page follows the demo’s access setting and email gate, and public guide pages can appear in search engines. Printing a guide or saving it as a PDF happens in your browser.

Personalized demos

A demo can show your name, company or other details in its text, such as “See how Acme closes the books”. The values come from what you entered in a form during your visit, from the website the demo is embedded on, from the demo link’s address (for example ?company=Acme or #company=Acme), or from a personalized link. Values from the first three are used only in your browser to fill in the demo: we do not store them and keep them out of analytics and AI and voice requests. Values from a link’s address are kept in that browser tab’s session storage while it is open, and the player removes them from the address bar. Values after a ? reach our servers as part of the request, so they can appear in our short-lived operational logs; values after a # never leave your browser.

Personalized links

A company can create a personalized link for one person, such as a prospect it is talking to. The link contains only a random code. The details the company entered for that person (for example name, company, job title and email address) are stored in its workspace, are visible to all its members, and are sent with the page when the link is opened so the demo can show them, so anyone who has the link can see them. If you open a personalized link, the company can see when the link was viewed and what happened in the demo, such as how far it was watched, and any details submitted through it are linked to it. The company can also be alerted, for example in Slack or Microsoft Teams, when the link is opened (up to 20 alerts per link per day); these alerts, and any details you submit, carry the link’s label, address and details to the company’s connected systems. If someone forwards the link, their visit counts for the same link. When the company deletes a link, its details are erased from the workspace, but copies already sent to its connected systems, and its recent delivery log, keep them. The company that sent the link decides how this information is used and is responsible for telling you about it, so contact it with any questions.

Reports and fonts

Viewers can report a demo, a guide or a collection page that breaks our Terms. Reports come to us, not the owner, as described in section 2. We do not give the reporter’s email address to the owner.

Demos and guide pages that use AtriumKit’s default typefaces load them from Google Fonts. Those whose brand kit sets its own fonts load them from AtriumKit. The player does not use advertising or cross-site tracking cookies.

5. AI features and AI assistants

Writing and translating with AI

When a workspace member asks, AtriumKit drafts or rewrites demo copy, guide wording, narration scripts and knowledge kit drafts, and translates demos, with an AI model provided by OpenAI, L.L.C. Requests reach OpenAI through Cloudflare AI Gateway.

• What we send: the demo’s title, its current copy and narration scripts, and how its steps fit together; for each screen, its name, page title, a short form of its address (the website and path, without the query string or identifiers) and the text and labels shown on it; the tone, audience, product name and instructions you give; and the brand kit’s knowledge: its description, audience, voice, glossary, notes and the passages of your uploaded files that best match the task, up to about 12,000 characters per request. Translations send the text to translate, the target language and the glossary terms it uses. A knowledge kit draft also sends the page paths, titles and labels of the demos that use the kit. Before sending, we leave out text under any blur (auto-blur, a “Blur area” or the editor’s blur), text outside a crop and text you hid or replaced, and we replace email addresses, phone numbers and long numbers in screen text and file passages with placeholders. Other details in your files, such as names and prices, and the copy and instructions you write are sent as written.
• What we do not send: screenshots or other images, HTML copies, the uploaded files themselves, personal values typed while recording, presenter notes, leads, analytics, viewers’ personalization values, or your name and email address. Requests carry your workspace and demo identifiers so we can track usage and cost.
• Training and how long it is kept: we do not use your content to train AI models, and OpenAI and Cloudflare are not allowed to use it to train theirs. We ask OpenAI not to store replies for later use. OpenAI keeps requests and replies in its abuse-monitoring logs for up to 30 days, or longer where the law requires it or to protect against harm. Cloudflare AI Gateway keeps a log of each request, which can include the text sent and the reply, for up to 7 days.
• You stay in control: suggestions appear in the editor, and nothing in your demo changes until you apply them. AI output can be wrong, so review it before you publish.

Files in knowledge kits

Files you upload to a knowledge kit (PDF, Word, PowerPoint, Excel, CSV, Markdown or plain text) are stored privately with the text extracted from them, and only members of the workspace can download them. Cloudflare Workers AI converts PDF, Word, PowerPoint and Excel files to text when you upload them; Cloudflare does not keep them after the conversion or use them to train AI models. We split the text into passages, with email addresses, phone numbers and long numbers masked, for the AI features above, the workspace’s knowledge base and AI assistants’ knowledge search. Every member of the workspace, viewers included, can see knowledge kits and their files.

AI assistants you connect

You can connect an AI assistant, such as Claude, ChatGPT or Cursor, to a workspace through AtriumKit’s MCP server, by approving it in AtriumKit or by creating a personal access token. The assistant can then do what you allow, within your role in the workspace: read and edit demos and collections, publish them and change who can see them, read guides and search knowledge kits, generate voiceovers, see screen images with their blurs applied (never unedited originals or blurred text) and screen text with email addresses and phone numbers masked, read analytics and, on the Team plan, presenter notes, and, only if you grant the leads permission, read leads, viewers’ email addresses in analytics and the details of personalized links.

• What the assistant receives is sent to it at your request and is handled by the assistant’s provider (for example, Anthropic for Claude or OpenAI for ChatGPT) under your agreement with that provider. Those providers are not our service providers. Check the assistant’s data and training settings before you connect it, especially before you let it read leads.
• For each token or connection we store its name, workspace, permissions, expiry, when it was created and last used, and the country it was last used from, and for each assistant the name and web addresses it gives about itself. To check an assistant that identifies itself by a web address, our servers fetch that address; the request carries no information about you. We store tokens only as hashes. Creating a token requires your password, and we email you when a token is created or an assistant is connected. Changes an assistant makes appear in the demo’s version history with its name.
• You can revoke a token or disconnect an assistant at any time in Settings, and workspace admins can revoke any token in their workspace. Tokens stop working when a member is removed, when an account is suspended and when a password changes.

6. Voiceovers and voice recordings

• AI voices: on paid plans, a demo can be narrated by an AI voice from Eleven Labs Inc. (ElevenLabs). When a workspace member generates narration, we send ElevenLabs, through Cloudflare AI Gateway, the narration script (including the pronunciations set in the brand kit’s glossary), up to 300 characters of the neighboring steps’ scripts so the speech sounds natural, and the voice and its settings. Personalized text is spoken with the demo’s default values, never a viewer’s. ElevenLabs returns the audio and the timing of each word, which we store as the clip and its captions. ElevenLabs keeps requests under its own retention terms, and we have turned off its use of our content to improve its models. Like AI requests, these requests pass through Cloudflare AI Gateway, whose logs can hold them for up to 7 days.
• Recordings and uploads: a member can record narration with the dashboard’s microphone or upload an audio file. Your browser converts it to MP3 before it is uploaded. A recording contains the speaker’s voice, and an upload may contain other people’s voices, so get their permission first. Cloudflare Workers AI transcribes recordings and uploads to create the script and captions; it does not keep the audio after transcribing it or use it to train AI models, but the request passes through AI Gateway, whose logs can hold it for up to 7 days. The transcript becomes the step’s script: published demos show it as captions, and it is sent to OpenAI if you translate the demo or ask AI to write narration, and to ElevenLabs if you turn it into an AI voice. We do not create voice clones or voiceprints from recordings.
• Where audio is kept: clips are stored with the demo at hard-to-guess addresses on media.atriumkit.com. Anyone who has a clip’s address can play it, including a clip that is not published yet, and anyone who can view a published demo can play and download its narration. We also record the characters of AI voice used each month, without the scripts.

7. How we use information

The table lists what we use information for and, for people in the EEA, the UK and Switzerland, the legal basis we rely on. Where we process information for a workspace, the workspace owner decides its legal basis.

We do not use automated decision-making that has legal or similarly significant effects on you. We do not use your content, or information about the people in it, to train AI models, and the providers that run our AI, voice and transcription features are not allowed to use it to train theirs.

What you have to give us. To create an account you must give us your name, email address and a password. To start a trial or paid plan you must give Stripe a payment method and, where tax applies, a billing address. Without them we cannot open your account or start the plan. Everything else is optional.

8. How we share information

• The people you choose: published demos, guide pages and collections are visible according to their access setting (public, unlisted or email gate), and public ones can be indexed by search engines. Hosted demo pages include the demo’s title and cover image for link previews.
• Your workspace: members of a workspace can see its demos, analytics, leads, personalized links, knowledge kits and files, members and invitations according to their role; personalized links and knowledge kits are visible to every role.
• Your systems: if a workspace admin connects an integration (such as Slack, Microsoft Teams, Discord, Google Chat, HubSpot, Salesforce, Zapier or a webhook), new leads are sent there (for collection pages, with what the lead watched), along with when a lead finishes a demo or clicks one of its buttons, and when a personalized link is opened, with the link’s details. These services are the workspace’s own providers, and their terms and privacy policies apply.
• AI assistants you connect: what they request, within the permissions you grant (see section 5).
• Websites you import a brand from: when you import a brand kit from a website, our servers request that site’s page, styles and images. They identify themselves as AtriumKit and send no information about you.
• Embedding websites: the player events described in section 4.
• Service providers that process information for us under contracts that limit how they use it:

This table lists every service provider that processes personal information for the Services, including information we process for workspaces. We update it before a new provider starts processing personal information.

• Google Fonts: this website, the dashboard, the extension’s popup and side panel, and demos, guide pages and collection pages that use AtriumKit’s default typefaces (including every demo on the Free plan) load typefaces from Google Fonts, so your browser sends Google LLC your IP address and browser details when it requests them. Google’s privacy policy applies to that information. When a brand kit uses a Google font, we copy the font to AtriumKit when the kit is saved, so viewers’ browsers do not contact Google for it. HTML copies of recorded pages never load anything from Google or other websites.
• Legal and safety: when the law requires it, or when it is needed to protect people, the Services or our rights.
• Business changes: as part of a merger, acquisition, financing or sale of assets, subject to this policy’s protections. Information received through the extension is transferred in such a deal only with your prior consent (see section 3).
• With your consent or at your direction.

We do not sell personal information, “share” it for cross-context behavioral advertising, or use it for targeted advertising, as those terms are defined in US state privacy laws. We do not disclose personal information to third parties for their own direct marketing. Apart from the font requests Google receives and the Google Analytics measurement of our marketing pages described in section 2, we do not let third parties collect information about your activity over time and across websites through the Services.

9. Cookies and local storage

The session cookie, dashboard settings, your cookie choice, email-gate, language, captions and form flags, personalization values and extension storage are needed for the Services to work or remember choices you made. The Google Analytics cookies are set only with your consent (see section 2). ak_vid is used only to count views and returning visitors for the demo owner’s analytics, and ak_cv_… and ak_cp_… only to show your progress through a collection. A company that embeds demos on its own website is responsible for any consent its visitors’ local law requires for ak_vid. Cloudflare may also set strictly necessary security cookies to protect the Services from bots and attacks. We do not use advertising or cross-site tracking cookies.

How we respond to Do Not Track and Global Privacy Control signals. When your browser sends either signal, the atriumkit.com marketing pages do not load Google Analytics or show the cookie banner. We do not track you across other companies’ websites, and we do not sell or share personal information for advertising, so the rest of the Services respond the same way whether or not your browser sends them.

10. Where information is processed

Simplisik LLC is based in the United States. Our database is hosted in North America, and Cloudflare’s global network delivers the Services from locations near each visitor. Our other providers, including OpenAI for AI features, ElevenLabs for AI voices and Google for website analytics, process information in the United States and may process it in other countries. If you use the Services from outside the United States, your information is transferred to, stored in and processed in the United States, where data protection laws may differ from those where you live. Where the law requires a transfer safeguard, our providers rely on recognized mechanisms such as the EU-U.S. Data Privacy Framework and its UK and Swiss extensions, or the European Commission’s Standard Contractual Clauses. When we process information for a workspace, the transfer terms in our agreement with the company that owns it also apply. You can ask us for a copy of the safeguards that apply by emailing privacy@atriumkit.com.

11. How long we keep information

Deleted information can remain in backups and logs until they expire as described above. We may also keep information for longer where we need it to resolve disputes, prevent abuse or comply with the law.

12. Your rights and choices

In the dashboard

• Change your name, email address and password, or reset a forgotten password by email.
• Delete your account. This deletes workspaces where you are the only member, with everything in them, and cancels their subscriptions immediately. If you are the only admin of a workspace with other members, make someone else an admin first.
• Delete recordings, demos, narration clips, collections, personalized links, knowledge kit files and leads, and export your leads as a CSV file. Turn a demo’s guide page off.
• Workspace admins can remove members, cancel invitations and delete the workspace.
• Revoke access tokens and disconnect AI assistants.
• In the extension, turn off auto-blur, choose “Screenshots only”, or discard a recording before it is uploaded.

By request

Email privacy@atriumkit.com for anything you cannot do in the dashboard, such as removing a saved version from a demo’s history, or to exercise any of these rights:

• know what personal information we hold about you and get a copy, including in a portable format;
• correct inaccurate information;
• delete your information;
• ask us to restrict how we use it;
• withdraw consent where we rely on it;
• opt out of the sale of personal information, targeted advertising and profiling, which we do not do.

These rights apply to everyone, wherever you live, although how they work depends on the law that applies to you. We will confirm your request by writing to the email address on your account, and may ask for more information if we cannot verify your identity that way. We respond within one month, or sooner where the law requires, and will tell you if we need longer. You can use an authorized agent, who must show us your signed permission. We will not discriminate against you for exercising your rights.

Your right to object. Where we use your information based on our legitimate interests (see section 7), you can object at any time by emailing privacy@atriumkit.com. We will stop unless we have compelling legitimate grounds that override your interests, or we need the information to establish, exercise or defend legal claims.

Appeals. If we decline your request, you can appeal by replying to our decision with “Appeal” in the subject line. We will answer within 60 days. If you are not satisfied, you can contact your state attorney general.

EEA, UK and Switzerland. You can complain to us at privacy@atriumkit.com, and we will acknowledge your complaint within 30 days. You can also complain to your local data protection authority; in the UK, that is the Information Commissioner’s Office (ico.org.uk).

Viewers, people a personalized link was made for, and people in a workspace’s content. The company that shared the demo, or whose content you appear in, controls your information, so contact it first. If you contact us, we will pass your request to that company and help it respond.

13. Security

We encrypt traffic with TLS, hash passwords with a unique salt, store session and access tokens, invitation links and password-reset and email-change links only in hashed form, encrypt the addresses and secrets of integrations, and limit access to workspace data by role. An invitation can only be accepted by the email address it was sent to. Creating an access token requires your password, and we email you when one is created or an AI assistant is connected. HTML copies of recorded pages are served from a separate domain, in a sandbox where the recorded page’s own scripts never run and that cannot reach your account. Changing your password signs out your other sessions, including the extension, and revokes access tokens, and we email you when your password or email address changes. The extension uploads only to AtriumKit, over HTTPS. Unlisted links and email gates control who is invited to see a demo, but they are not a security boundary: anyone with the link can open an unlisted demo, so do not publish confidential information in one. No method of transmission or storage is completely secure, so we cannot guarantee absolute security. If a breach affects personal information, we will notify the people affected and the authorities as the law requires. For information we hold for a workspace, we will notify the company that owns it so it can do the same.

14. Children

AtriumKit is for businesses. You must be 18 or older to create an account, and the Services are not directed to children. We do not knowingly collect personal information from anyone under 16. If we learn that we have, we will delete it.

15. Changes to this policy

When our practices change we will update this page and its “Last updated” date. If a change is material, we will tell account holders by email or in the dashboard before it takes effect. You can ask us for an earlier version at privacy@atriumkit.com.

16. Contact us

Questions, requests and appeals: privacy@atriumkit.com, or by mail:

Simplisik LLC
Attn: Privacy
5510 Old Hickory Blvd, Suite B #32
Hermitage, TN 37076
United States