This Privacy Policy explains how Rischio S.A.S. processes the personal data of the people who use rischio.io, the studio at studio.rischio.io, the free calculators, the Academy and our other services (the “Service”). It’s also our policy for the processing of personal data under Colombia’s Law 1581 of 2012 and its regulations (Decree 1377 of 2013, compiled in Decree 1074 of 2015). Where they apply, it also meets the EU and UK General Data Protection Regulations (GDPR) and other privacy laws.
1. Who is responsible for your data
The data controller (“responsable del tratamiento”) is:
- Rischio S.A.S., NIT 901787239-9, domiciled in Bogotá, Colombia;
- email for any privacy matter: hello@rischio.io, handled by Rischio’s data protection team;
- physical address for postal notices: available on written request to that email.
2. What data we collect
When you create and use an account:
- Account data: your name, your email, your password (stored only as a one-way hash), your preferences (the units and the design code your new models start in) and, if you choose to give them, your company, role, country, how you heard about Rischio and the tool you came for.
- Sign-in with Google or Microsoft: your account’s identifier, name and email address. We never receive your Google or Microsoft password, and we keep no access to your Google or Microsoft account: signing in gives us a short-lived token for those three details, which we don’t store.
- Acceptance: the version of these documents you accepted, and when.
- Plan and billing: your plan, trial and Education dates, your subscription status, and the payment records Paddle sends us: a customer identifier, invoices, and the card’s brand, last four digits and expiry date. We never receive or store full card numbers.
- Your content: your models (the engineering data you enter and their results), your report settings, and your letterhead (company name, details and logo).
- AI: the descriptions you write to create a model with AI or to find a template that fits your project, what the AI produced (its steps, assumptions and reply), and your rating of it.
- Feedback: the messages you send us, with the page you were on, your browser, the size of your screen and any recent errors, so we can reproduce the problem. If you send it from a model and choose to attach the model, we also receive it as it is at that moment: its inputs, the status of its last result and its last error. It goes to our private issue tracker without your name or email, and we remove it if you ask. A request for help reaches us by email with your name and email, so we can answer; the model you attach to it stays in the studio, where we look at it, and doesn’t go to the issue tracker. If a model of yours can’t be brought up to date when you open it, the studio tells our issue tracker by itself, with your user ID, your plan, the model’s ID and tool, and the names of the fields involved, never their values.
- Connected agents: the name of the AI agent app you connect, when you connected it, and its access tokens (stored as hashes).
- Sessions and security: for each sign-in, the IP address and the browser it came from.
- Server logs: for each request to the studio, including the ones rischio.io’s pages and calculators make, the IP address, the address requested, the time and the browser, for security and to fix problems.
- Suspension: if we suspend your account for breaking the Terms, when and why.
- Product emails, only if you ask for them: that you agreed to receive them and when, and which ones we’ve sent you. To choose them we use what your account already shows (whether you’ve calculated a model or connected an agent, your plan, and the tool you came for). Never the content of your models.
- Last use: the day you last used your account (signing in, opening the studio, or a connected AI agent working in it), recorded at most once a day, to apply the rule on inactive free accounts (section 6).
- Usage analytics in the studio: visits and actions, such as “created a model”, “calculated” or “opened the report”, and what you search for in the template gallery. They are recorded with your account (once you’re signed in), a shortened IP address (we never keep the full address for this), your browser and its version, operating system and device type, the page you arrived at, the referring page and the campaign parameters of the link that brought you. No cookies are used for this, and you aren’t tracked across other websites.
- Visits, in aggregate: Cloudflare Web Analytics also measures the studio’s visits in aggregate, without cookies and without identifying you, as it does on rischio.io.
- How you use the studio, with PostHog: the pages you open and what you do on them, and what a connected AI agent does in the studio, never the content of your models, with your user ID, your country and your browser, to see where people get stuck. No cookies are used for this, and PostHog uses your IP address only to tell your country, without keeping it. Only if you accept it, a recording of your session in the studio, with what you type hidden. Now and then, a short question inside the studio, and your answer.
When you visit rischio.io or use the free calculators without an account:
- Cloudflare Web Analytics measures visits in aggregate, without cookies and without identifying you.
- The calculators send only the model’s numbers to our servers, without any account or cookie. Your IP address is used to limit abuse: we keep it up to a day for that, and in the server logs until they rotate (section 6).
- If a page fails, the technical data of the error reaches Sentry through our server, without identifying you.
What we don’t collect:
- We don’t ask for sensitive data, and you shouldn’t include it in your models, descriptions or messages.
- We don’t track your location. When you sign up, the country Cloudflare infers from your IP address sets the units your account starts in, and we don’t keep it.
- The names, license numbers and signatures you add to a report stay in your own browser and never reach our servers.
3. What we use it for, and on what basis
| Purpose | Data | Legal basis |
|---|---|---|
| Create and run your account, provide the studio, calculate your models, produce your reports | account, content, AI, connected agents | performance of the contract; your authorization |
| Billing, subscriptions, invoices and taxes, through Paddle | account, plan and billing | performance of the contract; legal obligations |
| Security: preventing fraud, abuse, spam and attacks; enforcing the Terms | sessions, IP addresses, usage | our legitimate interest in protecting the Service and its users; legal obligations |
| Giving each email one trial or one Education, as the Terms say | a fingerprint of the email | our legitimate interest in keeping the free plans from being abused |
| Service emails: verification codes, password resets, trial and plan notices, replies to your feedback | account | performance of the contract |
| Product emails: tips to get started and news about Rischio | name, email, plan, and whether you’ve calculated a model or connected an agent | your consent, which you give only in the studio, with its own box at sign-up, in the welcome or in Settings, and can withdraw at any time from Settings or from the link in each email |
| Support and fixing problems | feedback, account, content | performance of the contract; legitimate interest |
| Understanding how the Service is used and improving it | usage analytics, ours and PostHog’s, reviewed in aggregate, and your answers to the studio’s short questions | our legitimate interest |
| Recording your session in the studio, to see where it gets in your way | the recording | your consent, which you give or refuse in the studio and can withdraw there |
| Complying with the law and answering authorities | what the law requires | legal obligations |
We don’t sell your personal data, we don’t share it for advertising, and we don’t send marketing emails without your consent. We don’t make decisions about you based solely on automated processing that have legal or similarly significant effects, apart from closing an inactive free account under the rule in section 6, which we warn you about by email 30 days before. The academic email check that grants Education only compares your email’s domain with a public list of universities: if it’s wrong, write to us.
Under Colombian law, you give us your prior, express and informed authorization to process your data as this policy describes by ticking the acceptance box when you sign up, or by continuing with Google or Microsoft after the notice that says so. The studio then asks you to tick the box before you go on.
4. Who processes it with us
We share personal data only with the providers that help us run the Service. They act as data processors (“encargados”) under contract, except Paddle, Google and Microsoft, which act as independent controllers for their part. Each receives only what it needs for its task:
| Provider | What for | Data |
|---|---|---|
| DigitalOcean | hosting of the studio, its database and the engine, on our server in New York (United States) | everything in the studio |
| Cloudflare | network and the connection to our server, which every request to the studio goes through; security, bot protection (Turnstile); storage of letterhead logos and of the encrypted backups of the studio’s database (R2); routing the emails sent to hello@rischio.io; analytics of the website and the studio, in aggregate | IP addresses, technical data, the studio’s traffic in transit, logos, the studio’s data in encrypted backups, the emails you send us, in transit |
| Paddle | payments as Merchant of Record: checkout, taxes, invoices, refunds | name, email, billing and payment data |
| Plunk | sending the service emails and, if you agreed, the product emails | name, email, the email’s content |
| Sentry | error monitoring, in the studio and on the website, through our server | technical data of errors, your user ID in the studio |
| PostHog | analytics of how the studio is used and of what connected agents do in it; its short questions inside the studio; and, if you accept them, the recordings of your sessions; in the United States | your user ID, what you do in the studio, your country and browser, your answers, the recordings you accept |
| Anthropic | the AI model that creates models from your descriptions and finds the templates closest to them; and the AI assistant (Claude) our team works with to maintain and develop the Service, which reads the feedback you send and the models attached to it, and the studio’s data a maintenance task needs | your descriptions and the model data needed; for our team’s work, your feedback and the studio’s data that work needs |
| Google, Microsoft | signing in, only if you choose them | what section 2 lists |
| Google (Gmail) | our mailbox, where the emails you send to hello@rischio.io and the studio’s requests for help arrive | what you write to us, your name and email |
| GitHub | tracking your feedback in a private repository | your message, the model you attached (when you choose to: its inputs, its last result’s status and error), the description you rated (when you rate the AI down), your plan, your user ID, the technical context; and, when a model of yours can’t be brought up to date, its ID, its tool and the names of the fields involved |
Some details about specific providers:
- Paddle acts as an independent controller for the payment data it collects at checkout, under its own privacy policy.
- Anthropic doesn’t use the data we send it to train its models, under its commercial terms, and keeps it only for a limited period.
- GitHub doesn’t receive your name or email, though your message reaches it as you wrote it, and so does any model you attach.
- Your AI agent: when you connect one, its provider (Anthropic, OpenAI or another) receives the model data you ask it to work with, under that provider’s own privacy policy.
When your models include other people’s personal data, we process it on your behalf, as your processor, under the Terms.
We may also disclose data to public authorities when the law requires it, to our professional advisers under a duty of confidentiality, and to a successor company in a merger or acquisition, which would be bound by this policy.
5. International transfers
Our providers process data in the United States and in other countries where they operate.
- Colombia’s Superintendence of Industry and Commerce (SIC) considers the United States to provide an adequate level of protection.
- For users in the European Economic Area and the United Kingdom, transfers rely on adequacy decisions (such as the EU–U.S. Data Privacy Framework, where the provider is certified) or on the Standard Contractual Clauses included in our providers’ data processing agreements.
By accepting this policy you authorize these transfers and transmissions.
6. How long we keep it
| Data | How long |
|---|---|
| Account, content, letterhead, feedback, connected agents | while the account exists; deleted within 30 days after it’s closed |
| Models you delete | 30 days in the studio’s trash, where you can restore them, then deleted |
| A fingerprint of your email, if your account got a trial or Education: a one-way code made from the address, which can’t be turned back into it | kept after the account is closed, so the same email doesn’t get them again |
| Descriptions and results of the AI | while the account exists; when it’s closed, they are deleted, and only an anonymous record of the usage and its cost remains |
| Usage analytics in the studio | 24 months, then deleted automatically, or earlier if the account is closed |
| Usage analytics in PostHog, and your answers to its questions | 1 year, then deleted by PostHog, or earlier if the account is closed |
| Recordings of your sessions, if you accept them | 30 days at most |
| Sessions (IP and browser) | until you sign out, sign in on another device, or the account is closed |
| Accounts that never verified their email, or that signed up with Google or Microsoft and never accepted these documents | deleted after 7 days |
| Inactive free accounts (no paid subscription, trial or Education) | closed and deleted after 24 months without use (no sign-in, no use of the studio and no connected agent working in it), after an email 30 days before; signing in keeps the account, and an account with a complaint in progress waits for its answer |
| Suspended accounts | 90 days to appeal, by writing to us: if we don’t lift the suspension in that time, the account is closed and its data deleted, as any closed account’s |
| Why you deleted your account, if you tell us (a reason from a list and your own words, kept as you wrote them), with the plan, the months the account existed and how many models it had | kept without your name, your email or anything that links it to the account |
| Feedback copied to our issue tracker (GitHub), with any model you attached | as part of our development history, without your name or email; we remove your message or the model on request |
| Emails you send to hello@rischio.io, and requests for help | in our mailbox, 24 months after the last message of the conversation; a request about your data under Law 1581, with our answer, 3 years after we answer it, to show how we did |
| Server logs | on our server, until they rotate out by size (30 MB for each part of the studio) |
| IP addresses counted to limit abuse | up to a day |
| Background tasks that failed for good, and payment notifications from Paddle that couldn’t be processed | 30 days, to look into them, then deleted |
| Error reports and records of the emails we sent | the retention periods of Sentry and Plunk |
| Encrypted backups of the studio’s database | the hourly ones 2 days, the daily ones 35 days, the monthly ones 400 days |
| Invoices and payment records | with Paddle, as long as tax and commercial law requires |
Backups are overwritten in their normal cycle, so deleted data disappears from them as they rotate.
7. Your rights
Under Colombian law (Law 1581 of 2012, article 8), you have the right to:
- know, update and correct your personal data;
- request proof of the authorization you gave us, except where the law doesn’t require it;
- be informed, on request, of how we have used your data;
- revoke your authorization and request that your data be deleted, where no legal or contractual duty requires us to keep it;
- access your data for free;
- file complaints with the Superintendence of Industry and Commerce (SIC), after completing the inquiry or complaint process with us.
If GDPR applies to you, you also have the rights to:
- access, rectify and erase your data;
- restrict or object to its processing;
- data portability;
- withdraw your consent at any time;
- lodge a complaint with your data protection authority.
Other laws: depending on where you live, such as some US states, you may have similar rights to access, correct and delete your data. We don’t sell or share your personal information as those laws define it.
How to exercise them:
- Write to hello@rischio.io from your account’s email, saying what you ask for. We may ask you to confirm your identity. A complaint (“reclamo”) must include your identification, a description of the facts behind it, an address to answer you at, and any documents you want to rely on.
- You can also change your profile yourself in the studio, under Settings, and delete your account there (Settings › Profile: we email you a link, and the account is deleted when you open it and confirm). On the plans that include them, you can download your models, one or all of them, and export your reports as PDF or Word in the studio. On any plan, you can ask us at hello@rischio.io for a free copy of your data, your models included, or to close your account.
- Response times:
- the terms run from the business day after we receive the request;
- inquiries (“consultas”) are answered within 10 business days, which can be extended once by up to 5 more, with notice;
- requests to correct, update or delete your data, and complaints that we failed a duty of the law (“reclamos”), are answered within 15 business days, which can be extended once by up to 8 more, with notice. Within 2 business days of receiving one, we mark your data as “complaint in progress”, with its reason, until it’s decided. If a complaint is incomplete, we’ll ask for what’s missing within 5 business days; if you don’t send it within two months, the complaint is considered withdrawn;
- for GDPR requests, we answer within one month.
- Exercising your rights is free.
8. Cookies and similar technologies
In the studio we use only what is strictly necessary:
- a cookie that keeps you signed in until you sign out;
- a cookie that carries the security token of the forms;
- local storage in your browser for your preferences (theme, the view of your models), for the state of the interface (a panel’s width, a notice you closed, the news you’ve seen) and for the report’s sign-off data, which never leaves your device.
We don’t use advertising or tracking cookies, and our analytics don’t use cookies.
On rischio.io we don’t set cookies. Your theme preference is saved in your browser’s local storage, and Cloudflare Web Analytics works without cookies. Each page asks the studio whether you’re signed in, to show Open the studio instead of Sign in: the studio reads its own sign-in cookie, rischio.io keeps nothing, and the request enters the studio’s server logs (section 2). The home page loads Paddle.js, from Paddle, only when you arrive from one of Paddle’s emails about a payment, as described below.
Third parties may set their own cookies:
- Cloudflare, for security and bot protection, on rischio.io and in the studio;
- Paddle: in its checkout, once you choose to subscribe on the studio’s billing page; on rischio.io’s home page, when you arrive from one of Paddle’s emails to update a payment that failed; and, for customers who pay through Paddle, on the studio’s pages, where it warns of a failed payment or a card about to expire.
Since we only use what is strictly necessary, we don’t show a cookie banner.
9. Security
We protect your data with reasonable technical and organizational measures:
- encrypted connections (HTTPS) everywhere;
- passwords and access tokens stored as one-way hashes;
- protection against bots and brute-force attacks, and rate limits;
- access to personal data restricted to the people who need it to run the Service.
No system is completely secure. If a breach affects your data, we’ll notify you and the authorities as the law requires.
10. Minors
Rischio is for people aged 18 or older. We don’t knowingly collect data from minors. If we learn that an account belongs to someone under 18, we close it and delete its data. If you believe a minor has given us data, write to us.
11. Changes to this policy
We may update this policy. We’ll tell you about significant changes by email or in the studio at least 15 days before they take effect, and for those the studio will ask you to accept the new version. The version in effect and its date are at the top of this page.
12. Validity
The first version of this policy took effect on October 14, 2026, and this one takes effect on the date at the top of this page. Our databases are kept for as long as Rischio provides the Service and the purposes described here last, within the periods of section 6.
13. Contact
For any question or request about your personal data: Rischio S.A.S. · NIT 901787239-9 · Bogotá, Colombia · hello@rischio.io. This policy is offered in English and in Spanish. If they differ, the Spanish version prevails.