Privacy Policy

Information we access

• Google identity: your name, email address, profile image, and Google account identifier, to sign you in and check your eligibility.
• Connected Gmail: message and thread content, subjects, participants, dates, identifiers, and attachment metadata returned by searches for relevant artists, projects, and submissions.
• Connected Calendar: event details, including titles, descriptions, dates, participants, and locations, to identify relevant meetings and outreach.
• Workspace content: submitted emails and screenplay attachments, generated PDFs and summaries, artist records, notes, feedback, and chat inputs.
• Operational information: connection status, granted permissions, encrypted Google refresh tokens, session cookies, and service logs. Diagnostic logs can contain request and response content, including relevant email, calendar, document, and chat content.

Gmail and Calendar permissions are read-only. They do not permit us to send, change, or delete Gmail messages, or create or modify Calendar events. These permissions technically allow broader reading than the relevant results we seek; searches can return unrelated content, which the application attempts to filter out. We do not receive your Google password.

How we use and share information

We use information to authenticate users, process submissions, identify relevant correspondence and meetings, generate shared Artist CRM outreach history and Live Feedback summaries, answer workspace questions, and operate and troubleshoot these features.

CRM updates are shared across the workspace. Authorized Blumhouse users and collaborators on the email allowlist can see shared updates drawn from all connected accounts. A refresh can search your connected Gmail and Calendar while you are signed out. Shared results can include summaries, source details, participants, dates, and relationship information, even for users who were not part of the original conversation or meeting. Sharing is not limited to the person who clicked Refresh.

Connecting an account authorizes this shared business use; it does not give teammates direct access to your Google account. Only connect an account you are authorized to contribute. Do not use the workspace to investigate personal matters or expose confidential information outside its authorized audience. If sensitive information appears in a shared result, contact us to request review and removal.

Google Gemini processes relevant email, calendar, submission, and chat content to generate summaries and answers. Under our paid service, Google does not use this content to improve its products, but may retain it for abuse prevention and legal requirements. See the Gemini API terms.

Service providers process information needed to host, store, secure, and deliver the workspace and its email features. Processing may occur outside your country. This does not make your information public.

Google data and Limited Use

Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements. This also applies to information derived from that data.

We do not sell Google user data, use it for advertising, or use it to train or improve AI or machine-learning models. We limit its use and transfer to providing the disclosed user-facing features, security, and other purposes permitted by those policies. Human access is limited to the sharing you authorize, your specific consent, and other access permitted by Google's policies, such as security investigations or legal requirements.

Storage, retention, and security

Saved submissions, files, summaries, CRM history, and source information remain in the shared workspace until deleted through available controls or an administrator-assisted request. Disconnecting an account stops use of its saved Google connection; it does not delete previously shared records or copies other users have already obtained. The same correspondence may also be present in another connected account.

Logs and backups follow the hosting providers' retention and recovery settings, so deletion from the workspace may not immediately remove every copy. Chat conversations are not saved as chat history in the app, but diagnostic logs and provider processing can retain content.

We use encrypted connections, encrypted stored Google refresh tokens, server-side credentials, and access checks for protected workspace records. No system can guarantee absolute security.

Your choices and deletion requests

You can decline Google permissions, although connected-account features and workspace access require the requested permissions. Signing out clears your browser's session cookie but leaves your Google account connected. To disconnect it, choose Disconnect Google account in the Profile menu. This clears the app's stored reusable Google credentials and signs you out. You can also revoke access through your Google Account connections.

To request access to, correction of, or deletion of information, email jaeschelachea@gmail.com. Identify the account and records involved, and whether your request covers shared summaries and source details. Do not send passwords, access tokens, or unnecessary copies of sensitive content. We verify your identity and authority before disclosing or deleting information, and explain any retention required for legal or security reasons. Deleting information from Blumhouse Labs does not delete the original messages or events in Google.

Changes and contact

We will update this page when our practices change. Material changes to Google-data use will be disclosed before the new use, with consent requested when required. For privacy questions, contact jaeschelachea@gmail.com.