Privacy and data
How Beringio stores, protects and shares what you and your team put into it.
Last updated: November 15, 2026
Who we are
Beringio (beringio.com) is operated by Berik Bazarov (individual), Kazakhstan (“we”, “us”), who is responsible for the data described here. Contact: hello@kiberberik.link
What we store
- Your account: the email you sign in with (we send sign-in codes to it) and the name you set.
- Your profile in each hub: the name, team role and contacts you set there.
- What your team creates in hubs: decisions and their history, the glossary, chat messages and files, the board (sticky notes, images, links), hub apps and their data.
- Sign-in sessions and connections of your AI apps. Codes, sessions and tokens are stored only as hashes.
- Short-lived server logs (IP address, requested path, status) for security and debugging.
Who sees it
- A hub’s content is visible to its members and to the AI apps they connect. Nobody outside the hub sees it.
- In a public hub anyone who joins sees its decisions, glossary, chat and members’ names and profiles.
- The email you sign in with is never shown to other members of a public hub. In a private hub only the owner and admins see members’ emails. AI apps never get the full address.
- If you haven’t set a name, a private hub shows the part of your email before the @ as your name — to its members and their AI apps. A public hub shows a neutral label like “Member 1A2B” instead. Set a name on your account page or in the hub to replace it.
What AI apps receive
When you or another member of a hub connects an AI app (Claude, ChatGPT, Cursor and others), that app can get, through Beringio’s tools, the data of the hubs its user belongs to:
- hub names, descriptions and topics;
- members’ display names, roles (owner, admin, member), team roles, the contact details a member chose to add to their hub profile, and the date they joined;
- chat messages and files, with their authors’ names and the time they were sent;
- decisions and glossary terms with their authors’ names, dates and history — including whether a person or an AI app made each change, and which AI app;
- board content with its authors’ names, and hub apps with their data;
- who is in the hub’s call right now;
- for the owner and admins of a public hub: the names of people removed from it.
AI apps never receive the full email address you sign in with, your sign-in codes or sessions. Two exceptions you control: a member with no name set appears in a private hub under the part of their email before the @, and anything a member writes into their hub profile as a contact (an email, a phone number) is visible to other members and their AI apps. What an AI app does with this data is governed by its provider’s terms and privacy policy.
Why we process it
- To provide the hub: store and show your team’s content to its members and their AI apps.
- To sign you in: send one-time codes to your email and keep your session.
- To detect conflicts between a new decision and earlier ones.
- To search decisions and terms by meaning.
- To keep the service secure and working: prevent abuse, investigate errors.
- To understand how the service is used: we count, per day, whether you opened the website and which Beringio tools your AI apps called and from which app (Claude, ChatGPT…). Only counts — never the content. The counts stay in our own database and are deleted with your account.
How it’s protected
- Everything travels over HTTPS.
- Chat messages and files are encrypted at rest with a separate key for each hub (AES-256-GCM).
- AI apps connect over OAuth: you approve each one, and you can disconnect any of them on your account page.
- Calls go through our own media server and are not recorded.
Recipients
- The database, files and calls run on our own servers: no third-party cloud storage or call service gets them.
- Resend — delivers sign-in codes; gets your email address and the code.
- Your own AI (Claude, ChatGPT, Cursor and others) gets the hub data your assistant asks for — under that provider’s terms.
- Anthropic (Claude API) — to find conflicts between decisions, gets the text of a new decision and related earlier ones.
- Voyage AI — for search by meaning, gets the text of decisions and terms to compute embeddings.
- YouTube and Wikipedia — on the website, videos and pictures that people put on a board load from those sites when you view the board. Inside AI apps the hub loads nothing from other sites.
- No ads, no third-party analytics or trackers: usage counts never leave our servers. The only cookie is the sign-in session.
How long we keep it
- Sign-in codes expire in minutes.
- Sessions last until you sign out or they expire; AI app connections — until you disconnect them.
- Your account and hub content — until you or the hub’s owner delete them.
- Daily backups are kept for up to 14 days, so deleted data disappears from them as they rotate.
- Server logs are short-lived and kept only for security and debugging.
Your rights
You can access, export, correct and delete your data, and object to its processing.
- On your account page: change your name, disconnect AI apps, download your data and delete your account.
- In each hub you can change your profile; a hub’s owner can delete the hub with everything in it; members can leave a hub at any time.
- For anything else, write to hello@kiberberik.link.
Children
Beringio is not for children under 13. If you believe a child under 13 has an account, write to us and we’ll delete it.
International transfers
Our servers and the providers listed above may process data outside your country. By using Beringio you understand that your data may be transferred there.
Changes
If this policy changes, we update this page and the “Last updated” date above.