Rigger privacy policy

Tester version of 21 October 2026 · Publisher: Bassú (legal name and address, in the definitive version) · Contact: seba@bassu.co

1. What this policy covers

Rigger is a desktop application for producing a live show, with its own broadcast engine and an artificial-intelligence producer; a browser extension (Chrome and Edge); and a cloud service. This policy covers all three and the rigger.live site. The extension also has a short policy of its own, which points here.

The essentials, before the detail:

• Your recording, your audio and your cameras' pictures stay on your computer. They go only to the streaming destinations you set up.
• The browser extension acts only on the tabs you connect or list in Rigger, or that Rigger opens for you. The other tabs of your browser are not read, and their addresses and titles never reach Rigger.
• Transcribing what is said happens on your computer. The audio never leaves it. The text of what was said — and, if you ask, of a page the assistant reads — does travel, as context, when you ask the AI producer something (section 2, D).
• Without an account, Rigger sends nothing to our service. The AI, keeping your projects in the cloud, phones as cameras and Kick's chat need you to sign in.
• We do not sell data, show advertising or use analytics or trackers.

2. What data we handle, why, and where it comes from

A. Your account (if you sign in). Your e-mail, your first name and the identifiers of your user and organisation, given to us by Clerk, the service that handles sign-in (with a code sent to your e-mail; we do not have your password). We use them to sign you in, to know which account what you keep belongs to, and to tell you if you ask to delete it.

B. How much, and when, you use the service. For each request to the AI or to saving: the time, the feature, the model, the number of tokens, the cost, whether it failed, a random session identifier, whether you were live, recording or neither, and the seconds on air. Never what was said. We use it to apply limits, measure costs, detect abuse and support you.

C. Your content in the cloud (if you sign in). Your projects: how your show is built (layouts, with their text; cameras, microphones and their names; mixer; streaming destinations; monitors; typeface names, never the typeface files), the pictures and design files you use, and your chat with Rigger. Also your audience's chat (item E). The summaries of each show and its transcript are planned but not yet kept. We do not upload your recording or your audio. Each piece of content is kept «sealed»: the service encrypts it with AES-256-GCM, under a data key of its own, itself protected by a master key that lives in our service's environment. It is not end-to-end encryption: we hold the key, so a forgotten password loses nothing, and whoever got into the service would reach both the data and the key.

D. The text sent to the AI. When you write to the producer, our service passes Anthropic (the model's provider) text only: never audio, images or screenshots. The text of a page arrives only when you ask the assistant to read it (below). Depending on the feature, that text includes: what you typed; the names of your layouts and of what is on screen, and the title (or the address, if it has no title) of what you attached; what was said in the last few minutes, as text and with the name of the microphone that caught it (which is usually a person's name), and the summaries of what came before; up to 40 messages of your audience's chat from the last 5 minutes, with every question, even if you are not asking about the chat (including ones you hid from your guests); and the whole of the session's conversation with Rigger and the project's memory; and, when you ask the assistant to read or look something up in a page (in a tab you connected, listed in Rigger or that Rigger opened for you, through the extension of item J), the text visible in it and the labels and kinds — never the values — of its links and form fields: the extension hands it to the application as data, not as instructions, and it becomes part of what the assistant passes to the AI to answer you; what the assistant tells you about the page stays, like the rest of the conversation, in your chat with Rigger. Web searches are made by our service with Brave (optional), which receives only the words of the search, not who asked. Anthropic deletes what it receives within 30 days at most (29 for batch summaries; up to 2 years if its safety systems flag a request) and, under its commercial terms, does not use it to train its models. We do not keep that text, except the optional diagnostics (item K) and what you yourself keep (your chat with Rigger).

