Privacy Policy

This Privacy Policy explains how Viralinx LLC, a Wyoming limited liability company (“Viralinx”, “we”, “us”, “RISR”), handles personal information when you use RISR: the RISR Studio apps for iPhone, iPad, Mac, Windows and Android, the risr.app website, and RISR's online services (accounts, cloud storage, sharing, the Assistant and remote access). It works alongside our Terms of Service and End User License Agreement.

• Your work starts on your device. Projects, recordings and settings are stored locally. They reach our servers only when you use a cloud feature: saving to the cloud, syncing, sharing a link or a file, or asking the hosted Assistant.
• We do not sell or share your personal information, show ads, or track you across other apps and websites.
• We don't use your work to train AI models without your permission.
• You can delete your account from the app or the website at any time.

Viralinx LLC, 30 N Gould St. #47078, Sheridan, WY 82801, USA, is the controller of the personal information described here. Contact: [email protected]. We haven't appointed a data protection officer; write to us at the same address.

Our representatives. Because we're based outside the EU and the UK, we've appointed representatives you can contact about anything in this policy. In the European Union: Prighter Privacy IRL Ltd, 9 Clare Street, Dublin 2, D02 HH30, Ireland. In the United Kingdom: Prighter Ltd, 20 Mortlake High Street, London SW14 8JN, United Kingdom. You can reach them at https://app.prighter.com/portal/16167690663.

When you buy RISR on our website or in the Mac and Windows apps, Paddle (Paddle.com Market Limited, or Paddle.com Inc. for buyers in the United States) is the merchant of record and sells it to you. Paddle is a separate controller of the payment and tax information it collects; see Paddle's privacy notice. When you buy in the App Store or Google Play, Apple or Google processes your payment under their own privacy policies.

Today, we do not collect the following. If that changes, we'll update this policy first and, where the law requires, ask you.

• product-usage analytics: how, when or how often you use the apps (we keep only the counts some features need to run, such as Assistant usage (3.5), connected assistants (3.6) and when you last opened each stored file (3.3));
• advertising identifiers, or data for advertising or profiling;
• your browsing behaviour on other sites;
• your contacts, location, or health data (RISR does not ask for location or health access on any platform);
• the contents of your projects, unless you save them to the cloud, share them, or send them to the Assistant (section 3.4–3.6);
• the audio, MIDI, video and sensor signals RISR processes while you play. These stay on your device, or travel only to devices and software you connect yourself.

3.1 Your account

3.2 Subscriptions and purchases

We never receive your full card details.

3.3 Things you save to the cloud

When you save a project to the cloud, upload audio or media, create a template, or sync preferences, we store:

Legal basis: contract.

3.4 Sharing

• Public links. Public links are for people 18 and over. To check you're 18 or over, we ask your month and year of birth once and keep only the result (yes or no) and when, never the date. Legal basis: legitimate interest (keeping public sharing for adults). When you share a file or template by link, anyone with the link can open it until you stop sharing, delete the file, or delete your account; the link then stops working within a minute. Anyone who already opened or downloaded it may keep what they got. Links don't expire on their own.
• Sharing with a person. When you share with someone by email, we store their email address and account so they can open it. They see your display name with what you shared, in the invitation email and in their list of things shared with them. Both of you can see the share. Legal basis: contract.
• Copyright notices and reports. If you send us a copyright notice, a counter-notice or a report about shared content, we keep what you sent (including your name and contact details), the content and account it concerns, and what we did about it. We use this to act on it, to tell the person who shared the content why we removed it, and to apply our repeat-infringer policy. For a copyright notice, we tell that person your name and the work you claim. A counter-notice is sent, as you wrote it, to the person who sent the copyright notice, as US copyright law requires. Legal basis: legal obligation; legitimate interest (keeping RISR lawful and safe). Kept while the account concerned exists and for 3 years after. If we remove something because it's illegal to have, we also find and remove identical copies of it in other accounts, by comparing a fingerprint of the file. We keep a record of any warning, pause or suspension on your account, with our reasons, under the same retention. If you dispute one of our decisions, we keep your message, our review and the outcome, under the same retention. If you report something without signing in, we keep a scrambled form of your IP address, never the address itself, for 2 days, to limit how many reports can come from one place. Legal basis: legitimate interest (preventing misuse of reporting).

3.5 The Assistant

