Local-first on developer machines, hosted in France on OVHcloud for enterprises.
RYNO keeps your deep link requests, environments and secrets on your Mac, in a folder of your repository. When your company shares a catalog with Team or Business, the service stores it in France, on OVHcloud. Stripe handles payment, and Google or Microsoft confirm who signs in: they are subprocessors.
Two uses, two places for your data
Ryno keeps a strict line between what you do alone on your machine and what your company chooses to share through its service.
On your machine, with the desktop app alone
- Requests, collections and flows are files in the
.rynofolder of your repository, reviewed with the rest of your code. See Open a workspace. - Local secrets stay in
*.env.local.json, which Git ignores and which is never uploaded. - Run history stays on your Mac. No account is needed.
- Ryno asks whether a newer version exists, unless you turn Updates off. Anonymous usage data leaves only if you turn it on, to Mixpanel in its EU region, and never holds a URL, a name or a secret. See Set Ryno up.
In the company service, for a shared catalog
- The catalog your pipeline publishes: shared collections and shared environments, stored as dated versions and never edited.
- Each member's name and email address, as Google or Microsoft report them, and the company they belong to.
- Sign-in sessions, deleted once expired, and the governance log of what administrators did.
- Your local requests and
*.env.local.jsonnever reach the service.
What the service stores in France, on OVHcloud
The company service, its databases and their backups are hosted in France, on OVHcloud. The catalog, accounts and members, and the governance log live there. What changes between plans is whether your company shares a database or has its own.
| What | Team | Business |
|---|---|---|
| Database | The shared service database, in France. Every query is filtered by company. | A database of its own, on the same server in France. Another company's query cannot read it. |
| Backups | The hosting provider's daily backup, in France. | The same, plus a daily backup of its own database, kept 30 days and restored without touching other companies. |
| Governance log | Kept 365 days, readable over the last 90 days. | Kept 365 days, readable over the last 365 days, exported in CSV and JSON. |
| Publication history | 90 days | 365 days |
Subprocessors
Only the data of the company service stays in France. Payment and sign-in go through other companies, each outside that hosting, and they are listed here rather than left out.
| Subprocessor | What it does | What it processes | Where |
|---|---|---|---|
| OVHcloud | Hosts the service, its databases and their backups. | Everything the service stores. | France |
| Stripe | Takes payment by card, confirmed with 3-D Secure, or by SEPA Direct Debit, and handles invoicing. | What payment and invoicing require. | Outside the OVHcloud hosting |
| Confirms who signs in, and your company's domain, when your company works with Google accounts. | The sign-in, and the name and email address it reports. | Outside the OVHcloud hosting | |
| Microsoft | Confirms who signs in, and your company's domain, when your company works with Microsoft accounts. | The sign-in, and the name and email address it reports. | Outside the OVHcloud hosting |
Governance and purchasing
Two roles
Every person is an administrator or a member, and there is no third role. Only administrators manage members, remove a project or remove access. See Roles and governance.
Access removal that holds
Removing someone's access cuts every session they have, on every computer, and refuses their next sign-in. It stays removed until an administrator restores it. See Remove access.
A governance log
Removing a project, removing or restoring access, granting or withdrawing the administrator role and regenerating a project token are each written down: who, on what, and when. The log never holds a secret, a token or an email address.
Sign-in with a work account
People sign in with the Google or Microsoft account their company gave them, and there is no Ryno password. Single sign-on your company configures itself (SAML or OIDC) and automatic provisioning (SCIM) are not available. See Sign in with your work account.
Payment and invoices
Your company pays by card or SEPA Direct Debit, through Stripe. On Business, from 10 seats billed annually, it can pay by invoice. See Billing and invoices.
Questions from your security review
For any contractual question, or a question this page leaves open, write to bonjour@isee-u.fr. Say who is asking and what your review needs to know.
Frequently asked questions
Does the desktop app send my requests anywhere?
No. Your requests, environments, local secrets and run history stay on your Mac. The app asks whether a newer version exists, unless you turn Updates off, and sends anonymous usage data only if you turn it on. That data never holds a URL, a name or a secret.
Where is the company service hosted?
In France, on OVHcloud. The catalog your pipeline publishes, accounts and members, the governance log, the databases and their backups all live there.
Does everything stay in France?
No, and the page says so on purpose. The data of the company service stays in France, on OVHcloud. Stripe handles payment and invoicing, and Google or Microsoft confirm identity at sign-in. Each of them processes what its role requires, outside that hosting.
Does every company get its own database?
Not on every plan. Team uses the shared service database, where every query is filtered by company. Business gets a database of its own, on the same server in France, with its own daily backup kept 30 days.
Who answers contractual questions?
Sales. Write to bonjour@isee-u.fr with the questions your security review, your data protection officer or your purchasing team need answered, including how your company's data is processed.