Privacy Policy

1. The Short Version

We do not collect, transmit, or store your dataset content — not a single cell value, column name, or row count. Section 2 below describes, in full, every network contact the Software makes with servers we operate, and none of it includes the data you process with the Software. Separately, if you point the Software at a database or a cloud storage location you specify, it connects directly to that source to read your data — never through us, and never through any server we operate, as explained at the end of Section 2.

2. What We Collect — and What We Never Collect

The Software makes network contact with servers we operate only for the following purposes:

• Licence heartbeat — a check that your licence key is still valid, sent to our licence server every three minutes, whatever the result. Only the notice you actually see in the Software waits for a change — the check itself runs on this fixed schedule the whole time the Software is open, so that a revoked licence takes effect quickly rather than at your next launch.
• Automatic activation — whether you signed up inside the Software or on our website and then opened the activation link we sent you, the Software exchanges the single-use token in that link for your licence key. If the signup itself was started inside the Software, it also sends a one-time random value the Software generated when it started that signup — proof to us that the redemption is coming from the same copy of the Software that began it, so a link someone else sends you cannot silently activate on your computer. When the signup instead started on our website, no such value exists to send, and the Software asks you to confirm before activating rather than proceeding silently. The token is used once and then expires, and neither the token nor this one-time value reveals anything else about you.
• Machine activation — when the Software activates on a computer, it sends your licence ID together with four one-way, salted digests of that machine's hardware and operating-system identifiers (never the raw identifiers themselves). This happens as a routine part of every activation — so that a single seat cannot be shared across many machines — not only when a problem is suspected.
• Machine deactivation — when you free a seat so the licence can move to another computer, the Software tells the licence server which machine to release, and records the release in our licence ledger.
• Trial usage — during a free trial, the Software reads and updates a count of completed runs, so the single trial run cannot be repeated indefinitely.
• Billing links — when you choose to add a payment method or cancel, the Software asks our server for the correct link to open in your browser. No card details ever pass through the Software.
• Cancellation feedback — after cancelling, you're offered a short, optional, skippable panel asking why you're leaving. If you choose to answer, submitting it sends the reason you picked from a short list, together with anything else you optionally typed. This is optional and skippable, and nothing is sent if you skip it.
• Integrity notice — if the Software detects that its own installed files have been altered, it locks its licensed features locally and tells our server, so that the licence can be reviewed. It sends your licence ID, the same four digests as an activation, a short summary of the reason, and a count of how many files were affected — never a file name, a file path, or the contents of any file.
• Downloads — fetching the installer, an update, or the optional GPU acceleration package.
• Update check — a check for a newer version of the Software.
• Opt-in diagnostics — diagnostic and usage information that never includes anything from your files: a random install identifier; the product version; your operating system and Python interpreter version; which GPU acceleration backends your machine could support; how long each pipeline step took; an overall completion rate; a per-step acceleration-backend field that is currently always empty, reserved for future use; a count of errors encountered; which step failed, a bounded error code, and a general reason the run ended, each drawn from a fixed list rather than free text; and a crash-grouping signature — a one-way fingerprint of the failing code location, never the error message itself, a file path, or a local variable; the engine build the run used, which updates independently of the product version; the total physical memory of your machine, in whole gigabytes; and the peak memory the OreML process itself used during the run. Nothing in that list describes your data: not its size, not its shape, not the number of rows or columns, not a column name, and not a value. Sent as a single batch at the end of a run, only if you explicitly enable it in Settings, and never while a run is in progress. This is off by default.
• Usage events — when your licence is active, the Software tells our server which of a fixed list of actions you performed and when: opening the Software; starting, completing or stopping a pipeline; a step failing; answering a review prompt; opening a report, export or settings window; changing the diagnostics setting; requesting an update; and deactivating a machine. Each event carries your licence ID and the same machine digest as an activation. It never carries a file name, a value, a column name, a row count, or anything you typed. We use these events to operate the service, support you, and administer your licence; they are recorded against the account that holds the licence.

Because each of the contacts above is an ordinary network request, it necessarily carries your device's source IP address. We use the IP address only to secure your licence and detect abuse — for example, one licence appearing from many different locations at once — and it is never combined with, and never reveals, anything about the data you process.

Database and cloud sources you specify. If you configure the Software, from the Database or Cloud tabs, to read from a database or a cloud storage bucket you specify, the Software connects directly to that source — using the connection details and credentials you provide — to load your data. That traffic runs only between your computer and the source you chose; it is not one of the contacts listed above, it never passes through us or any server we operate, and we never see it, its credentials, or its contents.

We never collect, transmit, or store the content of any dataset you process with OreML — no cell values, no column names, no row counts, no file contents, and no file names. This is a structural property of how the Software is built, not a configurable setting.

3. The Persistent Identifier in Your Exported Files

Separately from the network contacts above — and never transmitted anywhere — the Software embeds a persistent, one-way identifier in the file metadata of every Parquet, Feather and Excel file you export (in Excel, as a document property, never as a cell). It is not written into CSV, JSON, or any other format without a file-metadata layer, which are left unmarked.

