Privacy notice
How Benaiah handles your account, conversations, teammates and connected services.
Who is responsible
Benaiah AI Ltd, company number 17403584, is the controller of personal data processed to provide and operate Benaiah.ai. Our registered office is 167–169 Great Portland Street, 5th Floor, London W1W 5PF, United Kingdom. Contact [email protected] for privacy questions or requests.
Information we use
- Account and sign-in: your name, email, account identifier, sign-in method and verification records, account preferences, and the public credential information needed for passkeys. Email can be supplied directly during sign-in or through an identity or payment provider. Sign-in emails use the configured email-delivery service. Device biometrics and passkey private keys are not sent to Benaiah.
- Your workspace: prompts, conversations, voice input and transcripts, uploaded files, teammate settings, memories, task instructions and results, schedules and activity you choose to save or sync. Relevant context is supplied to the model or tool used for your request.
- Connected services: account identifiers, authorisation tokens and the records your selected tools need, such as authorised email, calendar or file content. We obtain these from you and providers you connect. Access depends on the permissions granted. Desktop-local connections and cloud connections store credentials differently; local-device storage is not a promise that every integration credential remains on your device.
- Calls and voices: a verified callback number, verification status, call identifiers, direction, duration, delivery status, usage, and audio or transcripts where generated by the enabled voice service. A consented voice clone involves processing the recording supplied for that purpose.
- Payments and wallets: payment-provider references, amounts, currencies, receipts, Credits purchases and usage, wallet addresses, networks, transaction hashes and approval records. Payment and onramp providers may collect card, bank and identity-verification information directly. Benaiah receives the status and records needed to operate and reconcile the transaction; do not send payment credentials through chat.
- Operations: request metadata, approximate network location, timestamps, model and feature selection, latency, token usage, errors, security and approval events. Support messages include the information you choose to send.
Why we use it
We use account information, requested content, authorisations and payment records to provide the service you request and administer the contract with you. Our legitimate interests support proportionate security, fraud prevention, troubleshooting, service reliability, cost monitoring and handling enquiries. Legal obligations may require accounting records, responses to valid legal requests and protection of your data rights.
Where consent is required, including optional improvement use and applicable optional tracking, it must be specific and can be withdrawn. Declining optional improvement use does not prevent ordinary use of Benaiah. Withdrawing consent does not undo processing that was lawful before withdrawal. Do not provide sensitive personal information unless the selected feature is appropriate and you have the necessary authority.
Website analytics and device storage
Our website analytics code records page visits, approximate location, browser and viewport information, referring-page paths, named links and buttons selected, sections viewed, scrolling and time spent. It starts only after you choose Allow analytics, uses a session-storage identifier, and respects Do Not Track and Global Privacy Control. You can withdraw from Analytics choices on this page or any page showing that control. A necessary preference cookie remembers your choice for up to six months; it contains no account identifier. Your choice applies to this browser and website hostname. It does not record text entered into forms or chats, payment credentials or file contents. Hosting and security logs can still record requests when this tracker does not run.
Essential cookies and device storage support sign-in, security, preferences and workspace continuity. Connected providers may use their own storage during sign-in or checkout. Optional analytics stays off until you make an affirmative choice; declining does not prevent ordinary use. This privacy page, the terms page and the support page do not load our optional site tracker.
Optional improvement use
“Help improve Benaiah” is off by default. If enabled in Settings → Personalisation, future eligible conversations may be redacted and placed in a separate operator-only Research Library for review, evaluations, prompt improvement or possible model development. Entry into the library does not automatically train a model. Redaction reduces exposure but is not a guarantee of anonymity.
We record the consent and notice version. Turning the setting off stops future capture and removes pending candidates. Contact us about reviewed material; we will explain any limits where content has already been incorporated into an evaluation or model-development process. Provider data-use settings are separate from this Benaiah preference.
Contributor models
Auto High, the default in-app Auto level, may use Meta's Muse Spark 1.3 Contributor through OpenRouter. Contributor is also a separately labelled manual model. Requests sent to Meta can include your prompt, conversation context and any content included for the model to process. Meta may use prompts and outputs to improve its products. This is a condition of the Contributor tier, separate from Benaiah's own optional Research Library and improvement programme.
The Help improve Benaiah setting does not control Meta's use of Contributor requests. To avoid sending new requests to Contributor, select another Auto level or a non-Contributor manual model. This does not undo data already sent. Existing standard Muse Spark selections are not automatically changed to Contributor. Native Codex Responses uses a separate compatible route, and Auto High may use another provider for native private-file search or connected tools, or if OpenRouter funding is unavailable.
Do not use Contributor for secrets, confidential client material or sensitive personal information. Review OpenRouter's model disclosure and the provider's applicable terms before choosing it.
Connecting external assistants to your teammates
Connecting the Benaiah plugin authorises the account scopes shown on the consent screen. We receive the instructions and context supplied through tool calls, not automatic access to your entire ChatGPT history. The plugin can return teammate names, task titles and results, and callback status to ChatGPT. ChatGPT handles those responses under the terms and settings applicable to your OpenAI account.
The separate Claude integration for Claude Code and Cowork receives only context explicitly supplied through its tools and can return teammate names, task titles, statuses and results to Claude. It does not automatically access Claude conversation history, local files, memories or connected apps. It cannot initiate telephone calls or completion callbacks. Claude handles the returned data under the terms and settings of your Anthropic account.
The initial integration sends supplied task context and relevant teammate preferences to OpenAI for background analysis or drafting. It does not browse the web, retrieve private files or act in connected apps. A requested callback uses the verified personal number in your Benaiah account and the configured voice and telephone services. Verification codes belong on the Benaiah verification page, not in plugin tool calls.
Disconnecting revokes the relevant credentials when the revocation flow is completed; it does not itself cancel already requested work or recall a placed call. Cancel queued tasks separately, and contact support if you cannot revoke access. Private reviewer credentials, where enabled, are restricted to an explicitly provisioned sample account.
How long information is kept
Saved account, workspace and synced history records are kept to provide the account and restore your work, until removed through supported controls or a deletion request, subject to necessary legal and security exceptions. Operational records are kept for service support, security investigations, reconciliation and any applicable legal requirements. These stores do not all have the same automatic expiry: website archives, provider logs and operator copies require separate retention and deletion handling. For records without a fixed expiry, the retention review considers whether the requested service still needs the record, whether a payment, complaint or security investigation remains unresolved, whether a legal obligation requires it, and whether the purpose can be met with less identifying information. Contact us for the period or decision applying to a particular record. We assess deletion requests across the relevant systems, rather than treating a single account deletion as proof that all copies have been removed.
Goals on Alexa is a separate, optional setting in your Benaiah Goal Calls screen. It is off by default. If you enable it and link your account, the skill can send your saved goal titles, latest permitted journal update and next scheduled call details to Amazon to speak on your Echo. Anyone using that linked Alexa account or Echo may request this information. You can turn the setting off in Benaiah; this also cancels pending extra Goal Calls requested through Alexa and revokes further goal access through the skill. Your existing goal and account history preferences continue to apply. An extra Goal Call uses your verified Benaiah recipient and the private team number, requires a separate confirmation, and leaves the recurring schedule unchanged. We keep the latest extra-call request and its pseudonymous Alexa account/session identifiers with your goal records for confirmation, duplicate prevention and delivery reconciliation. This record does not have the public callback store’s 30-day expiry. The private goal journal is separate from public-demo call reports.
For a callback requested through Alexa, we use the UK phone number you explicitly allow Alexa to share, or the verified number in your linked Benaiah profile, and ask you to confirm the teammate, approximate time, destination and outgoing number before booking. You do not need a Benaiah profile for a public-team callback. A profile phone number from Amazon is not proof of who is speaking or who answers, so the recipient must press 1 to continue. We do not match an Alexa user to a Benaiah account by phone number. Confirmed callback records, including a pseudonymous Alexa identifier and delivery status, expire from our callback store after 30 days. You can ask Alexa to cancel a pending callback. Public-team callbacks use 01234 386575 and their reports go to the Benaiah team as described below. Calls using a linked member’s own active team-plan number use that plan’s allowance and stay in that member’s call history; those private call reports are not sent to the public-demo report inbox.
A short personal reminder dictated to Alexa is shared with Amazon as part of the request and read back for your confirmation. We store it with the callback record and, for a verified private team-plan call, supply it to the voice provider and save it in that member’s call record. The callback copy follows the 30-day callback expiry; the member’s call history follows the account retention described above. Personal reminder content is not sent to the public demo route or public-demo report inbox. A combined request sends only the computer-work clause to the selected computer integration; the reminder and goal check use their own services.
For calls to our public demo number and requested callbacks from it, we keep a call summary and operational report for 30 days and email the report to the Benaiah team. When you request and confirm a callback, we use your incoming caller ID to return that call at the agreed approximate time. Callback booking and delivery records expire from our callback store after 30 days. Relevant conversation context for the returning teammate expires after 24 hours. For incoming public demo calls, we may match the caller ID to a verified phone number on a uniquely matched or explicitly chosen Benaiah profile, use the saved first name in the greeting and retain a tentative human association in the 30-day call report. Unknown, withheld or ambiguous numbers receive the normal greeting. Caller ID is not proof of your identity or access to an account. Captured speech text used to prepare the report expires from our reporting store after 24 hours; we do not make an audio recording in that store. Email copies and provider records have separate retention. Public SMS conversations are kept separate by sending number, with recent conversation context limited to 20 messages. Conversation and message delivery records expire from our SMS store after 30 days. Sender numbers are used for replying and opt-out handling, not as proof of account identity. Public callers and texters do not receive access to the account owner’s private chats, files or connected tools.
When you ask a public telephone teammate to carry out research, calculations or document preparation, we send the agreed task and necessary context to an isolated OpenAI-hosted workspace. We do not provide it with your account credentials or access to your computer. The task, result and small prepared files are kept in our task store for up to 24 hours so the conversation or a separately confirmed callback can pick up the result. We request deletion of the provider session after collecting its result or confirming cancellation. OpenAI provider retention applies separately; this service does not use Zero Data Retention and hosted execution currently uses US infrastructure. We do not automatically attach profile records or caller-ID fields to cloud tasks.
Our Axiom application-event and Vercel-log datasets are configured to retain events for 30 days. This does not set the lifetime of separate source records, call-provider records, exports or backups.
Assistant-connection task and dispatch records use a 90-day storage lifetime, which can restart when a record is updated. Plugin access tokens expire after one hour. Refresh tokens rotate and have a 30-day lifetime; temporary replay and revocation records remain to prevent credential reuse. Provider-side background responses, logs, recordings and backups follow the relevant provider configuration and terms, rather than automatically inheriting these periods.
We retain a minimal, versioned record of account-connection acceptance and the telephone eligibility and processing notice for five years from each acceptance, with longer retention where required for a specific legal obligation or dispute. The record contains a pseudonymous account identifier, the accepted notice version, the time and whether telephone use was enabled and adulthood confirmed. It does not contain your date of birth, telephone number or call content. This record supports our consent and contractual obligations; disabling calls stops future call starts but does not erase evidence of earlier acceptance.
Billing and transaction evidence may need to be retained for accounting, dispute resolution and legal obligations after account closure. Research Library candidates follow the consent and review rules described above. Deletion may require a support request across separate systems; we do not promise that disconnecting an app immediately erases all stored records.
Your choices and rights
You can manage connected services, saved content and the improvement setting in Benaiah, and ask us for access, correction or deletion. Depending on the circumstances, you may also have rights to restrict processing, object to processing based on legitimate interests, receive portable data, or withdraw consent. We may need proportionate verification before releasing or deleting account information.
Your right to object
You can object to processing based on our legitimate interests by emailing [email protected]. Explain which processing you object to so we can assess and respond to the request. Where the law requires us to stop, we will do so.
Email [email protected]. We normally respond to data-rights requests within one month; if an extension or exception applies, we will explain it. You can complain to the UK Information Commissioner’s Office or the appropriate authority where you live.
Providing account and transaction information may be necessary for the relevant service; if you decline it, that feature may not work. We use automated controls for access, fraud checks, usage limits and spending permissions. Contact support to challenge a restriction or billing result. AI-generated output is not a decision you must accept.
Updates
We will update this notice when data handling changes and give additional notice or obtain new consent where required. Material changes do not retrospectively authorise a new use of previously collected information.