prorso
Legal

Privacy Policy

This policy explains what data prorso collects, why, how it is handled, and the choices and rights you have. prorso is built around deliberate, recorded decisions — the same care applies to your data.

Version 2.4 Last updated 3 November 2026 6 min read
At a glance

Never sold

Your data and decision logs are never sold or rented to anyone.

Private by default

Logs stay private to you and invitees unless you choose to publish.

Yours to export

You can access, export, or request deletion of your data at any time.

Collected sparingly

Only what is needed to run the service — no tracking for advertising.

Our approach

prorso collects as little personal data as it can while still operating reliably. It does not use your data for advertising, does not sell or rent it, and does not track you across other websites.

This policy describes the data involved when you use prorso, why it is processed, and the rights you have over it. It forms part of the Terms of Use.

In plain terms

The short version: minimal data, no selling, no ad tracking — and clear rights for you over everything that is collected.

Who is responsible

prorso is a personal project operated by Ivan Jureta, who acts as the data controller for personal data processed through the service. prorso is not affiliated with or operated on behalf of any organization.

You can reach the controller at ivan@ivanjureta.com for any question or request relating to your data.

What data is collected

Three kinds of data are involved when you use prorso:

Account data
your name and email address from the sign-in method you choose (such as Google), used to create and secure your account.
Content you create
the decision logs, nodes, attachments, comments, and history you add to the service.
Technical and usage data
limited information such as log-in events, basic device and browser details, and error logs needed to keep the service secure and working.
Landing-page input
if you describe a decision on the landing page without signing in, that sentence is held for up to two hours so you can work through the guided steps, and is then deleted. It is not linked to an account, because at that point there is no account.

How data is used

Data is used to provide and secure the service: to create and authenticate your account, to store and display your decision logs, to preserve their immutable history, to operate AI-assisted features when you use them, and to diagnose and fix problems.

Data is not used for advertising or profiling, and is not combined with data from third parties to build a profile of you.

AI-assisted processing

When you use AI-assisted features, the relevant content from your log may be sent to a third-party AI provider (OpenAI) solely to generate the assessment, risks, or options you requested, and then returned to you. This processing happens only when you trigger it.

This also applies before you have an account. If you describe a decision on the landing page, that sentence is sent to OpenAI, which drafts options, reasons for and against each, and comparison criteria for you to edit. It is sent when you submit the sentence and never as you type, it is not linked to an identity, and nothing is saved to an account unless you sign in.

Which OpenAI account a request goes through decides whether its content may be used to train models. Ours is used for the guided setup on the landing page, and for the guide inside a log when the log has no key of its own — neither its organisation’s nor, on a Personal log, the owner’s own; on ours, under OpenAI’s standard API terms, content is not used to train their models. Your organisation’s own account is used for the AI features inside its logs when it has connected one, and your own key, if you add one, for your Personal logs; there, that account’s terms and settings decide, including how long OpenAI keeps a request. On ours, OpenAI keeps it for up to 30 days for abuse monitoring. AI features are never applied to your private logs unless you invoke them.

In plain terms

AI features only run when you ask. On our OpenAI account, what you send is not used to train models; on your organisation’s or your own, that account’s settings decide. The guided setup on the landing page is one of those features — it runs when you press Start.

Public logs and visibility

Logs are private to you and the people you invite. If you choose to publish a log or template, the content you publish — including any names or details inside it — becomes readable by anyone, including signed-out visitors.

Only publish content you are comfortable making public, and avoid including personal data about others without a basis to do so.

Organisations and managed accounts

If you belong to an organisation in prorso, its admins can see that you are a member, your role, and the actions recorded in its action log, and they can remove you from it.

An organisation can verify that it owns an email domain, such as northwind.com. If your confirmed email address is on a domain an organisation has verified, that organisation manages your prorso account:

Sign-in rules
its rules for how long you stay signed in, and whether you must use two-step verification, apply to your whole account, including in other organisations you belong to.
Signing you out
its admins can sign you out of every device. Each sign-out is recorded with the admin’s reason.

A managing organisation cannot read the logs of other organisations you belong to, remove you from them, or change how you sign in. Your account settings say whether your account is managed, and by which organisation. The organisation that owns your work address also controls that address and its mailbox outside prorso. If you want an account no company manages, sign up with a personal email address.

In plain terms

If you sign up with your work email and your employer has verified its domain, your employer’s organisation sets sign-in rules for your account and can sign you out. Use a personal address if you don’t want that.

Sharing with third parties

Data is shared only with the service providers needed to run prorso, under agreements that limit them to that purpose:

Identity providers
to authenticate your sign-in (for example, Google).
Hosting and infrastructure
to store and serve your data securely.
AI provider (OpenAI)
to process AI-assisted requests you initiate, including the guided setup on the landing page. Content sent through our account is not used to train their models; content sent through your organisation’s or your own account is governed by that account’s settings.

Cookies and local storage

prorso uses only the cookies and browser storage needed to keep you signed in and to remember basic preferences. It does not use advertising or cross-site tracking cookies.

Data retention

Your account and content are kept for as long as your account is active. Because prorso preserves an immutable history of each log, earlier states are retained as part of that record until the log or account is deleted.

A decision you describe on the landing page without signing in is held for at most two hours from your last edit and is then deleted automatically. If you sign in within that window it becomes a log in your account and is kept like any other content. If you do not, nothing remains.

When you request that we delete your account, your personal data and logs are removed within a reasonable period and you are notified when this is executed, except where limited information must be kept to meet legal obligations. If you request the deletion of your data and we complete it, this cannot be undone.

Security

Reasonable technical and organizational measures are used to protect your data, including encryption in transit and access controls. No service can guarantee absolute security, but access to your content is limited to what is needed to operate prorso.

Your rights

Subject to applicable law, you have the right to:

Access
obtain a copy of the personal data held about you.
Rectify
correct data that is inaccurate or incomplete.
Erase
request deletion of your account and data.
Port
export your data in a usable format.
Object or restrict
object to certain processing or ask that it be limited, and withdraw consent where it was the basis.
In plain terms

Email ivan@ivanjureta.com to exercise any of these. You can also lodge a complaint with your local data-protection authority.

Landing-page drafts are not linked to an identity, so there is no way to look one up, correct it, or export it on request. It deletes itself within two hours, and that is the only handling it gets.

International transfers

Some service providers may process data outside your country or the European Economic Area. Where that happens, appropriate safeguards — such as standard contractual clauses — are relied upon to protect your data.

Children

prorso is not directed at children and is not intended for anyone under 16. Personal data of children is not knowingly collected; if you believe a child has provided data, please get in touch so it can be removed.

Changes to this policy

This policy may be updated from time to time. When changes are material, the updated version and its effective date will be posted here, and reasonable notice will be given where practical.

Contact

For any question or request about this policy or your data, contact ivan@ivanjureta.com. Because prorso is a personal project, correspondence is handled directly by its author.

Questions about your data?

prorso is a personal project, not affiliated with any organization. To exercise a privacy right or ask a question, reach out directly.

ivan@ivanjureta.com