This identifier identifies your licence, not you as an individual; it cannot be reversed to recover your licence key or any personal data; it touches no cell, column, or row of your actual data; and it survives table-level rewrites of the file, so it persists into files you build from your export and forward to someone else — though not through a dataframe library, which discards file metadata when it writes a new file. We disclose it here because, even though it never travels over a network and is never received by us, it is information about your licence that rides along inside output files you control and may choose to share.

4. Legal Basis for Processing

Where the UK/EU GDPR applies, we rely on the following legal bases:

• Legitimate interests (GDPR Recitals 47, 49, and 50) for the licensing, activation and abuse-prevention contacts and usage events described above — necessary for fraud prevention, network and information security, and reporting unauthorized access to a competent authority.
• Consent for opt-in crash/usage telemetry, which you may withdraw at any time by disabling it in Settings.

5. Payment Data Is Handled Separately by Paddle

Purchases are processed by Paddle.com Market Ltd ("Paddle"), which acts as the Merchant of Record and an independent data controller for your payment information (name, email address, billing address, and card details). OreML does not receive, process, or store your payment card details, and we do not receive your Paddle account email or name unless you separately provide it to us (for example, by emailing support). Paddle's own privacy practices are described at paddle.com/legal/privacy.

6. Data Retention

Licence and machine-fingerprint records are retained for as long as needed to administer your licence, prevent abuse of the free trial, and comply with legal obligations. Opt-in telemetry, if enabled, is retained only as long as necessary for diagnostic purposes and is never linked to your dataset content, which we do not receive in the first place. Usage events are retained for 90 days.

7. Your Rights

Depending on your location, you may have the right to request access to, correction of, or deletion of personal data we hold about you (such as your licence ID, machine fingerprint, or the usage events recorded for your account), to object to or restrict certain processing, and to lodge a complaint with your local data-protection authority. To exercise any of these rights, contact support@oreml.com. If you are in the United Kingdom you may also use our UK representative — see Section 14. You may lodge a complaint with your local supervisory authority; in the United Kingdom that is the Information Commissioner's Office (ico.org.uk). For requests concerning your payment or billing data, please contact Paddle directly, as they are the controller for that information.

8. Data Security

Licence-related data is encrypted in transit, stored on access-restricted infrastructure in the European Union, and backed up nightly to encrypted storage. Because we never receive your dataset content, the security of your underlying data is governed by your own device's security, not by us.

9. Cookies and This Website

This website (oreml.com) does not itself set any cookies. It uses your browser's session storage only — cleared automatically when you close the tab — to remember standard advertising campaign parameters (source, medium, campaign) if you arrived here via a marketing link, so a signup completed later in the same visit can be attributed to that campaign. This is not a cookie, is not combined with any other identifier, is never sent to any third party, and disappears on its own. It is used only to tell us which marketing channel a signup came from — never to identify you individually or to track you across other websites.

We do not use advertising or cross-site tracking cookies of our own, and we run no analytics on this website today.

10. International Transfers

Our licence server and machine ledger are hosted in the European Union. Requests reach them through a global content-delivery network, which may process the request in transit outside the EU/UK under its own safeguards. Paddle, as the Merchant of Record and an independent controller for your payment data, may process and transfer that data outside the EU/UK under its own safeguards — see Paddle's privacy policy for how it handles international transfers of your payment data.

11. Children's Privacy

The Service is not directed at, and is not intended for use by, children. We do not knowingly collect personal data from children.

12. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by an updated "Last updated" date above.

13. Who We Are, and How to Contact Us

The data controller for the personal data described in this policy is OBSITH, trading as OBSITH / OreML — a sole proprietorship (Ατομική Επιχείρηση) established and registered in Greece, identified by the registration numbers below.

• Registered address: Ag. Lavras 42, 18450 Nikaia, Attica, Greece — Αγ. Λαύρας 42, 18450 Νίκαια, Αττική
• General Commercial Registry (ΓΕΜΗ) number: 195473709000
• Tax identification number (ΑΦΜ): 134747475 — EU VAT: EL134747475
• Contact: support@oreml.com

Questions about this Privacy Policy, about the Software, about your licence or subscription, and any request concerning your personal data can all be sent to support@oreml.com. That is the fastest route and the correct one for every country.

14. Our Representative in the United Kingdom

We are established in Greece and have no establishment in the United Kingdom. Under Article 27 of the UK GDPR we have appointed DataRep as our Data Protection Representative in the United Kingdom. If you are an individual in the United Kingdom, or a UK authority, you may reach us about the processing of your personal data through DataRep, in any of these ways:

• Email: datarequest@datarep.com — quote OBSITH / OreML in the subject line
• Online form: www.datarep.com/data-request
• Post: DataRep, 107-111 Fleet Street, London, EC4A 2AB, United Kingdom

When writing by post, address your letter to "DataRep" and not to OBSITH / OreML — mail addressed to us rather than to DataRep may not reach them. Please also name OBSITH / OreML clearly in your correspondence so that it can be routed to us. We may ask you to evidence your identity before acting on a request, so that your personal data is never disclosed to anyone but you.

This representative route is for individuals and authorities in the United Kingdom only, and only for matters concerning the processing of personal data. For every other country, and for anything else — support, billing, or the Software itself — please write to support@oreml.com instead. DataRep handles the personal data it needs in order to act for us in line with its own privacy notice at www.datarep.uk/privacy-policy.