RISR's Assistant can work in two ways:

• RISR's hosted Assistant (uses RISR credits). What you send (your messages, images you attach, screenshots and project details the Assistant reads to help you) goes to our servers and from there to our AI provider OpenRouter, which passes it to the AI model that answers (models and providers change over time). Today we don't store the content of your conversations on our servers; we keep usage records such as the number of tokens and the cost. Our AI providers process the content to produce the answer, under their own terms and retention. We don't use your conversations or projects to train AI models without your permission. Conversations are kept on your device with your project. Legal basis: contract (you ask the Assistant to help you).
• Your own provider. If you connect your own AI service (for example a local model, or your own account with an AI company), the app sends your messages directly from your device to that service, using your key. We store the connection's name, address and model in your account so it appears on your other devices; we never receive or store your key. That service's own privacy policy applies. Legal basis: contract.

Dictation in the Assistant chat uses your device's speech recognition. On iPhone, iPad and Mac it runs on the device. On Android and Windows, your operating system may send the audio to Google or Microsoft, depending on your device settings.

3.6 Remote access and connecting your AI assistant

RISR can let AI tools and other software control the app through the Model Context Protocol (MCP). It is off for other devices by default: only the device itself can connect, with an access token.

Control from other apps (RISR Pro). If you turn it on, apps and AI tools on this device or your network that have one of your access tokens can do anything you can do in RISR on that device: open, change and delete projects and files, change settings, share and export, see what's on the screen (including your camera), and read your device's sensors, including location and health readings from connected devices. The screen you turn it on from says this, and you confirm separately that a connected app may see your camera and sensor readings, including health data; until you do, those stay hidden from connected apps. What those apps read goes to whoever runs them, under their terms; it doesn't pass through us. We keep a record of when you turned this on or off, with the version of the words you agreed to and the device, until you delete your account. Legal basis: contract; your explicit consent for camera and sensor readings, which you can withdraw by turning this off. You can revoke a token, or turn this off, at any time in Settings.

Connecting your own AI assistant (RISR Pro). You can connect an AI assistant you use, one that supports connectors, to RISR.

