Privacy Policy

Last updated 6 November 2026. These Services, including synap.linkrra.com, are operated by Linkrra LLC, a Wyoming limited liability company, which is the data controller. Contact [email protected].

The short version

We collect the minimum needed to run an account and bill it. If you explicitly connect Google to Build, we also use the limited permissions you approve to deliver website messages to you and create requested appointments. We do not sell your data, use it for advertising, or use your prompts or Google data to train models.

What we store

Account: the email address, name and profile picture Google returns when you sign in. We never see or store a password.
Build projects: project settings, published pages, form submissions, delivery receipts and appointment details that the site owner chooses to collect.
Google connection: the email address and approved permission list, plus encrypted access and refresh tokens needed to perform the owner's requested Gmail and Calendar actions.
Billing: which plan you are on, what you were charged, and Stripe's reference for it. Card numbers are handled by Stripe and never reach our servers.
Usage: per-request token counts, the model used and the timestamp, so we can bill correctly and show you where your credits went.
Sessions: an opaque cookie token, stored only as a hash, so a copy of our database cannot be replayed as a login.

Google services in Build

Connecting Google to Build is optional and separate from ordinary sign-in. Build requests permission to send email through Gmail, create and manage appointment events, and check whether a requested time is busy. It does not request permission to read your inbox. We use these permissions only to send a website submission to the notification address chosen by the site owner, check appointment availability, and create the appointment the visitor requested. We do not transfer Google user data to advertising platforms or data brokers.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Voice receptionist

A Build owner may optionally request an AI voice receptionist. The receptionist identifies itself as digital, collects the details needed to handle the call, and may deliver a message or appointment to the owner's configured email and calendar. If recording is enabled for that business, the caller is told that the call is recorded. The business owner controls whether the receptionist is enabled and which destinations receive the information.

Your prompts and answers

Requests are forwarded to a serving node, answered, and the token count is recorded. We do not retain prompt or completion text for API requests, and we do not use it to train anything. Conversations you save in the site chat are stored in your account so you can return to them, and you can delete them.

The models are served on machines contributed by independent operators. We require operators not to retain request content, but we cannot audit every machine, so treat the service as you would any third-party cloud: do not send secrets, credentials, or data you are contractually barred from sending to a processor.

If a message is blocked by our safety filter or reported by another user, a short excerpt (up to 120 characters) is kept in a moderation log so we can review and tune the filter. It is keyed to a hashed identifier, not your account, and this applies even to visitors who are not signed in.

Requests that reach us through OpenRouter

When OpenRouter routes a request to Linkrra as a provider, it arrives on a dedicated key that we handle with zero data retention. No prompt or completion text is written down by our service, and that includes the moderation excerpt described above. We keep only the token counts, the model, the price and the timestamp, because OpenRouter is invoiced from them.

These requests are served only on GPU nodes that Linkrra itself operates, and the serving software on those nodes does not log request content. They are never forwarded to an upstream provider or to a machine run by anyone else. If none of our nodes can take a request, we refuse it and OpenRouter routes it elsewhere.

Who else sees anything

Stripe — payments, and it holds your card and billing details under its own policy.
Google — sign-in and, only after the Build owner grants the additional permissions, the Gmail and Calendar actions described above.
When our own capacity is short, a request may be served by a commercial upstream provider. Every request we send one is restricted, per request in our code and not just by account setting, to providers offering zero data retention — a provider able to store the request is refused before it can run one. We do not share your identity with them; they see the request, not who sent it. For a subset of models, API callers can additionally request "confidential": true, which restricts the request to a provider running it inside an attested GPU Trusted Execution Environment — the operator cannot read it even with root access to the machine, not merely a policy promise not to look; see the docs for which models support it.
We disclose data to authorities only where a valid legal order requires it.

How long we keep it

Account, project and Google connection records are kept while the account exists or until the owner disconnects the integration. Billing records may remain afterwards for as long as tax and accounting law requires proof of a transaction. Usage records are kept up to 24 months for billing history. Moderation log excerpts are reviewed periodically and cleared once no longer needed for filter tuning. Session tokens expire after 30 days.

Your choices

You can see your data on the account page, cancel a plan yourself, disconnect Linkrra from your Google Account permissions page, and ask us to delete your account by writing to [email protected]. Disconnecting stops new Google actions; deleting the account removes the stored Google tokens and project data that law does not require us to keep. We tell you what is left and why. If you are in the EU or UK you have the usual rights of access, correction, portability and erasure.

Cookies

One cookie, for your session, so you stay signed in. Local storage remembers your theme and sidebar preference. No advertising or cross-site tracking cookies.

Children

Linkrra is not for anyone under 16. We do not knowingly hold data about children, and we delete it if we learn we have.