Privacy notice · Updated September 16, 2026
Privacy should follow the relationship.
SeVIIen LLC operates RIOS. This notice explains how the RIOS website and operating systems handle information. A business using RIOS remains responsible for its own client relationship and instructions.
Information RIOS handles
Public inquiries
Name, email, organization, topic and the message submitted through a RIOS form.
Account and workspace data
Identity, sign-in, role, organization configuration, staff activity and security records needed to operate the service.
Business and client records
Information an organization and its authorized users enter about clients, dogs, services, schedules, agreements, invoices, communications and evidence.
Technical records
Request metadata, security events, device and browser information, service logs and audit history used to protect and operate RIOS.
Why information is used
- Provide, secure, troubleshoot and improve the requested RIOS service.
- Authenticate users, enforce organization boundaries and preserve an attributed audit history.
- Route inquiries, deliver requested messages and support onboarding.
- Process provider-hosted payments and reconcile transaction state without storing card or bank details in RIOS.
- Meet contractual, safety, fraud-prevention, accounting and legal obligations.
- Run optional AI-assisted features only within their stated human-review, data and provider boundaries.
Providers and disclosure
RIOS uses service providers for hosting and databases, transactional email, object storage, messaging, payment processing and approved model-assisted functions. Current integrations include Railway, Resend, Cloudflare R2, Twilio, Stripe and OpenAI where the corresponding feature is enabled. Providers receive only the information needed for their function and remain subject to their own terms and privacy practices.
RIOS does not sell personal information. One organization's private records do not become another organization's records, public content or shared training material automatically. A lawful request, emergency, fraud investigation, corporate transaction or explicit user-authorized sharing path may require a bounded disclosure.
Payments, messages and AI
Payments
Stripe hosts payment, identity, bank and payout controls. Connected businesses are merchants of record for their own customer transactions.
Email and text messages
RIOS sends transactional messages requested by an organization or user. Reply STOP to supported SMS messages to opt out; carrier rates may apply.
AI-assisted work
RIOS limits provider context to the task being performed, records applicable provenance and keeps high-impact decisions with an authorized human. Customer records are not made public or contributed across organizations by default.
Retention, choices and requests
RIOS retains information for the service relationship, security, audit, accounting, safety and legal needs. Some records must remain as immutable history or evidence even when an account closes. Derived indexes and provider copies are removed or expire according to the applicable workflow and provider agreement.
Depending on the relationship and applicable law, a person may request access, correction, export or deletion. Client and dog record requests should normally begin with the business that collected the record; platform-level requests may be sent directly to RIOS. Identity and authority are verified before release or deletion.
Children and student information
The public RIOS site is not directed to children. RIOS Teach is a development preview and is not authorized for real student data. A separately reviewed school or education release must establish its own agreement, privacy, retention, security and authorization controls before student information is accepted.