• It's off until you turn it on in the app, and you allow it by signing in with your RISR account.
• Your assistant can then read and change the project open in RISR: its parts, settings, wiring, names and widget code, and its author and description. It can also read the project's scripts and the MIDI notes you've recorded in it, and measurements of what's playing (levels, pitch and a frequency summary), but not the sound itself. It can see pictures of your faceplates as live mode draws them, with any camera or video left blank. It can read your device's motion sensors (how it's tilted and moved) at the moment it asks, but not your location, camera or health readings. It can also open live mode on your screen so it can look at your faceplates. It can't reach your other projects, your cloud files, your recordings' audio or your account details. On phones and tablets, this works only while RISR is open.
• Requests and replies travel through our relay (mcp.risr.app, on Cloudflare). We don't store or log their content.
• We keep: which assistants you've connected and when each was last used, so you can see and remove them, until you remove an assistant or delete your account; a record of when you turned connecting on or off, with the version of the words you agreed to and the device, to show your choice, until you delete your account; and counts of requests and data, to keep the service secure and fair, for up to 2 days. Legal basis: contract (you asked for it); legitimate interest (security); legal obligation (the record of your choice).
• If you use RISR on more than one device, the relay remembers which of your devices each connected assistant works on: the kind of device (such as "iPad") and a coded version of its ID (not the ID itself). We keep this until you remove that assistant, delete your account, or that device hasn't connected for 30 days. It doesn't include your projects or what the assistant does.
• What your assistant receives goes to the company that runs it, under your account with them. Their terms and privacy policy apply, including what they keep and whether they use it to train their models. We don't control that.
• You can remove an assistant, or turn connecting off, at any time in the app or on risr.app/account. Deleting your RISR account disconnects every assistant.

If you use RISR's relay for other tools, their requests and replies pass through it the same way. The tools you connect receive whatever project and app data you let them read; their own terms apply.

3.7 Email

• Service email about your account and subscription (verification, password reset, receipts, renewal and billing, new or removed devices, account deletion). Sent under our contract with you, not marketing.
• Marketing email (product news and tips) only if you opt in, at sign-up, on the website newsletter form, or later in the app under Account → Privacy or on risr.app/account. Every marketing email has a one-click unsubscribe. We keep a suppression list so we don't email you again after you unsubscribe. Legal basis: your consent, which you can withdraw at any time.
• Newsletter sign-up without an account: your email, the consent text you agreed to and when. You can unsubscribe from any email, or write to us to have it deleted. Legal basis: your consent.
• Support email: when you write to us, we keep your message, your contact details and, if you have an account, a snapshot of your subscription and devices so we can help. We keep it as long as we need it to help you and keep a record of our support (currently up to 2 years). Legal basis: contract if you're a customer; otherwise legitimate interest (answering you and keeping a record of our support).
• Improving our support. To help us draft and improve our replies, our own AI on our servers turns your support message into a short anonymous summary, without your name, contact details, order details or your own words. Only that summary is shared with an outside AI service. You can ask us not to do this for your messages: email [email protected]. Legal basis: legitimate interest (better support); you can object, as section 8 explains.

We send all email through Twilio SendGrid, which also tells us whether an email was delivered or bounced.

3.8 Crash and error reports

When something goes wrong, the app can send a report to our error-monitoring provider Sentry (Functional Software, Inc., USA): the error and stack trace, which part of the app was active, app version, device and operating-system or browser details, your IP address, and a short trail of recent app events. We use reports only to find and fix problems. Legal basis: your consent, which you can withdraw at any time in Account → Privacy. Sentry keeps reports for a limited period under our retention settings.

3.9 Feedback

If you rate or comment on a building block in the app, we store your rating, words and note with your account so our team can improve RISR. Kept until you delete your account. Legal basis: legitimate interest (improving RISR).

3.10 Technical data and logs

Like any online service, our servers and providers see your IP address and basic device and browser information when your app or browser connects. We use this to deliver the service and keep it secure:

• Hosting: our website runs on Vercel and Cloudflare; our servers on Google Cloud (Firebase). They keep standard request logs for a limited period.
• Server logs: our Cloud Functions logs may include your account ID or email when something about your account is processed; kept for a limited period (currently about 30 days).
• Security checks: we may use Firebase App Check to check that requests come from a genuine app or browser. Where it's turned on, it uses Apple's App Attest on iPhone, iPad and Mac, and Google reCAPTCHA Enterprise on the website, Windows and Android; with reCAPTCHA, Google receives browser and device signals for this.
• Sign in with Apple: when you open the sign-in page on risr.app, it loads Apple's sign-in script so the button works on iPhone and iPad. Apple receives your IP address and basic browser information, even if you sign in another way.
• Downloads the app makes: app updates and interface updates (from risr.app and cdn.risr.app), the in-app news feed, the app's fonts from Google Fonts, and, for some camera features, machine-learning models from public content networks. These servers see your IP address; we send no account information with them.
• Google Play billing in the Android app: when you buy through Google Play, Google's billing component sends Google technical usage information: device and app details (such as the phone model, Android version, language, country, time zone and mobile network) and how the purchase screen performed (such as response codes and timings). Google uses this for diagnostics and usage statistics.
• Mac and Windows updates include only the platform, release channel and app version; not your account.

Where we process this technical data ourselves or through our providers, and an item above doesn't say otherwise, our legal basis is legitimate interest (delivering RISR and keeping it secure).

Cookies and browser storage

The risr.app website does not use analytics or advertising cookies. It keeps you signed in using your browser's storage. On the checkout page, our merchant of record Paddle uses its own cookies and storage to run the payment; see Paddle's notice. Your theme choice is remembered in your browser.

RISR asks for these permissions only when you use a feature that needs them. Everything here is processed on your device unless the table says otherwise.

Local network details. To find your other devices, RISR announces itself on your local network with the device's name (on Windows, the computer's name), a device ID, and a security key fingerprint. Other people using RISR on the same network can see that name in their list of nearby devices. Devices signed in to the same RISR account can connect to each other without a pairing prompt. Data you route between devices travels on your network, not through us.

Remote control (RISR Link). If you switch it on for one of your devices, RISR Link carries out the key presses, pointer moves and other actions that device sends, on that computer only. It doesn't record or send what you type. To switch per-app setups, it checks which app is in front; that stays on the computer, and only a setup number goes back to your device.

Android backup. Android may include your RISR projects and settings in your Google device backup, under Google's terms. Your sign-in keys are excluded.

