Our trust principle
Every output from the Boardku agent is explainable and verifiable: the SQL it ran, the reasoning steps it took, and the confidence in its answer are all visible in-product. The agent is read-only in v1 — it informs, it does not act on your source systems. You control every connection, and you can disconnect any source at any time. Trust is earned by being legible; we try to make every step legible.
Data handling
Boardku's v1 demo runs entirely in your browser. The local demo workbench stores its workspace in an in-browser Postgres (PGlite) and in your browser's localStorage; queries run on your device, and no business data from the local-only demo is persisted on Boardku servers. As we ship real connectors (see the connectors roadmap on our plans), each connector will document its own backend data path before shipping — what gets read, where the query runs, and what (if anything) is cached. We will update this page before any connector that changes this posture goes live.
Read-only guarantee (v1)
In v1, Boardku's agent never writes back to your source systems. It does not run INSERT, UPDATE, DELETE, or any data-mutating operation against a connected data source. It reads, it reasons, it explains — and that is the entire surface. Action-taking (write-back, side effects in third-party systems) is deliberately out of scope for v1; it's a trust boundary we don't cross until the read-only posture has earned that step. If a connector cannot honor read-only at the source level, we won't ship it as a v1 connector.
Encryption
Traffic between your browser and Boardku is encrypted in transit via TLS. The marketing site is served over HTTPS. The v1 local-only workbench stores its workspace in your browser's PGlite + localStorage, which inherits your device's protection model rather than a server-side at-rest encryption story. As real connectors and any server-side state land in v1.3+, we will document the encryption-at-rest posture for each, in this section, before that path goes live. We are not claiming a formal compliance certification today (see “What's coming next” below).
Sub-processors
We will list every third-party service that processes your data in this section. At the time of this page's last update, Boardku's v1 demo runs entirely in your browser and uses no sub-processors that touch your business data. Hosting (Vercel) serves the static marketing site and the static app shell only. As we add the first real LLM provider, the first hosted data path, or any other processor that touches your data, we will update this list before that connection ships.
Retention & deletion
Today, your workspace lives on your device. Clearing your browser data deletes everything Boardku knows about you locally; there is no separate account or server-side record to purge in the local-only demo. Once accounts and any server-side state land, you will be able to request deletion of your account and all associated data; we will commit to a published turnaround window at that time, and we will update this section before that path ships.
Security contact
Found a security issue? Email keronelau@gmail.com. We appreciate responsible disclosure: please give us a reasonable window to fix and ship before sharing publicly, and we will credit you (with your permission) when we do.
What's coming next
Where the v1 posture is honestly thin, this is the trajectory:
- SOC 2. Not currently certified. We plan to begin a SOC 2 Type II program once the connector epic (v1.3) stabilizes and we have a real backend posture to audit. Not a present-tense claim; explicitly on the roadmap.
- ISO 27001 / PCI / HIPAA. Not currently certified. ISO 27001 may follow SOC 2 once we have enterprise demand; PCI / HIPAA depend on use-case fit. We will not market a certification we don't hold.
- Single sign-on (SSO / SAML). Planned for v1.4 alongside real auth — see the Enterprise tier on pricing.
- Independent penetration test. Planned once a real backend ships in v1.3+; we will publish a summary once it completes.
- Status page. Coming with the first hosted data path. Until then there is no production data surface to report on.