Privacy policy

How .hub by N1 handles account, product and Google data.

Last updated October 31, 2026. Covers the service at hub.n1.team: the web app, the MCP server /mcp, event intake /ingest and the script /sdk/v1.js.

Who we are

.hub by N1 is an independent beta run by its founder, Kirill Dobrinov, as an individual; no company has been formed yet. When one is, this page will name it, and you will be told in advance. Questions about your data: k@n1.team; a person answers.

We have two roles. For the people who sign in to the hub (accounts, teams, tasks) we decide how data is handled and answer for it. For the visitors of your products (events from the script, Search Console, Metrica, payments) we process data on your behalf: your team decides what it is for, and it is up to you to inform visitors or ask their consent where the law requires.

What we keep about people who sign in

• An internal ID, when the account was created and last used, and the name you entered.
• Email if you add it or choose Google sign-in. Other registration methods may work without email.
• Your passkey: its public key and a device label. The private key stays on your device.
• Telegram: only the numeric ID of your private chat, if you link Telegram for sign-in and notifications. We don't keep your name, username or photo.
• Your session (a token hash, how you signed in, the device in words) for up to 365 days, renewed as you use it.
• An access log: invitations, sign-ins, keys, recovery, «sign out everywhere», without tokens.
• Agent keys: only a hash and prefix, a name, when they were used, and their limits.

We never ask for a password, phone number or documents.

What we keep about your work

Tasks, comments, the activity log (who did what, person or agent, with which key), products, strategy and goals, as you or your agent wrote them. Don't put secrets or other people's personal data there. Conversations with the Analyst are visible only to their author.

Connected sources are only those you connect: Search Console (up to 485 days of history), Yandex Metrica (up to 365 days), Stripe, RuStore, PostHog and Amplitude (daily counts), and Semrush exports. Source tokens and keys and the Analyst's model key are stored encrypted, agent keys only as hashes, and none of them reach the server logs.

Google data: sign-in and Search Console

Sign in with Google

When you choose Google sign-in or sign-up, we request openid, email and profile. We verify your email and Google account identifier (sub). We store their link to your hub account and the date it was linked, so we can recognize you when you return. We use your Google name when creating a new account; linking Google to an existing account does not change its name. We do not store your profile photo for this sign-in.

The ID token is verified on the server. Google ID, access and refresh tokens received for sign-in are not stored in the database. A workspace owner connects Search Console separately.

Connecting Search Console

With your permission, we receive the list of accessible sites and data for the sites you select: queries, pages, countries, devices, dates, clicks, impressions, CTR and positions; URL indexing inspection results and sitemap information. We use these for SEO reports, goals, tasks, period comparisons and answers to your questions about your product.

For an OAuth connection we store the Google account email, granted scopes and an encrypted refresh token. For a service account we store its email and encrypted key. Search Console access tokens are cached in server memory and used within their Google-issued lifetime.

Access and use

Site data is available to members with access to the relevant product and their agents. When you ask the Analyst a question, relevant aggregates, including Search Console data, may be sent to the owner's selected Anthropic or OpenAI provider to answer that question. Your agent receives data when it calls hub tools using the access you granted it.

We do not sell Google data, use it for advertising or use it to train generalized artificial intelligence models. Human access to Google data by the service is allowed with your explicit consent for specific assistance, to investigate security threats or when required by law.

The use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, disconnection and revocation

Your Google sign-in binding is retained until you delete your account or your request to remove the binding is fulfilled. Downloaded Search Console history remains in the workspace until that workspace is deleted; disconnecting a source does not erase its history. Google's available download history and retention of data already downloaded to the hub are different periods.

The owner can disconnect Search Console in Connections. This removes its stored connection credential and its cached access tokens and stops further updates. Revoke the OAuth grant in your Google Account connections. For a service account, delete its key in Google Cloud or revoke its access to the site in Search Console.

Revoking Google's grant does not end an existing hub session or erase downloaded history. End sessions in your account settings. To delete an account or workspace data, see Deletion and export. Questions and requests to remove a Google binding: k@n1.team.

Events from your products

You choose the mode when you create a product, and it can't be changed later.

• No user IDs. Events become daily totals on arrival. No raw events, no user or device IDs, no IPs or user agents are stored. A random delivery ID is kept for 48 hours so a retry isn't counted twice. Retention comes from a device ping with no ID; cells under five are not shown.
• With user IDs. The user ID becomes a salted hash on arrival; the original ID is not stored. Raw events are kept for 396 days (about 13 months), then deleted; daily totals without IDs are kept indefinitely.

IPs and user agents are written neither to the database nor to logs. The user agent is used once, to leave out bots; the IP lives in memory only as a rate-limit key.

Who sees the data

Data belongs to a workspace and never mixes with another's. The owner decides which products a member sees; an agent sees exactly what its person sees, and every action it takes is signed. The hub's operator has technical access to the database and looks only to fix the service or when you ask.

Who we share data with

• Netlify (hosting, functions, database; United States): everything the hub stores.
• Telegram: the chat ID and the notification text, if you linked it.
• Google, Yandex, Stripe, RuStore, PostHog, Amplitude: requests made with your key, if you connected that source.
• An email provider: the address and the message, only if you have an email and email is on.
• An error-reporting service: error texts without personal data, if it is on.
• Anthropic or OpenAI: a question to the Analyst and tool aggregates, only if the owner added their own model key.
• Your agents: exactly what you allowed with a key or a connector; from there, that agent's rules apply.

We don't sell data or give it to ad networks.

Cookies

A session cookie, a separate cookie for Google sign-in (up to 10 minutes), and a short-lived cookie while connecting Google Search Console or Yandex. No analytics or ad cookies; the hub's script sets none.

Deletion and export

In Team → Deletion, an owner can delete the workspace and each person can delete their own account. If you are the only owner of a team with other members, transfer ownership first. Account deletion ends its sessions, revokes agent keys and removes the Google binding, personal sign-in methods and profile data. Shared work history and the access log may remain under an anonymized “Deleted member” record.

Workspace deletion removes its products, connected data including downloaded Search Console history, and saved credentials. The owner can export tasks, products and money as JSON, and events and counters as CSV. Deleted data leaves backups when their retention period expires. For help with deletion or export, contact k@n1.team.

Task attachments are held in private file storage and follow current task access. JSON exports contain their metadata; files are downloaded separately. Team attachments remain with the team after a member deletes their account. Deleting a file or team ends access immediately; physical file removal is retried until storage confirms it.

Your rights

You can ask for a copy of what we hold about you, and to correct, delete, restrict or object to its processing. Most of this is self-service in the app; for the rest, write to k@n1.team and we answer within 30 days. You can complain to the data protection authority where you live or work.

Children and changes

.hub is not for anyone under 16. If a breach affects your data, we tell you and, where the law requires, the regulator. We announce changes to this policy in the hub in advance.