We share personal information only with the providers that run RISR for us (processors), under contracts that limit their use to providing their service, and with the stores and Paddle as described above. Our current providers are listed below; we update this list when they change.

We may also disclose information if the law requires it, to protect people's safety or our rights, or as part of a merger or sale of the business (you would be told).

People at RISR. Staff who need it can see account, subscription, device and support information to help you and keep RISR running. Access is limited by role and protected by two-factor sign-in.

We are based in the United States, and our providers process data in the United States and other countries. Where the law of your country requires it (for example the EEA, the UK and Switzerland), we rely on the EU–US Data Privacy Framework where the provider is certified, or on Standard Contractual Clauses. You can ask us for a copy of these safeguards at [email protected].

We keep personal information only as long as we need it for the purposes above, or as the law requires.

Deleting your account. You can delete your account in the app's account settings or on risr.app/account. Your account stays recoverable for a short period (currently 30 days); sign in and choose Cancel deletion during that time. After that we permanently delete your account, your cloud files and templates, your shared links and shares, your devices, your consent and preference records, your email and newsletter records (records kept under an email address count as yours once you've verified that address on your account), and your Assistant and credit records. A subscription bought on the website or in the Mac or Windows app is cancelled; App Store and Google Play subscriptions must be cancelled in the store. Data stored on your devices stays there until you delete the app.

Backups. Copies may remain in encrypted backups for up to 90 days, used only for disaster recovery.

What we keep after deletion. Transaction, billing, tax and invoice records are kept as tax and accounting law requires, in a form that no longer identifies your account where possible. We also keep security and administrative audit logs with your personal details removed (for 3 years, or as long as the billing record they belong to), and a one-way code that shows an account was deleted. If we hold an Apple security token for your account (we get one when you sign in with Apple in the iPhone, iPad or Mac app), we keep it, with no name or email, for up to 7 days after deletion, only to ask Apple to end the Sign in with Apple link; then we delete it. If we don't hold one, or Apple doesn't confirm, you can end the link yourself in your Apple ID settings, under Sign in with Apple. Paddle, Apple and Google keep their own records of your purchases. If the law requires us to keep something, for example evidence we've reported to the authorities, we keep it for as long as that law requires, even after you delete your account.

• Choices in the app: marketing email, crash reports and the hosted Assistant (Account → Privacy in the app; marketing email also on risr.app/account); stop sharing any link; delete files; disconnect devices; turn remote access off; delete your account.
• Your rights: depending on where you live (including the EEA, UK, Switzerland and California), you may have the right to access, correct, delete, or receive a copy of your personal information, to restrict or object to processing, and to withdraw consent at any time. Email [email protected]; we respond within the time the law requires and may need to verify it's you. You can download your cloud files from the app; for a full copy of your account data, email us.
• Your right to object: where we rely on legitimate interests (shown in each section above), you can object at any time, on grounds relating to your situation. We'll then stop, unless we have compelling legitimate grounds, or we need it to establish, exercise or defend legal claims. You can object to marketing at any time, without giving a reason.
• Automated decisions: We don't make decisions about you based solely on automated processing that have legal or similarly significant effects for you. Some protections run automatically: if three or more credit packs are refunded within 12 months, we may stop selling credit packs to the account (Terms, section 4); and a reported item may be hidden until a person reviews it. You can ask a person to look again at any of these: write to [email protected].
• What you have to give us: To create an account we need an email address and your agreement to our Terms; without them we can't give you an account or our online features. To buy, the store or Paddle needs your payment details. Everything else is up to you: if you don't give it, only the feature that needs it won't work.
• California: we do not sell or share personal information (as those words are defined in the CCPA) and do not use sensitive personal information to infer characteristics.
• Complaints: if you are in the EEA or UK, you can complain to your data-protection authority; in the UK, that's the Information Commissioner's Office (ico.org.uk).

We use reasonable security measures, such as encrypted connections to our services, encryption at rest by our providers, and restricted staff access. No system is perfectly secure; if a security incident affects your data, we will tell you as the law requires.

RISR is not directed to children under 13 (or the higher age the law sets where you live), and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact us and we will delete it.

We'll update this policy when RISR changes. For material changes we'll give you notice (for example by email or in the app) and, where the law requires, ask for your consent. The date at the top shows the latest version.

Viralinx LLC · 30 N Gould St. #47078, Sheridan, WY 82801, USA · [email protected]