Privacy policy

Scope

This policy covers logosvox.com and the surfaces that run alongside it — app, chat, studio, desktop, products and admin. It does not cover projects that people publish with LogosVox: those run on a separate domain, lvox.app, and their authors decide what happens on them.

What we collect

• Account details. You sign in with Google or GitHub; we receive your email address, and your name and avatar when the provider supplies them. We never receive your password.
• Your handle and profile. The address logosvox.com/@yourname, plus anything you choose to put on that page. A profile is private until you make it public.
• What you create. Conversations, applications, projects, files and the settings that belong to them.
• Usage and billing counters. Storage consumed and AI credits spent, so a plan's limits can be applied.
• Model provider keys, if you add your own. These are encrypted before storage — see below.
• Operational records. A security audit log of significant account events, such as an account becoming an administrator.

What we use it for

To run the product: to sign you in, to keep your work, to show your public profile if you have asked for one, and to apply the limits of the plan you are on.

To keep the platform safe: to investigate abuse, to hold an audit trail of privileged actions, and to meet a legal obligation where one applies.

We do not sell your data, and we do not use your private content to train models.

AI processing

When you use a feature that calls a language model, the content of that request is sent to the model provider that serves it in order to produce a response. That is what makes the feature work. What each provider then does with the request is governed by that provider's own terms.

If you supply your own provider key, requests are made against your account with that provider, under your agreement with them.

How provider keys are held

A key you enter passes through the browser exactly once. On the server it is encrypted with AES-256-GCM and kept in a cookie that page scripts cannot read. Requests to a model do not carry the key in their body; the server unlocks it. The interface only ever shows a masked summary such as ••••a1b2.

The cookie is specific to the host that set it, so a weakness on one surface does not reach the keys held by another.

Who else sees it

Only the service providers needed to run the platform: our hosting and database providers, our file storage provider, the identity provider you chose to sign in with, and the model providers described above. Each receives only what their part of the job requires.

How long we keep it

Your account and its contents are kept while the account exists. Sessions expire thirty days after they are issued. When you delete your account, its content is removed; audit records of security-relevant events may be kept longer where there is a legitimate reason to, and backups age out on their own schedule.

Your choices

You can see and change your profile at any time, make it private again, export or delete the work you have created, and close your account. Depending on where you live you may also have a statutory right to access, correct, export or erase your personal data, and to object to some processing. Write to us and we will act on it.

Age

LogosVox is not intended for children. Do not create an account if you are under 16, or under the minimum age that applies where you live if that age is higher.

Changes

The platform is in beta and this policy will change as it does. The revision date at the top of this page always reflects the current version, and a material change will be announced before it takes effect.