Legal
Privacy Policy
Effective Date: October 8, 2025
Last Updated: September 23, 2026
Section 1
Introduction
At Simulive, we respect your privacy and are committed to protecting your personal information. This Privacy Policy explains how we collect, use, and safeguard your data when you use our platform at simulive.us.
We believe in transparency and minimal data collection. We only gather information that is essential for providing you with a secure and functional service.
Section 2
Information We Collect
Account Information
When you create an account or sign in through a third-party authentication provider, we collect basic account credentials necessary to identify and authenticate you. We do not store passwords if you use external authentication providers.
Usage Data
We collect minimal technical information required to maintain your session and ensure platform security. This includes session identifiers, authentication tokens, and security-related data to protect against unauthorized access.
Cookies and Similar Technologies
We use essential cookies to maintain your login session and protect against security threats. These cookies are strictly necessary for the platform to function properly and cannot be disabled without affecting your ability to use our services.
We do not use tracking cookies, advertising cookies, or analytics cookies. We do not collect behavioral data or share information with third-party advertisers.
Section 3
How We Use Your Information
We use the information we collect solely to:
- Authenticate your identity and maintain your login session
- Provide access to platform features and functionality
- Protect your account from unauthorized access and security threats
- Prevent fraud, abuse, and violations of our Terms of Service
- Communicate important updates about the service or your account
We never sell, rent, or share your personal information with third parties for marketing purposes.
Section 4
Google Account Data
When you connect your Google account to Simulive, we access certain information to provide our simulation and meeting features. This section explains what we access, what we store, and how we use it. Our use of Google data complies with the Google API Services User Data Policy.
What We Access
- Your account identity - your name, email address, and profile picture, used to sign you in and display your account information within Simulive.
- Selected files from your Google Drive - only files that you explicitly create or open through Simulive. We do not scan or access any other content in your Drive.
- Your Google Meet spaces - we create, read, and update meeting spaces on your behalf so you can schedule and run simulated sessions through Simulive.
What We Store
- Authentication credentials - stored securely so Simulive can act on your behalf for scheduled simulations without requiring you to sign in each time.
- Meeting space information - the details of Google Meet spaces linked to your simulations, such as the meeting link and settings, stored internally to support your sessions. Only your meeting join link is visible to you.
- Session files from Google Drive - files you explicitly open or create through Simulive are used temporarily during a simulation and permanently deleted once the session ends. They are never stored long-term.
How We Use This Data
- Google data is used exclusively to deliver the Simulive features you have requested.
- Your files and meeting data are processed securely on our backend and never shared with any third party.
- Temporary session data is permanently deleted once your simulation completes.
- Your authentication credentials are removed immediately when you disconnect your Google account or delete your Simulive account.
- We do not use your Google data for advertising, profiling, or any purpose beyond what is described here.
Section 5
Third-Party Service Integrations
Simulive connects with the following third-party meeting platforms. Each integration requires specific permissions to function. We only request the minimum permissions necessary.
Google Meet
As described in Section 4 above, we access your Google account, selected Drive files, and Google Meet spaces to create and run simulated sessions on your behalf. Only your meeting join link is visible to you - all other internal details remain on our backend.
Zoom
When you connect your Zoom account, Simulive accesses the information needed to create and run automated simulated sessions on your behalf.
What We Access
- Your Zoom profile - your name, email, and account identity, used to associate your Zoom account with your Simulive profile.
- Your meetings and webinars - details such as title, schedule, join link, and settings for sessions linked to your simulations.
- Registrant information - the list of people registered for your meetings or webinars, used to manage attendance for simulated sessions.
- Session activity - join and leave events and in-session chat activity during simulated sessions, used solely to calculate engagement metrics shown on your dashboard.
What We Store
- Authentication credentials - stored securely so Simulive can manage your sessions on your behalf.
- Meeting and webinar details - stored to support scheduling and running your simulations.
- Engagement data - attendance and chat activity from simulated sessions, retained only to generate the analytics shown on your dashboard.
- Session history - timestamps and status records for your completed simulations.
How We Use This Data
- Zoom data is used exclusively to deliver the simulation features you have requested.
- Only aggregated metrics such as total attendance and engagement scores are shown on your dashboard. Raw participant names, emails, or IDs are never displayed.
- Zoom data is never shared with any third party.
- Your authentication credentials are removed immediately when you disconnect your Zoom account or delete your Simulive account.
Microsoft Teams (Coming Soon)
Microsoft Teams integration is currently in development and not yet available to users. When it is released, this policy will be updated to describe the specific data accessed. You will be asked to re-authorize at that time.
General Principles
For all integrations:
- We store authentication credentials securely and use them only to perform actions you have authorized.
- All credentials are encrypted at rest and in transit.
- You can disconnect any integration at any time from your account settings, which will revoke our access and delete your stored credentials.
- Your data is never sold, rented, or shared with third parties for any purpose.
Section 6
SimuHost AI Brain and Bring Your Own Key (BYOK)
SimuHost is an optional AI co-host feature. It is off by default and only becomes active for a runbook if you choose to set it up. This section explains what SimuHost is allowed to use, what you control, and what we do and do not do with it.
Bring Your Own Key
- SimuHost runs on an AI provider account that belongs to you, not to us. You add your own API key for a provider such as OpenAI, Anthropic, Google, or another supported provider, and you choose which key is used for each runbook.
- Your key is encrypted at rest and shown to you only in masked form afterward. Revealing the full key again requires your account password or, if you have multi-factor authentication enabled, your verification code.
- Your key is used solely to send the requests SimuHost needs to generate replies for the runbook you assigned it to. We do not use your key or the model access it grants for any other purpose, and we do not use your key, your prompts, or your provider's replies to train Simulive's own models or any third party's models.
- You can edit or delete a saved key at any time from the API Keys page in your dashboard. Deleting a key removes it from our database immediately and permanently.
- The AI provider you choose processes the requests SimuHost sends on your behalf under that provider's own terms and privacy policy. We encourage you to review the policy of any provider whose key you add.
Skills, Guardrails, and Other AI Brain Content
- The instructions, blocked terms, reference notes, and any transcript you give SimuHost live in a workbook kept in your own connected Google Drive, not in Simulive's own storage. You can view and edit that workbook directly in your Drive at any time.
- When you upload a file such as a skills or guardrails document through the SimuHost dashboard, we read it, write it into the matching tab of your workbook, and do not keep a separate copy of the uploaded file once that write is complete.
- We read this workbook from your Drive before and during your event so SimuHost can follow it, and any reply that contains a blocked term from your guardrails is not sent.
Using Your Event's Live Content
- By default, SimuHost answers only from the skills and guardrails you have given it and does not see what is happening in your live event.
- You can separately choose, per runbook, to let SimuHost use your event's own content, such as a transcript, so it can ground its replies in what was actually said instead of relying on the model's general knowledge. This is off unless you turn it on, and you can turn it off again at any time from the SimuHost window.
Your Host Name
If you set a custom @handle for SimuHost, that handle is your own chosen name and is shown to attendees in place of a generic Simulive label. It is your branding, not ours, and you can change it from your profile settings at any time.
During a Live Session
When SimuHost answers in chat, that reply is delivered as a chat message in your event, the same as a message from any attendee, and is stored as part of your event's chat history in the same way described in Section 5. The prompt sent to your AI provider to generate a reply is used only to produce that reply and is not kept separately once the reply has been generated and delivered. We do not use your chat history to train any AI model.
Section 7
Screen Recording for Support (Drefly)
Simulive.us includes a support widget, built and operated by our vendor Drefly, that lets you record your screen and send that recording directly to the Simulive Support Team when reporting a bug or asking for help. This section explains how that feature works and who is responsible for the resulting recording.
How Recording Works
- A recording only starts after you click the record control on our site and approve your browser's own screen-sharing prompt. Nothing is captured before that click, and your browser's built-in sharing indicator shows whenever screen or microphone access is active.
- The widget requests your current browser tab rather than your whole screen or another window, and it never has access to any other tab, application, or window you have open.
- While a recording is running, the widget automatically blurs password fields and other clearly sensitive fields, such as card numbers and card security codes, so those values are not visible in the recorded video.
- You can decline the browser's screen-sharing prompt at any time to cancel a recording before it starts, and you can stop a recording in progress from the widget itself.
Who Stores the Recording
- Drefly does not store, retain, or keep a copy of your recording at any point. Drefly only operates the widget code that runs in your browser and the upload pathway that carries the recording to its destination. The finished recording is uploaded directly into Simulive's own secure storage, not to any server or database controlled by Drefly.
- Because recordings land directly in Simulive's secure storage, our Support Team is the only party that stores or can access the recording, and we use it solely to diagnose and fix the bug or support issue you reported.
- The widget only accepts recordings from domains we have registered to it, including our subdomains, so it cannot be used to route a recording anywhere outside of Simulive's own storage.
- We do not use recordings submitted this way for advertising, profiling, or any purpose beyond resolving your request.
- You can request deletion of a recording you submitted at any time by contacting us using the details in the "Contact Us" section below, the same as any other personal data request.
Drefly builds and operates the widget itself, and the code that runs in your browser during capture (before the recording reaches Simulive's storage) is described in Drefly's own Privacy Policy. Simulive's storage, use, and retention of the recordings you choose to send us through this feature is governed entirely by this Privacy Policy.
Section 8
Data Security
We implement industry-standard security measures to protect your data, including:
- Encryption of data in transit using HTTPS/TLS protocols
- Secure storage of authentication credentials, OAuth tokens, and session tokens
- Protection against common security vulnerabilities (CSRF, XSS, SQL injection)
- Regular security assessments and updates to our infrastructure
While we strive to protect your information, no method of transmission over the internet is 100% secure. We encourage you to use strong, unique passwords and enable additional security features when available.
Section 9
Data Retention
We retain your account information for as long as your account remains active. Session data and authentication tokens are automatically deleted when you log out or after a period of inactivity.
OAuth access tokens from third-party integrations (Google, Zoom) are deleted immediately when you disconnect the integration or delete your account.
AI provider keys you add for SimuHost, described in Section 6, are deleted from our database immediately when you remove them from the API Keys page or delete your account. Skills, guardrails, and other AI Brain content are kept in your own Google Drive and are not duplicated in our storage, so removing or editing them there removes them from SimuHost as well.
Support recordings submitted through the Drefly widget, described in Section 7, are retained only as long as needed to review and resolve the issue you reported, and are deleted on request.
If you delete your account, we will remove your personal information from our active systems within 30 days, except where retention is required by law or for legitimate business purposes such as fraud prevention.
Section 10
Third-Party Authentication Providers
Simulive supports sign-in via the following third-party identity providers: Google, GitHub, and Zoom. Microsoft Teams login is coming soon. When you sign in through any of these providers, you are redirected to their login page and we only receive basic profile information necessary for account creation, such as your name and email address.
These providers have their own privacy policies governing how they handle your information. We encourage you to review their policies before using them to sign in to Simulive.
Section 11
Your Privacy Rights
You have the right to:
- Access: Request a copy of the personal information we hold about you
- Correction: Request correction of inaccurate or incomplete information
- Deletion: Request deletion of your account and associated personal data, including any support recordings you have submitted
- Data Portability: Request your data in a structured, machine-readable format
- Objection: Object to processing of your personal information in certain circumstances
- Revoke Integrations: Disconnect Google, Zoom, or other integrations at any time from your account settings
- Remove AI Provider Keys: Delete any SimuHost API key at any time from the API Keys page in your dashboard
To exercise any of these rights, please contact us at support@simulive.us. We will respond to your request within 30 days.
Section 12
Children's Privacy
Our services are not intended for users under the age of 13. We do not knowingly collect personal information from children. If you believe we have inadvertently collected information from a child, please contact us immediately, and we will take steps to delete such information.
Section 13
International Data Transfers
Your information may be transferred to and processed in countries other than your country of residence. These countries may have data protection laws that differ from those in your jurisdiction. By using our services, you consent to the transfer of your information to our facilities and to the third parties with whom we share it as described in this policy.
Section 14
Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. We will notify you of any material changes by posting the updated policy on this page and updating the "Last Updated" date.
We encourage you to review this Privacy Policy periodically. Your continued use of the service after changes are posted constitutes your acceptance of the updated policy.
Section 15
Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our privacy practices, please contact us at: