Privacy policy
Last updated: 2026-08-22
Arkush is a tool for building dashboards. This page says what this instance — the one at arkush.app — stores about you, why, and what you can do about it.
This instance is operated by Oleh Omelchenko, located in Kyiv, Ukraine. Write to [email protected] with any question about this policy or about your data.
Other organisations can run their own arkush installation on their own servers. If you reached a different installation, that installation's operator holds your data, not us.
Arkush is in alpha
This instance runs pre-release software. The document format still changes without migration, so dashboards can break or be lost between updates. Keep an exported copy of anything you would mind losing, and keep personal or otherwise sensitive data out of the dashboards you build here.
What we store about you
| What | Why | How long |
|---|---|---|
| Your email address | To identify you, own your dashboards, and record who changed what | Until you ask us to delete your account |
| Dashboards you create | They are the product | Until you move them to the trash, plus up to 70 days (see below) |
| Data you save into them | Charts read saved data, not live queries | With the dashboard, including earlier versions (see below) |
| Comments you write | To show them on the dashboard | Until deleted; a deleted comment leaves a marker with your address |
| Files you upload | To build dashboards from them | Until you delete them |
| Connected agent grants | So an AI agent can act as you over MCP | Until you revoke the grant |
| Server logs | To operate the service and investigate faults | 30 days |
Server logs record the request, the account that made it, and the result. They never record the contents of a dashboard, a query, or a token.
We use this information to run the service. We do not sell it, we do not use it for advertising, and we do not use it to train machine-learning models.
How we protect your data
- Traffic is encrypted on every hop: your browser talks to the service over TLS, and the service talks to Google's APIs over TLS.
- Stored data is encrypted too. Dashboards, saved data, and uploaded files live in Google Cloud Storage, encrypted at rest with AES-256.
- Every request re-checks who you are. A dashboard is reachable only by its owner, the people it is shared with, and whatever visibility its owner set. Administrative functions are restricted to named accounts.
- Your Google tokens never reach our server. When you connect BigQuery or a sheet, the token stays in your browser and goes only to Google's own APIs. We do not store it, log it, or transmit it.
- We hold no Google keys. The server stores no service-account key files. Where it needs Google access of its own, it uses short-lived read-only tokens created at request time and thrown away.
Signing in
Sign-in uses your Google account. We receive your email address and nothing else — no contacts, no calendar, no Drive files, no profile beyond the address.
Connecting Google BigQuery or Google Sheets
You can connect your own Google account to read your own data. This is the part Google's rules call sensitive, so it is worth stating exactly:
- We ask for two permissions, and only at the moment you use each: BigQuery, read-only, when you run a query — arkush cannot write to your warehouse; and per-file Google Drive access, when you connect a sheet.
- Per-file access starts with the link you paste: Google's own dialog opens showing that sheet, and you pick it. After that arkush can read that file and nothing else in your Drive — not your file list, and not any file you did not pick. The permission Google attaches to a picked file is technically wider than reading, but arkush only ever reads sheets; it never edits or deletes them.
- The access token is created in your browser and stays there. It is held in your browser's local storage until it expires, about an hour. It is never sent to our server and never written into a dashboard.
- Queries run from your browser, directly to Google, under your own account. Our server does not see them and does not run them for you.
- What reaches our server is the result rows you choose to save into a dashboard. Those rows are then stored like the rest of the dashboard, and they are visible to anyone you share that dashboard with.
- Disconnect at any time from the same place you connected, or revoke arkush at myaccount.google.com/permissions.
Arkush's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
AI and machine learning
Arkush contains no AI models and calls no AI service. We do not use your data — including anything read from Google — to create, train, or improve any machine-learning model, ours or anyone else's, and we do not pass it to third parties for that purpose.
Separately, you can connect an AI agent you choose over MCP. An agent you connect acts as you: it can read and change the dashboards you can, and every change is recorded under your account. What that agent does with what it reads is governed by your agreement with the agent's operator, not by us; arkush itself sends nothing to any AI provider. You can revoke an agent's access at any time.
Who can see your dashboards
- A dashboard you create is private to you until you share it.
- People you share it with can see it and everything saved inside it.
- The operator of this instance can technically read what is stored on the server. We read your dashboards only to investigate a fault you report, to keep the service running, or where the law requires it.
- An AI agent you connect can read and change the dashboards you can — see the section above.
Deleting a dashboard
Deleting a dashboard moves it to the trash. It disappears at once for everyone it was shared with and for any connected agent, and its address stops working for them.
For 30 days it stays in Trash on your library page, and you can restore it yourself. Anyone who can edit that dashboard can restore it too. After 30 days we delete it and nobody can restore it.
Deletion is not instant everywhere. Our storage keeps earlier copies so that a mistake can be undone. Those copies expire within a further 30 days, and our storage provider holds its own recovery copy for 7 days after that. Everything is gone within 70 days of the day you moved the dashboard to the trash.
Changing a dashboard works the same way: the version you replaced stays in our storage for up to 37 days, then expires. Deleted files and deleted comments follow the same timetable.
Dashboards you keep only in your browser have no trash. Deleting one deletes it at once, and we never had a copy.
Where your data lives
This instance runs on Google Cloud in Belgium (europe-west1). Documents and saved data are stored in Google Cloud Storage in the same region. Google acts as our hosting provider and processes the data on our instructions.
Beyond hosting, arkush loads nothing from anyone else: no analytics, no error reporting, no fonts, no advertising networks. The scripts we do load from another site are Google's own, and each loads only when you use it: the sign-in library when you press Connect, and the file picker when you pick a sheet.
Cookies
Arkush sets no cookies of its own. Signing in sets one session cookie, which exists only to keep you signed in. There is nothing here to consent to, which is why there is no cookie banner.
Your rights
Write to [email protected] to:
- get a copy of what we hold about you
- correct something wrong
- delete your account and its contents
- object to how we use your data
We answer within 30 days. You can also export any dashboard yourself, at any time, from the dashboard itself.
When we delete your account we delete your dashboards, your uploaded files, and your comments. Storage copies then expire on the timetable in "Deleting a dashboard" above.
If you are in the EU or the UK and you think we have handled your data badly, you can complain to your national data protection authority.
Changes to this policy
If we change this policy in a way that affects you, we will say so on this page and update the date at the top. The current version is always here.