Skip to content

Privacy policy

Last updated 18 November 2026

This page describes what the Bokyaa service (app.bokyaa.com, api.bokyaa.com), the Mac app and the iPhone and Android apps store and why. It is operated by Diginnovators Solutions Pvt Ltd, India, which decides what is stored and why.

What we store

  • Account: your name, your email address and a salted scrypt hash of your password. The password itself is never stored.
  • Sign-in sessions and devices: for each signed-in app, the platform (macOS, iOS, Android), a device name, when it was created and last used, and a SHA-256 hash of its token. Password reset links are stored only as a hash and expire after one hour.
  • Workspace content you create: assistants and their instructions, knowledge documents, conversations and messages, the actions assistants proposed and your approvals, workflows and their runs, memories, your dictation dictionary and style choices, and workspace members.
  • Screenshots (Pro and Team): when you share a screenshot of your Mac with a cloud assistant from the Mac app, or approve one the assistant asks for, the image itself is stored in our database with that conversation until you delete it. We do not redact it, and it can show anything that was on your screen, including other people's information and passwords, so check your screen before you share. Screenshots count toward your storage allowance. A screenshot uploaded but never sent is deleted within an hour. A single request to a model carries at most four screenshots; older ones stay stored but are not sent again. Screenshots in a run on your own Mac are not sent to us. Bokyaa is for people 18 or older and is not directed at children.
  • Keys and connections: model-provider API keys and MCP server headers you add are encrypted (AES-256-GCM) and never shown again, except their last four characters.
  • Provider connections: the model-provider keys you connect to the router are encrypted (AES-256-GCM) and never shown again, except their last four characters.
  • Router keys: only a hash of each key and its last four characters are stored, with its scopes and per-key usage counters. The key itself is shown once, when you create or rotate it.
  • Gateway request metadata: for each request through the router we store your user id, the router key id, the model requested and the model it resolved to, the provider, token counts, cost, status and latency. Prompts and replies are forwarded to the provider your workspace chose and are not stored by Bokyaa. We store no IP address and no user agent with these records.
  • Rate-limit counters: short-lived counters keyed by a hash, so that no email, address, token or id is stored in them. They are deleted automatically once they are no longer needed.
  • Bokyaa MCP server calls: when a router key calls the Bokyaa MCP server we record one audit row per call with the tool name, the outcome, the length of the input and the duration. We do not record the text of the request or the answer.
  • Usage and audit records: counts of model tokens and, once cloud speech is switched on, cloud voice minutes per workspace (to apply plan limits; a minute used by a website visitor also carries an anonymous visitor id), and a log of administrative actions in each workspace. Each screenshot upload or deletion adds a row with its time, size, dimensions and an internal user id, never the image. A Mac paired with a workspace also reports, for each tool call it handles, the tool name, its risk level, whether the call was approved, refused, started, finished or failed, the time and the device id. These entries are stored in the workspace audit log, which Bokyaa operators can read; a workspace-admin view of them is not available yet. Dictation and the local router are not reported. It never reports the arguments, messages, file contents, screenshots or script text.
  • Platform credit records: for each model turn that the platform model answered, we record per workspace the time, the model, the token counts and the cost charged against the plan's platform credit, so the credit can be enforced and shown on the billing page. We never record the content in these records.
  • Billing: your plan and the Stripe customer and subscription identifiers. Card details are entered with and held by Stripe; we never receive them.
  • Embedded chat widget: if a workspace puts an assistant on its own website, that site's visitors' messages are stored in the workspace with a random visitor identifier, not a name or email.

What stays on your devices

  • On the Community plan the Mac app runs models through Ollama and speech recognition and synthesis on your Mac. That audio and text do not reach our servers.
  • Voice audio is not stored. Cloud dictation and server text to speech are not switched on today: they work only once Bokyaa's operators set up a speech server, and none is set up. Once one is, a dictation clip is sent to it for transcription, and with spoken replies on, the text of the reply is sent to it to be turned into speech. Neither the audio nor the transcript is stored: the clip is held in memory for the request, and a spoken reply's audio is kept in memory for up to ten minutes so a repeat is not generated twice. The only record is the minute count with its source and, for a dictation clip, its size; for speech, the conversation id and the number of characters; and, for website visitors, an anonymous visitor id. The reply text itself stays in your conversation as before. Without a speech server, dictation is unavailable, and when the assistant has voice turned on, spoken replies in the web app and the website widget use your own browser's voice on your device, and only a voice your browser reports as local is used.
  • The apps keep sign-in tokens in the macOS or iOS Keychain, or in storage encrypted by the Android Keystore. The web app keeps one session cookie that is needed to stay signed in. We use no advertising or analytics cookies and no tracking across apps or websites.
  • Your browser keeps two local preferences, bokyaa-theme (light or dark) and the sidebar state. They are stored in your browser, never sent to a server.

