1. Scope
RequestBeam is an AI and data API platform operated by JenThoughful. This policy applies to the website, console, APIs, accounts, payments, and related support services.
You may submit or query only data that you are authorized to process or use. If you use the services for an organization, you are responsible for informing its authorized users and obtaining any required permissions.
2. Data We Process
- Account and identity data, such as name, email address, account status, password hashes, and account identifiers, names, and avatars received when you sign in with Google.
- AI requests and content, such as prompts, conversations, reference images, input files, parameters, model responses, and generated outputs. Some content may also be saved as drafts in your browser.
- Data API requests and returned data, such as query parameters, filters, identifiers, and fields returned by data providers.
- Authentication and security data, such as API key identifiers, hashes and protected ciphertext used for authorized copying, sign-in credentials, authentication events, request timestamps, status codes, and security logs.
- Usage and billing data, such as request usage, balance, top-ups, charges, orders, payment status, and information required by payment processors.
- Connection and usage data, such as browser details, page visits, referral information, diagnostics, and performance data. Connection, hosting, and security infrastructure may also process IP addresses and other connection information.
3. How We Use Data
- Provide access, authentication, request processing, balance management, and usage records for AI and data APIs.
- Send requests to applicable providers, return AI outputs or Data API results, and save tasks, results, and conversation context for relevant features.
- Measure usage, calculate charges, present billing records, and enforce quotas, rate limits, security, and abuse-prevention controls.
- Troubleshoot issues, maintain service reliability and security, and improve the product experience.
- Handle account, payment, and support matters, and provide service, security, billing, or policy communications when needed.
4. Upstream Providers and Service Providers
To fulfill a request, we send inputs, files, query parameters, and necessary request information to applicable AI or data providers. Automatic routing, retries, or failover may involve multiple providers processing the same request. Failover for stateful conversations may also replay relevant historical context.
Identity services such as Google, payment processors, hosting, object storage, logging, and security providers may process data needed for their services. Loading third-party fonts, images, or other resources in your browser may also send connection information to those resource providers. Each service provider may have its own terms, data handling, and retention rules.
Some generated outputs may be copied to object storage and returned through public URLs. Anyone who obtains such a link may be able to access the content; the link is not equivalent to a private file that requires account sign-in. Share these links carefully.
We do not sell personal data. We share personal data only when needed to provide the service, comply with law, protect safety, or with your authorization.
5. Content, Logs, and Retention
Server-side task records may store complete inputs and request parameters. Some endpoints also store complete outputs, generated results, or result links. Stateful conversations may store requests, responses, and historical context. This content is not necessarily held only while a request is being processed, nor limited to usage metadata or response summaries.
Account details, request content, conversation context, generated files, usage, billing, security logs, and visit analytics are retained according to their purposes, relevant configuration, upstream requirements, and applicable legal obligations. Some conversation configurations do not expire automatically. This policy does not promise one retention period or automatic deletion rule for all data.
Upstream protocol options such as store:false do not mean zero retention for the platform's task, conversation, billing, or log records. Neither such an option nor this policy uniformly determines providers' own retention rules.
Do not submit personal data, regulated data, third-party secrets, confidential credentials, or other restricted information that you are not authorized to process.
7. Security and Your Rights
We use reasonable administrative and technical measures to protect data, but no internet service can be guaranteed to be completely secure.
Where applicable law allows, you may request access, correction, deletion, export, or restriction of your personal data. We will process requests after reasonable identity verification.
Deletion requests need to distinguish local browser data, server records, billing and security records, backups, and copies held by providers. Clearing drafts or signing out does not delete an account and every copy. Some records may be retained for accounting, security, or legal obligations, and upstream copies are subject to the relevant provider's rules.
When this policy changes materially, we will update its version and effective date and provide related notices when necessary.
Privacy Questions and Requests
For questions about this policy or data handling, or to make a personal data request, email [email protected].