Privacy Policy
How BeatAPI handles account data, API usage, files, realtime media, and workflow logs.
Last updated: 2026-11-13
How BeatAPI handles account data, API usage, files, realtime media, and workflow logs.
Last updated: 2026-11-13
BeatAPI provides async AI video workflows and Realtime Video sessions, including API keys, USD billing, file upload, task logs, webhooks, browser media connections, and hosted outputs. This Privacy Policy explains what information we collect, how we use it, and the choices available to you when you use BeatAPI.
We collect information needed to operate an API-first service:
client_secret; it must not receive your permanent BeatAPI API key.We use this information to:
When you connect BeatAPI to an AI application such as ChatGPT, you sign in to BeatAPI and approve the access scopes shown on the consent page. The connection uses OAuth; you do not need to provide a BeatAPI API key in the conversation.
BeatAPI stores the connection's account association, client identifier, approved scopes, authorization and expiry timestamps, revocation status, and spending-limit settings and counters. OAuth authorization codes, access tokens and refresh tokens are stored as credential hashes in the OAuth credential columns. This does not describe the host application's own credential storage.
When the connected application invokes a tool, BeatAPI receives the arguments needed for that request, such as a research query, public source URL, prompt or input-media URL. BeatAPI and the relevant model, data or tool providers process these inputs as needed to fulfill your request. Tool responses, task status and result links are returned to the requesting application, where its privacy terms and your settings also apply. Connecting BeatAPI does not itself authorize access to private social messages or a social account's login session.
You can revoke a connected application's access in your BeatAPI account security settings. Revocation prevents further authorized calls through that connection; it is not a request to delete all prior tasks, results or accounting records. Credential hashes may be retained until the associated authorization expires for replay detection. Expired authorization records are removed by scheduled cleanup, not necessarily at the instant of expiry. The retention rules below continue to apply to usage, security, billing and generated files. Contact support@beatapi.io for privacy and deletion requests.
The BeatAPI AI Image & Video Generator extension processes the prompt you enter and an optional image you explicitly select from your device or a web page. When you use the image context-menu action, the extension temporarily captures the visible tab, crops the selected image locally, and discards the full-tab screenshot. The reference contains the visible portion, not necessarily the original image file. The extension does not send source-page URLs or browsing history to BeatAPI, read cookies or account credentials, or include an analytics SDK.
Drafts stay in browser session storage and expire after ten minutes. Expired extension records are removed by periodic cleanup. Clicking Open Generator transfers your draft to the BeatAPI website; prompt text and image bytes are not included in the URL. The website keeps a temporary session copy so the draft can survive sign-in. A selected image is uploaded through the BeatAPI gateway only after authentication. The website session copy is cleared after successful upload or expiry; if no website page is open, expired copies are removed on the next load. You can remove the reference or cancel its pending upload on the website. Links carry static extension-source attribution, not a personal tracking identifier.
The extension does not itself start generation or authorize a paid task. Website authentication, uploads, generation and billing remain subject to this policy and the service terms. Uploaded files and requested generation inputs may be processed by the service vendors described below; the ten-minute local-draft expiry does not promise deletion of an already uploaded file from those systems.
Data obtained through the extension is used or transferred only to provide its user-facing draft and creation workflow, and as permitted by the Chrome Web Store User Data Policy. We do not sell it, use or transfer it for unrelated purposes, personalized advertising, or creditworthiness or lending decisions. For privacy and deletion requests, contact support@beatapi.io.
Realtime Video can use a camera or another browser MediaStream, prompts, and optional reference images to create a live generated output. Camera input and generated output travel over the realtime WebRTC media connection to the AI processing provider; BeatAPI operates the session-control, credential, billing, security, and diagnostic layers needed to provide that connection.
Realtime Video does not automatically create or store a hosted MP4. If your application uses MediaRecorder or another local recording feature, the recording is created and handled by your browser or application under your control. You are responsible for telling participants when capture or recording occurs, obtaining all required permissions, and applying your own storage and deletion policy.
Faces, voices, movements, likenesses, and other characteristics present in a MediaStream or reference asset may be processed to provide the requested generation. BeatAPI does not use this material for biometric identification. We do not use private customer content to train general-purpose AI models unless we provide a separate, explicit notice and obtain any consent required by law.
BeatAPI may use infrastructure, storage, payment, analytics, email, security, and upstream AI providers to operate the service. Workflow inputs and outputs may be sent to these providers only as needed to process your requested task, store files, deliver webhooks, process payments, or provide support.
We do not sell your personal information. We may disclose information when required by law, to protect BeatAPI and our users, or as part of a business transaction such as a merger, acquisition, or asset transfer.
Where supported by an applicable legal basis, we may use the account information, IP address, approximate location, transaction records, and necessary usage records described above to assess service eligibility, prevent fraud and abuse, enforce applicable regional or provider restrictions, and meet legal obligations. This does not mean that every user undergoes identity verification or sanctions screening. Information used for these purposes is limited to what is reasonably necessary. If additional information is needed, we will explain its purpose and the relevant requirements.
Depending on the capability you select and the service providers involved, information needed to fulfill your request may be processed or stored outside your country or region. This may include inputs, files, request parameters, and related technical information sent to the relevant model, data, or tool provider, as well as information handled by payment, infrastructure, or support providers for their respective purposes.
Applicable data protection requirements depend on the processing involved. Where required, we will provide additional notices, obtain required consents, and apply the safeguards required by applicable law for international transfers. Provider processing and retention policies may differ; contact us if you need information about the processing applicable to a particular capability. This policy does not promise that every provider offers zero retention or excludes all use of data for model training.
You are responsible for the prompts, files, URLs, and other content you submit to BeatAPI. We use customer content to provide the workflow you request, troubleshoot service issues, enforce safety and acceptable-use rules, and maintain billing and audit records. We do not publish your private customer content unless you choose to share it or direct us to do so.
We use cookies and similar technologies for login sessions, language preferences, security, analytics, and product reliability. You can control cookies through your browser settings, but disabling some cookies may affect authentication or dashboard functionality.
We keep account, billing, API usage, file, task, webhook, Realtime session metadata, and support records for as long as needed to provide the service, comply with legal obligations, resolve disputes, prevent abuse, and maintain audit logs. Short-lived Realtime credentials expire and are cleared according to the session lifecycle. Some generated outputs or uploaded files may be removed earlier based on product limits, storage policies, or account deletion requests. Customer-controlled local recordings are not retained by BeatAPI unless the customer separately uploads them to BeatAPI.
We use reasonable technical and organizational safeguards, including encrypted transport, access controls, authentication controls, logging, and operational review. No internet service can guarantee perfect security, so you are responsible for keeping API keys, account credentials, and Realtime client_secret values confidential and for limiting each session to exact trusted browser origins.
You may request access, correction, export, or deletion of certain personal information by contacting us. We may need to keep some records where required for security, billing, legal compliance, abuse prevention, or legitimate operational needs.
We may update this Privacy Policy from time to time. If we make material changes, we will update the date above and may provide additional notice through the service or by email.
For privacy questions or data requests, contact us at support@beatapi.io.