RIOSFROM THE WORK OUTWARDPrivacy notice · Updated September 23, 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.
One-time location lookup
If a visitor chooses “Use my location” in the directory, the browser sends precise coordinates once to OpenStreetMap to return a city and state. RIOS receives the resulting place search, not the coordinates, and does not store the coordinates.
Optional staff route maps
Where mapping is enabled, opening the route map sends stop addresses to Mapbox to locate them and coordinates to estimate driving routes. Names, dog names and session notes stay in RIOS. Mapbox receives normal network and device information and its map telemetry. Results remain in the open map only. The location button requests your device position once; RIOS does not store or share a live staff location.
Public-site measurement
Daily aggregate counts for a small allowlist of professional matcher, demo and signup actions. This measurement stores no visitor or session ID, IP address, user agent, contact detail, free text or analytics cookie.
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
With the recipient's consent, RIOS may send service, inquiry follow-up and appointment messages requested by an organization or user. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is not a condition of purchase.
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.
Mobile information
Mobile information is not sold, rented or shared with third parties or affiliates for their marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties. RIOS may provide the minimum information needed to messaging processors acting only on RIOS's instructions to deliver the requested service, or disclose it when required for security, fraud prevention or law. Opt-out requests are honored for the applicable messaging program.
RIOS contact
Privacy and messaging questions may be sent to info@riosos.com.
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.
Account holders can review the account and data deletion instructions to request full account deletion or deletion of selected personal data.
Children
The public RIOS site and the RIOS Canine Professionals OS business product are not directed to children. Do not submit a child's information unless an authorized adult and the applicable business workflow have established a lawful, necessary reason and the required consent.