Privacy Policy
MyBriefing Privacy Policy
This is a pre-release policy for production smoke testing. It may be reviewed and replaced before MyBriefing becomes generally commercially available.
Overview
This Privacy Policy explains how Datagem LLC handles information in connection with MyBriefing, an AI Executive Briefing service. It covers the account-entry, briefing, usage, billing, and support flows currently represented by the service. It does not make promises about features or data practices that have not been implemented.
1. Information MyBriefing processes
Identity and profile information
When you sign in, Amazon Cognito provides a stable identity subject and profile claims used for account access, such as display name, email address, and email-verification status. If you choose Google, Google authenticates you through Cognito. MyBriefing uses the exact Cognito issuer and subject to link the identity; it does not use a matching email address to merge accounts.
Internal account, consent, and support information
Datagem LLC processes an internal account ID, identity-provider label, profile snapshots, policy versions and acceptance time, selected login method, application-session records, and related status data. The account ID may be shown as a support reference.
Meeting and briefing content
Depending on the features you use, MyBriefing processes your session description, agenda, persona, language choices, optional event metadata, meeting audio, source transcripts, translated text, live summaries, analytical notes, and final briefings. When you request encrypted email delivery, MyBriefing also processes the verified email already bound to your signed-in account, an artifact-kind code, an opaque request ID, and the encrypted attachment. The delivery form does not accept another recipient.
Operational, usage, entitlement, and billing records
MyBriefing processes session and usage identifiers, timestamps, status, measured quantities, plan and credit balances, consumption allocations, catalog and checkout identifiers, payment and subscription status, and provider event references needed to operate access and billing. Stripe hosts checkout and billing-management pages; MyBriefing is not designed to receive or store full payment-card numbers.
Support communications
If you contact Datagem LLC, it may process the contact details, message, account or billing references, diagnostic information, and attachments you choose to provide in order to respond and maintain appropriate business records.
2. Transient provider processing and MyBriefing-held data
In the current architecture, browser microphone audio is sent directly to OpenAI's realtime service for transcription and optional translation; the MyBriefing backend does not relay the continuous audio stream and does not persist raw meeting audio. OpenAI transiently processes that audio and returns realtime results to the browser.
Source transcript chunks and translated text are sent from the browser to MyBriefing so the service can assemble session state and create live and final briefings. Transcript and context may be sent to OpenAI for summary generation.
MyBriefing processes meeting content to provide Live Notes, Live Briefing, and Final Briefing. For email delivery, the selected Final Briefing and transcript are encrypted in the browser. The attachment-encryption password never leaves the browser, so neither the MyBriefing server nor Resend can decrypt the emailed attachment.
The current application holds briefing content in process-local, expiring repositories rather than the commercial account database. Account, identity, consent, application-session, entitlement, usage, and billing records may be persisted in MyBriefing's configured database. Provider systems may retain information under their own terms and legal obligations.
3. How information is used
Datagem LLC uses information to:
- authenticate customers, establish application sessions, and protect accounts;
- capture transcripts, translate text, and generate live and final briefings;
- deliver a requested briefing email;
- enforce ownership, plans, usage allowances, credits, and billing status;
- process and reconcile verified checkout, subscription, and payment events;
- operate, troubleshoot, secure, and improve service reliability;
- respond to support requests and prevent abuse or fraud; and
- comply with applicable law and resolve disputes.
This preview policy makes no claim about whether a provider uses data to train models. Provider-specific handling is governed by the configuration and terms applicable to the service account used by Datagem LLC.
4. Configured service providers
- Amazon Cognito provides managed account registration, sign-in, email verification, password recovery, and identity claims.
- Google provides authentication when you choose Continue with Google; Cognito remains MyBriefing's identity issuer.
- OpenAI processes realtime audio, transcription or translation requests, and briefing-generation requests.
- Stripe hosts configured checkout and billing-management experiences and provides verified billing events and identifiers.
- Resend processes the verified account recipient, fixed generic notification, encrypted attachment, and necessary delivery metadata when encrypted final-briefing delivery is configured and requested.
A provider is involved only when its related feature is configured and used. Datagem LLC may update providers as the service changes and will update this policy when a material change requires it.
7. Security
MyBriefing uses backend token verification, opaque HttpOnly application sessions, same-origin request checks, account ownership checks, and server-owned billing and consent configuration. No system is completely secure, and Datagem LLC does not guarantee that loss, misuse, or unauthorized access will never occur. Do not send passwords, session cookies, or provider secrets to support.
8. Retention
Datagem LLC retains information for as long as reasonably necessary to provide and secure MyBriefing, maintain account, consent, entitlement, billing, and transaction records, respond to support and disputes, and meet legal obligations. Different categories and providers may have different retention needs. This preview does not promise a fixed deletion schedule or an automated account-deletion capability.
9. Customer choices and privacy rights
You may choose Google or native email sign-in, choose whether to enable translation, choose whether to email a final briefing or include a transcript, stop capture, sign out, and stop using the service. Password changes and recovery are handled by Google or Cognito, as applicable.
Depending on your location, you may have rights to request access, correction, deletion, restriction, objection, or portability, or to complain to a privacy authority. These rights may be subject to identity verification, legal exceptions, and technical limitations. Submit a request through the MyBriefing product site at briefing.datagem.cloud.
10. International processing
Datagem LLC and its service providers may process information in countries other than the one where you live. Those countries may have different data-protection laws. Datagem LLC will use the safeguards required by applicable law for such processing.
11. Children's privacy
MyBriefing is designed for professional and academic session attendees who can lawfully agree to the service terms. It is not directed to children who cannot provide valid consent under applicable law. If you believe a child has provided personal information without required authorization, contact Datagem LLC through the support channel provided with the service.
12. Contact and policy changes
Contact Datagem LLC through the MyBriefing product site at briefing.datagem.cloud. Include your MyBriefing User ID when it is safe and relevant, but never send a password or session cookie.
Datagem LLC may update this policy to reflect product, operational, legal, or provider changes. The effective date and policy version identify the applicable text. A material change to either accepted legal document requires new configured version identifiers and renewed acceptance; the text will not intentionally change silently under the same version.