E. Your audience's chat: other people's data. Rigger reads the chat of the channel of your own that you linked on Twitch, YouTube and Kick: the writer's display name, their identifier on the platform, the text, the time and the kind of message (for example a contribution or a subscription). It passes through your computer's memory, is written to disk as part of the session, is shown on your console and on your guests' screens (on your local network) and, if you sign in, is uploaded sealed to the cloud. Twitch and YouTube chat comes straight from those platforms to your computer; Kick chat passes through our service, which relays it without writing it anywhere, and the token that gives access to your Kick channel also passes through it. There is no switch to stop keeping the chat. A message that the platform deletes, or from someone it bans, is removed from the kept chat and from what Rigger answers. If you unlink an account, that account's chat is deleted everywhere after 7 days to change your mind, or at once if you choose «Borrar ahora».

F. What stays on your computer. Your projects and sessions (including the chat with Rigger and the project's memory), your recordings (by default in the Rigger folder of your Movies or Videos), your settings and the program's working logs. Credentials (the Twitch, YouTube and Kick tokens, stream keys, your Rigger sign-in and your phones' certificates) go to your system's keychain (macOS Keychain, Windows Credential Manager). Your project files are not encrypted on disk.

G. Microphone, camera and screen. Rigger's broadcast engine opens your devices, composes them, shows them and records them only when you say so, and sends them only to the destinations you turn on. Transcription runs on your computer with a model that ships with the application; the audio is sent nowhere. Rigger has no cloud speech model.

H. Phones as cameras. The phone's picture and sound go from it to your computer inside your local network, without passing through our servers or any relay service. Our service only connects the two ends at the start: it forwards short signalling messages (which include your local network's addresses), without keeping or logging them. The phone's name and certificate are kept in your keychain.

I. Guest screens («Monitor»). They show the state of the show, the script and your audience's chat (names and text) to the devices you paired, inside your local network.

J. The browser extension. A tab becomes connected only when you click Rigger's icon, press its keyboard shortcut or choose its entry in the right-click menu; nothing is connected before that. From a connected tab, the extension carries the page's picture and sound, and its address, to the Rigger application on this same computer, over a connection that never leaves it (a WebSocket to 127.0.0.1 and the browser's native-messaging channel). When you choose «Listar en Rigger» on a page, a link, an image or a video, it tells it that address too, and for a tab you involved some other way (for example by marking a part of it) it tells it the page's address. It never tells it an address with its #fragment or with a user name and password in it, and when a connected tab goes to another site it tells only the site's name, until you click again. It does not send, store or show what you type or what is in a form or a password field: it hears that you typed (it counts the event, never the text) and, when you connect a tab, checks inside the page whether any field differs from the value the page gave it, and keeps one yes or no. When the Rigger application asks, for its assistant, in a tab you connected, listed in Rigger or that Rigger opened for you, the extension reads the text you can see in that tab, lists its links and form fields (their labels and kinds, never their values), scrolls it and, only after you confirm in the extension's own prompt for anything risky, clicks or types in it; password and payment fields are refused. The answers go to the Rigger application on this computer and the extension keeps none of them. The other tabs of your browser are not read, and their addresses and titles never reach Rigger. The extension has no server, account, analytics, advertising or remote code, and sends nothing to its publisher or to anyone else; it keeps each tab's state in the browser's session storage, deleted when the browser closes. On the extension stores' forms this is declared as «web history» (the address of pages) and «website content» (the picture, the sound and the text of the tabs above). We do not sell or transfer this data to third parties outside the permitted uses, do not use it for anything unrelated to the extension's single purpose (bringing web pages into Rigger) or to decide on credit or lending. What the Rigger application then does with it is what this policy says (items D, E and G). The extension also has a short policy of its own, with the same content in its own scope.

K. Diagnostics, only if the account holder turns them on. For at most 24 hours, the service can keep the text of your requests to the AI and of the answers (with addresses and the titles of what you attached replaced by «[material]»; what you typed, what was said and chat lines do stay), unencrypted, and deletes it 7 days after the window ends. Our staff can read it only through a function that leaves a record. Today the application has no control to turn it on.

L. Logs and network addresses. Our service does not store IP addresses in its database, and its working logs carry no content, e-mails or addresses: only the route, the account, the session identifier, the status and the time, kept 7 days at Render. The third-party services we use necessarily see the network address from which their user connects. The phone relay keeps addresses in memory only, for a minute, to limit abuse. The images and videos of search results you display are downloaded from their sites of origin, which see your address.

M. Cookies. The application uses no third-party cookies. Our service uses none. The phone page keeps a certificate and the language in the phone's own storage. The administration panel (internal use) uses three technical cookies. Clerk's sign-in pages use Clerk's own cookies. This page uses no cookies or scripts.

N. What we do not handle. No advertising, analytics or trackers in the application. We handle no payment data: there is no billing today. The application does not look for updates on its own.

3. Who we share data with

We do not sell your data or share it for advertising.

4. Where it is kept

In the United States: our service and its database are in Virginia (Render); the daily copy, in Virginia (AWS us-east-1, Neon); Clerk, in the US; Anthropic does not publish where it answers from; Amazon SES's region is not defined. Your computer keeps its own. If you live outside the United States, your data is transferred there.

5. How long we keep it

6. How we protect your data

Connections use HTTPS. The content we keep in the cloud is sealed (section 2.C); the rest (e-mail, name, usage records) is kept unsealed. Our internal panel shows its staff the accounts, their members' e-mails and the usage records, but has no screen for sealed content, and the service logs every time it opens it for you. But the key lives in our service, and the service itself reads chats to give the AI context: it is a rule we keep, not a lock we cannot open. Your platforms' credentials are not kept by us: they stay in your computer's keychain.

7. Deleting your data and your account

There are four ways to delete, always whole (single messages are not deleted): (1) a session or a project, here and in the cloud; (2) from this computer only, to free space (the cloud keeps it and it comes back when you ask); (3) unlinking a platform account, which deletes its chat everywhere (7 days to change your mind, or «Borrar ahora»); (4) deleting your account.

Deleting the account is done from Rigger. This computer's projects are deleted at once (if you tick it, you keep your video). In the cloud, the account becomes «being deleted» for 7 days: you can read and download but not write, and if you sign in again within that time, the account is reactivated and everything comes back. We e-mail you when you ask, 2 days before, 1 day before and when it is done. After the 7 days, deletion is final: your projects, sessions, chats, files, the members' e-mails and whatever was linked to the account are deleted, and the backups stop holding them within 7 more days. What remains (with no expiry): the account's identifier, the usage records without anyone's name (cost, tokens, route, model), each member's Clerk user identifier and an access log with no personal data. Clerk's record (your e-mail and your sign-ins) is not deleted by Rigger today. Platform chats wait out the same 7 days; YouTube's also expire at 30 days. Uninstalling the application does not delete your local data.

8. Your rights

You can ask us for access, rectification, deletion, objection and a copy of your data by writing to seba@bassu.co. We answer within 10 calendar days. If you are in Argentina, the supervisory authority is the Agencia de Acceso a la Información Pública; if you are in the European Union, your country's.

9. The people who appear in your show

If you are a producer, you decide to read your channel's chat and who takes part. Rigger transcribes, on your computer, the voice of whoever speaks into a microphone, and that text may travel to the AI as context: it is your responsibility to tell your guests. Anyone who wrote in a chat and wants their messages deleted can ask at seba@bassu.co, and we delete them. For that data, you decide what it is used for; we act as your tool.

10. Minors

This tester version defines no minimum age; it will be defined in the definitive version.

11. Changes to this policy

We publish the new version at this same address, with its date and a list of what changed; a change that matters to you is also said in the application. Previous versions are kept.

12. Contact

seba@bassu.co.

What the definitive version will confirm

• The publisher's full legal name and address, and who the controller is under Argentine and European law.
• The account-deletion period (today, 7 days) and what is kept afterwards, and for how long.
• The third parties' retention periods (Anthropic, Brave, Clerk, Render, Neon, Cloudflare): this version's figures are taken from their public documents and have not been reviewed by a lawyer.
• Where the data is kept, and how international transfers are handled.
• How requests for access, a copy and deletion are answered, and within what time: today they are made by e-mail and answered by hand, with no export tool.
• How requests from authorities are handled.
• The minimum age to use Rigger.
• Which cloud features are on: this version describes the product as it is meant to be, and some parts are not yet available to testers.