Last updated · November 16, 2026
Privacy policy
BugBoard is built by a small team at ICXCNIKA OÜ, a company registered in Estonia. We collect the minimum data needed to run the service and we never sell it. This page tells you exactly what we hold and why.
What we collect
Account essentials (email, name, organization), the issues, comments, chat messages and files you create, a small set of product events about how your account is used (see “Retention and deletion”), and standard telemetry: our servers log requests together with your IP address, and a self-hosted analytics tool records page views and basic browser details. How long each of these is kept is under “Retention and deletion” below.
Retention and deletion
What happens to your data when you delete it, and what we keep anyway. Where something is not erased automatically yet, we say so instead of promising it.
- Content you delete. When you delete a task, comment, project, organization or similar record, it disappears from BugBoard at once. A job that runs daily then permanently erases it, and the files attached to it, from our live database and file storage once it has been deleted for 30 days.
- Not yet erased automatically. Chat messages: deleting one hides it, but its text is kept and is not yet erased by that job. Some other deleted records, such as AI agents and what they remember, are not covered by the job either. To have any of these erased sooner, email info@bugboard.ai.
- Logs. Server request logs, which include IP addresses, are kept for 7 days. Our activity log and the log of API (MCP) calls are stored in monthly blocks that are dropped once a whole month is more than 30 days old, so an entry is kept for between 30 days and about two months.
- Product events. We record a small set of events about how an account moves from sign-up to checkout, for example the first project or first task created, a connected repository, an import, a plan limit being hit, and the steps of a checkout. Each event is an organization id, a user id, an event name, a time, the kind of client (web, mobile app, API or MCP) and a few values from a fixed list such as the plan. It never contains your name, email, IP address or the text of your work. Events stay in our own database and are not sent to any provider. They are deleted after 400 days, except the “first project”, “first task” and “first MCP call” events, which are kept until the organization is deleted. When an organization or user is erased as described above, their events are erased in the same run.
- Backups. Deleting something does not change backups that already exist. Our nightly database backups are kept for 14 days. Backup files are also copied to two other servers, and those copies are not pruned on a schedule today, so older backup files can remain there beyond 14 days.
- Accounting records. Subscription and payment records, and the time entries, billing rates and billing items of workspaces that track time and cost, are kept as accounting records and are not covered by the 30-day erase. We keep them for at least seven years from the end of the financial year they belong to, as our bookkeeping obligations require. Nothing removes them automatically after that yet.
Where data lives
BugBoard runs on servers we rent from two EU hosting providers, OVH in France and Contabo (EU). The application and the primary database run at OVH in France; database replicas, file storage and backups run at Contabo and at OVH. The providers listed under “Subprocessors” also receive data. Where one of them can process it outside the EU, its entry says so.
AI processing
If you use the AI features in BugBoard, the text and code you choose to send, and for some features the task or comment text around it, are sent to OpenRouter, an AI gateway, which passes them to the model provider that serves the request. For text generation we ask OpenRouter to use only providers that do not store prompts or train on them, and not to fall back to other providers. The model we use for text generation is not available on OpenRouter's EU endpoint, so the provider that serves a request may process it outside the EU. If a project turns on duplicate-task detection, task titles and descriptions are sent to generate embeddings with a Google model. Those requests go to OpenRouter's EU endpoint, which keeps them with providers in Europe (the EU/EEA, the UK and Switzerland) and rejects the request instead of leaving that region. The Google endpoints for that model may keep a request for a limited time to detect abuse, so the no-storage restriction above does not fully apply to them. OpenRouter keeps account, billing and abuse-monitoring records, which it says may be processed in the US. An organization owner or admin can turn AI off for the whole organization in Settings → AI. BugBoard keeps your AI chat conversation like any other content in your workspace.
Subprocessors
These providers receive data from the service, and we list what each one gets. OVH, Contabo, OpenRouter and the model providers behind it, Resend, and Apple and Google (push notifications) process it on our behalf as our subprocessors; this list is the subprocessor annex of our Data Processing Addendum. Stripe, and the services you connect yourself, also receive data, as independent controllers.
- OVH (France). Hosting: application servers, the primary database and backup copies.
- Contabo (EU). Hosting: database replicas, file storage, backups and our analytics database.
- OpenRouter and the model providers it routes to. AI features. Text generation: the text you send, processed by the provider OpenRouter routes the request to, which may be outside the EU. Duplicate-task detection: task titles and descriptions, sent through OpenRouter's EU endpoint to Google in Europe. OpenRouter's account and abuse-monitoring records may be processed in the US.
- Resend. Email: your address and the content of the emails, including task titles and comment text in notifications, sign-in codes, invitations and onboarding emails. May process outside the EU.
- Apple and Google (push notifications). Mobile push: the notification text and your device token. May process outside the EU.
- Stripe. Payments: billing details for paid plans. Stripe is an independent controller for its own payment, fraud-prevention and compliance purposes. May process outside the EU.
- Services you connect. GitHub, GitLab, Google sign-in, imports from tools such as Trello and ClickUp, and webhooks you configure exchange data with BugBoard as you set them up.
Your rights (GDPR / CCPA)
You can export your data anytime from your account settings. To correct your information or delete your account, email us at info@bugboard.ai . We action every request within 30 days, in line with the GDPR. The three short onboarding emails we send in your first week each carry a “Stop these emails” link that turns off the ones not yet sent.
Cookies
We set three cookies. NEXT_LOCALE remembers your language and bb-dock-tiles remembers how many project tiles your side dock shows; each lasts one year. bb_oauth_state is set only while you sign in with a social provider, to protect that sign-in, and lasts 10 minutes. Your login session and your theme choice are kept in your browser's local storage, not in cookies. Page views are counted by Umami, an analytics tool we host ourselves, whose tracker sets no cookies. There are no advertising cookies.
Who runs BugBoard
ICXCNIKA OU operates BugBoard. It is the controller of the personal data of people who visit our website and of the account, billing and security data of people who use the service. For the content a customer's organization puts into its workspace (issues, comments, chat messages, files and similar), ICXCNIKA OU is the processor and the customer is the controller; our Data Processing Addendum applies to that. Read the Data Processing Addendum