Privacy notice — KinetiRO

Not in force

What follows records what the notice has to contain and what this site actually collects. The binding wording must be drafted by counsel against the named entity. Accounts are open while this notice is being finished. Signing up asks for a name, an email address and a position. The sign-in service also records technical details of each request, such as the network (IP) address it comes from, the browser and device making it, and the time. Requests about that data go to contact@kinetiro.com, and the full statement of rights comes with the binding wording. To report a security problem or a suspected exposure of your data, write to security@kinetiro.com.

The responsible party

An aviso de privacidad names a responsable and a domicilio. The responsable is named here; the domicilio is not, and the gap is described below rather than glossed over.

Responsable: Eduardo Damian Saucedo Montemayor, persona física con actividad empresarial
RFC: SAME991214TD0
Contact for privacy requests: contact@kinetiro.com

The domicilio is missing, and that is a real gap

An aviso de privacidad is required to state both a responsable and a domicilio. The responsable is named above. The domicilio is not published, by the founder's instruction, so this notice does not yet meet that requirement.

That is a decision he has taken and is carrying, not something the build is waiting on — and it is written here rather than left to be noticed, because a privacy notice that quietly omits a required field is the wrong kind of quiet.

What the notice must contain

The formal content requirements under the Mexican federal data protection law:

The identity and address of the responsible party.
The personal data collected, by category.
The purposes of the processing, separated into those necessary for the relationship and those that are not.
Transfers to third parties, and to whom.
Where a transfer to a third party requires consent, how it is obtained and the clause by which the data subject may refuse it.
The means of exercising the rights of access, rectification, cancellation and objection, and the channel for doing so.
How changes to the notice will be communicated.

What this site actually collects

Correspondence received: This site has no contact form. Enquiries arrive as email to contact@kinetiro.com or sales@kinetiro.com. What is held is whatever the sender chose to include in the message and, where an incorrect result is being reported, frequently a project file describing a plant. That last case warrants explicit naming in the drafted notice rather than inclusion under "free text", because a project file may belong to the sender's client rather than to the sender.; Retention: correspondence relating to a closed account is kept for 30 days after closure. The mailboxes are Google Workspace aliases, so the drafted notice has to name that as the processor and say where the mail is held.
KinetiRO Sim accounts, which are now required to use the product at all: This is the substantive change since the previous draft. Previously an account was optional; now the account is the product's front door. The notice has to be clear about what is collected at sign-up, what the beta's complimentary licence record is, and how long an account and its licence history are kept after it lapses.
What is stored where: Projects are stored on KinetiRO's server, under the account that creates or opens them, with a copy in the user's own browser; private keys in the user's own browser; account and licence records on the server. The calculation runs in the browser; no flowsheet is sent to be solved. The design — the flowsheet, every block and its parameters, the equipment, the sizing, the layout and the project's name — is encrypted in the browser before it is stored, under a passphrase the account holder sets once and enters on each device; KinetiRO cannot read it unless the user shares it. The passphrase itself is never sent to KinetiRO: the key that encrypts a design is derived from it in the browser, and only the encrypted design is stored. KinetiRO cannot read a design without the passphrase — so, for a design that is not shared, its strength is what protects it. A forgotten passphrase loses every design, with no recovery by KinetiRO, because the same property that keeps the design unreadable makes it unrecoverable — so export anything that cannot be lost. KinetiRO can see the initial characterisation of the water and the characterisation of every outlet stream of the design — water, permeate, concentrate, sludge, and the air and biogas. It cannot read the design itself — the flowsheet, the equipment and the sizing. An account may choose, in Settings, to share its designs with KinetiRO; the choice is off unless the holder turns it on. It applies to every design of the account. A shared design can be opened by KinetiRO. Readable by KinetiRO, of every project: the initial characterisation of the water; every outlet stream's flow and quality as solved — the treated water, the permeate and concentrate of any membrane array, the sludge, and the air and biogas — once the project has been calculated; the account and its company; when the project was made and last saved; how many blocks and streams it has; and how many projects the account holds. Not readable by KinetiRO: the flowsheet, every block and its parameters, the equipment, the sizing, the layout and the project's name. This section changed together with the storage section of the product page and clause 6 of the licence.
Email: Ordinary correspondence to contact@kinetiro.com and sales@kinetiro.com, and how long it is kept. If the domain mailbox forwards through a third party, the notice has to say so.

No analytics, and therefore no consent banner

This can be said plainly, and should be. There are no analytics, no cookies set for measurement, and no third-party embeds. So there is no consent banner and there is nothing to opt out of.

Request logs at Supabase's gateway are kept for one day. Cloudflare, which serves the site, holds request data under its own privacy policy, which publishes no maximum period. The audit entries the sign-in service writes are deleted after 60 days. A session record is deleted when the account holder signs out, which clears every session for that account. How long a session that is never signed out of is kept has not been established.

The Spanish edition of this page

This notice must exist in Spanish from the day the site goes live, independently of the rest of the site's language plan. The data subjects are largely in Mexico, and the required content is a legal matter rather than a translation. It is the one page where that is not a preference.