Who processes it

  • DigitalOcean hosts the service and its database, in its Bangalore (India) region.
  • Cloudflare sits in front of our websites and the API as a network proxy and security filter, so your requests to them pass through its network.
  • The AI provider your workspace chooses (for example Anthropic or an OpenAI-compatible service) receives the messages, instructions, context and any screenshots needed to answer, sent with your workspace's own key or connection and under that provider's terms. This includes requests sent through the router. The one exception is the platform model, described in the next item, which a paid workspace with no key or connection of its own can use. If the key is on a provider's free tier, that provider's terms may allow it to use what you send; check them before you send anything sensitive. Providers keep what they receive under their own terms: Anthropic, for example, keeps API inputs and outputs for 30 days by default. Deleting something from Bokyaa does not delete the provider's copy.
  • The platform model (Pro and Team). When a workspace has no enabled connection and no model key of its own, its runs use a model that Bokyaa supplies and pays for, within the credit that comes with the plan. The Free plan never uses it, and neither do website visitors using an embedded chat widget or a connected channel. It is not used for images or audio (the platform model cannot read images). A workspace owner or admin can turn it off for the workspace in Settings ("Use the platform model"), and owners and admins see a notice about it the first time. Bokyaa sends these requests, with a key that belongs to Bokyaa, to NaraRouter (router.bynara.id), a service run by PT Nara Pemecut Digital in Indonesia. NaraRouter passes them to a model provider that it does not name to us and whose terms we cannot show you. What is sent: the messages, the assistant's instructions, the saved memories recalled for the turn, and the results of tools the assistant calls (which can include passages from your knowledge documents). Dictation cleanup and the assistant suggestions Bokyaa offers send text only. What is not sent: images, screenshots and audio, because the platform model cannot read images and a message with an image is refused rather than sent without it; and your memories and knowledge documents are not sent to be turned into search vectors, as no model is set up for that today. Chats a signed-in member starts, workflow runs (including scheduled ones) and background jobs can use it. Requests sent through the router gateway (chat completions) never use it. An assistant run started when a router key calls the Bokyaa MCP server can. NaraRouter's privacy statement (6 June 2026) says it does not store prompts or replies and keeps only request metadata and short-lived error diagnostics. The model provider behind it applies its own retention terms, which Bokyaa does not control. Bokyaa cannot tell you which tier the model provider behind NaraRouter runs on, and its terms may allow it to use what is sent, so do not send passwords, secrets or sensitive personal data through it. To avoid it, connect your own key or router connection, turn the platform model off in Settings, or use the Community plan.
  • Our self-hosted speech server, once an operator sets it up (none is today), transcribes cloud dictation clips and turns spoken replies into speech.
  • Stripe processes payments for paid plans.
  • Our email provider delivers password reset links and human-handoff notifications.
  • Services you connect, such as MCP servers or a Slack webhook for handoffs, receive what you send to them.
  • PostHog receives the error and crash reports described under "Error and crash reports", and only from an app or a deployment that was built or set up with Bokyaa's PostHog project key.
  • A trace collector that Bokyaa chooses receives the API traces described under "Error and crash reports", only if Bokyaa sets a collector address for its deployment. Its deployment configuration sets none today.

Where your data goes

Bokyaa's servers and database are in Bangalore, India. Cloudflare passes requests through its worldwide network. Stripe, our email provider and the AI provider your workspace chooses process data in their own countries, which may be outside India. When a workspace uses the platform model, the text of its requests also goes to NaraRouter in Indonesia and from there to a model provider, which may process it in other countries, including outside Indonesia. Bokyaa does not have a data processing agreement with NaraRouter. You can avoid this path by connecting your own model key or router connection, by turning the platform model off for the workspace in Settings, or by using the Community plan, which runs on your Mac. Error and crash reports, when they are sent, go to PostHog's US cloud by default; Bokyaa can point a deployment or an app build at another PostHog host.

How long we keep it, and how to delete it

  • Your data stays until you delete it, with these exceptions. Archived memories are removed automatically after 30 days. Gateway request metadata and the audit rows for the Bokyaa MCP server are deleted automatically after 90 days. The tool-call entries reported by a paired Mac are deleted automatically after 90 days. Other audit rows, including those for screenshots, are not deleted automatically: they stay until the workspace is deleted, and in a shared workspace they remain after a member leaves, under an internal id only.
  • Platform credit records stay until the workspace is deleted. When a member's account is deleted, the internal user id in the records they caused is removed and the rows stay; when a member only leaves a workspace, the rows keep their user id.
  • For the platform model, Bokyaa does not control how long NaraRouter or the model provider behind it keeps what it receives. NaraRouter's privacy statement (6 June 2026) says it keeps request metadata and short-lived error diagnostics; the model provider applies its own terms. Deleting a message, a conversation or your account in Bokyaa does not delete a copy held by either of them.
  • A screenshot stays with its conversation until it is deleted. You can delete a single screenshot (from its card in the Mac app or its line in the web chat) or the whole conversation, an admin can delete the assistant, or you can delete your account. Nothing deletes it automatically once it is sent. A deleted screenshot is gone from the database at once, but database backups run daily and are kept for up to seven days, so a deleted screenshot, like any deleted data, can remain in a backup for that long.
  • Delete your account at any time in Settings, in the web app or the iPhone or Android app. This removes your account, your sessions and devices, and every workspace where you are the only owner or admin, with all of its data. In workspaces you share, your private conversations, including any screenshots in them, are deleted with your account; things you created such as assistants and workflows pass to another owner or admin, and your membership ends.
  • For anything else, such as a copy of your data, including your screenshots, email [email protected]. We reply within 30 days and, for screenshots, send them as image files with a list of what each one is.
  • You can also ask us at that address to correct data we hold about you, or withdraw a consent you gave. You may complain to the data protection authority where you live: for people in the European Economic Area, their supervisory authority, and in India, the Data Protection Board of India.

