Privacy Policy

Who we are

V.E.Y.R is software operated by you on your own instance. This policy describes how the V.E.Y.R software and the services that support it (together, "V.E.Y.R", "we") handle information. Questions: [email protected].

What we collect and where it lives

• Accounts you connect (for example, Instagram). When you authorize Instagram, we receive an access token and your public professional-account profile (username, name, follower and media counts) and, with your permission, the media, comments and messages needed for the features you use. This is stored on your own V.E.Y.R instance. Our sign-in service performs the confidential token exchange and does not retain your token afterwards.
• The account you create on your instance. Your login email and settings live on your instance.
• Operational logs on your instance (for example, messages you send or automations you run) so the product can show you your history. These live on your instance.
• What your instance sends us. A random install id and the public half of the key your install signs with, the installed release and update channel, the sharing level you chose, licence counts (how many systems, agents and modules), your licence tier and kind and, for a bought key, the key's opaque id (never the key itself), and the update state of your install (which release the web console runs, the last update applied and its date, whether an update was interrupted). That lets us match your install to your purchase for support and, if a key is revoked, stop it unlocking. At the default sharing level it also sends one word of health (ok or degraded) and how many checks passed, warned or failed, as counts only; you can lower the level to licensing only on the console's Telemetry page. If you choose the managed level, it also sends, for each edge device you run, a short code derived from its id plus its status word, platform class and agent release. The fleet-learning level is reserved: today it sends nothing beyond the default level. It never sends names, email addresses, network addresses, device names, file names or your content. The full list of fields is published in the product documentation and enforced in code on both ends: a field outside that list is refused by your install and, if it ever arrived, stripped by us before it is stored.
• What we keep of it. One record per install, holding only the newest report; the next report overwrites it. We keep no history of reports, we store no failure shapes, and we do not use anything your install sends to train models. Our operations records are version-controlled, so an overwritten record can remain in that history until we remove your install's record, which we do when you ask. On a self-hosted install you can switch the dial-home off entirely (set VEYR_NET_URL to off); your install keeps working within its last valid licence.

How we use it

• To show your insights, posts, comments and messages inside your console.
• To perform the actions you ask for: publishing, replying, sending direct messages, running automations.
• We do not use your content to train models, and we do not sell or rent your data.

Sharing

We share data only with the platform you connected (for example, Meta / Instagram) to perform the actions you request, and with the infrastructure providers that route requests. We do not share your data with advertisers.

Retention and deletion

Because your data lives on the instance you control, you delete it: open your V.E.Y.R Creator console, go to Connected accounts, and disconnect the account. This removes the token and synced content immediately. You can also remove V.E.Y.R from Instagram under Settings, Apps and websites, which voids the token. See our data deletion page for details.

Security

Connections use TLS. Access tokens are held only on your instance. Our sign-in service holds the app secret required for the token exchange and never ships it to instances.

Children

V.E.Y.R is not directed to children under 13 (or the age required in your region) and we do not knowingly collect their data.

Changes

We will update the date above when this policy changes. See also our Terms of Service.