Error and crash reports

  • Off by default: error reports from the web app and from the Mac app's main window are off by default. A signed-in person can turn them on in Settings ("Send error reports from this web app", or "Send error reports from this app window" in the Mac app). The choice is saved with your account, with the time you last changed it, and applies to both. The switch appears only in a build of the app that carries Bokyaa's PostHog project key; a build without one sends no reports.
  • Workspace setting: a workspace owner or admin can leave the choice to each member, turn error reports off for every member, or turn them on for every member whatever each member chose. In the Mac app the setting of the workspace you are signed in to wins over your own choice, and another workspace's off setting does not stop its reports. In the web app, while you belong to any workspace whose owner or admin turned error reports off, none are sent from any page; a workspace that turned them on for every member applies that on its own pages only, and on other pages, such as the dashboard, your own choice applies. A change reaches a tab you already have open when you next open a page in it. Each change to it is recorded in the workspace audit log.
  • Crash reports from the Mac app: a separate switch, "Send crash reports from the Mac shell", is off by default and needs no account. While it is on, a Rust panic in the app, including one the app recovers from, writes a small record on your Mac with the source file name (no folder), the line and column, the app version and the time; a native crash, such as a segmentation fault, is not recorded, and the panic message is never recorded, and at most five records wait. They are sent the next time the app opens, as the file name, line, column and version, only if the switch is still on and the build carries the key. Turning the switch off deletes every record waiting to be sent.
  • What an error report holds: a fixed set of fields: the error's name, its message shortened to about 240 characters, the stack (function names, file names without folders, lines and columns, and for each frame whether it is the app's own code), a fingerprint that groups the same error, its level (error or warning) and whether it counts as handled, which app sent it and, where they apply, the app version, the deployment's environment name (server reports), the API route template or the web page address with its workspace, conversation, assistant, run, workflow and document ids replaced, the method, the status, a request id and the part of the app. Before a report is sent, credentials, tokens, keys, cookies and email addresses are removed from its message and stack, and quoted text longer than 40 characters from its message. In a home-folder path the user name is replaced with ~; the rest of a path in a message can remain. The filter cannot recognise everything, so a short piece of text that appears inside an error message can remain. Nothing else from the request, your conversations, files, audio, screenshots or workspace is added to a report.
  • Not tied to your account: Bokyaa adds no account, user, workspace or device id to a report, but an id can still appear inside an error message (a database error can quote the values of a query). An error report is labelled with a random id made for that page load or app launch, a crash report with the time it was sent, and PostHog is told not to create a profile for either. Reports go straight from your browser or Mac to PostHog, so PostHog receives the network address they are sent from, as with any request.
  • Server errors and traces: these describe the service Bokyaa runs and are not a personal setting. When Bokyaa's deployment has the PostHog project key, a server fault in the API (an answer with status 500 or above) is reported in the same fixed shape, with the route template, method, status and request id. API traces (OpenTelemetry) are off unless Bokyaa sets a collector address, and go to a collector Bokyaa chooses. Their span attributes are limited to the method, status, route template, scheme, protocol version, handler type, database system and operation, so attributes such as query strings, network addresses, user agents, full paths and SQL text are dropped. Each span also carries its name, timing and outcome, with the service name and version. A failed span keeps its error status and the error's type name, but never the error's message, its stack trace or database error text. The web app, the Mac app and the phone apps send no traces, and the iPhone and Android apps send no error or crash reports.
  • How long: Bokyaa's code does not delete reports from PostHog; how long they stay there is set in PostHog for Bokyaa's project. Because Bokyaa adds no account id to a report, deleting your account does not delete reports already sent, and there is no account id to look them up by. Your own choice is deleted with your account; a change to the workspace setting stays in the audit log like other audit rows.

Who at Bokyaa can see it

Bokyaa operators can see workspace metadata, such as plans, usage and request counts, through our operator console. Every view is recorded. Router requests are stored without their prompts and replies, so the console cannot show them.

Changes

When what we collect changes, this page changes with it and the date above is updated. Questions: Support.