Privacy Policy

Last updated: 7 October 2026.

RemDo is an early-stage project under active development. This Privacy Policy explains how personal data is handled when you use the RemDo service operated at remdo.com.

The service is currently operated by Piotr Lewalski, a private individual based in Poland, who is the controller of personal data described in this policy.

For privacy questions or requests, contact piotr@remdo.com.

Information we process

Depending on how you use RemDo, we process:

Why we process information

The purposes and legal bases for processing are:

Where processing is based on consent, you can withdraw that consent at any time. Withdrawal does not affect the lawfulness of processing carried out before consent was withdrawn.

Information required to use RemDo

You are not legally required to provide personal data to RemDo.

However, some information is necessary to provide particular features. For example, account information is required to create and maintain an account, and information from an authentication provider is required if you choose that method of signing in.

Content, integrations and other information are provided when you choose to use the corresponding RemDo features.

Usage statistics are not required to use the core RemDo service, and you can turn them off.

Product updates

“Keep me posted” stores your email address and request time for occasional RemDo product updates. The form currently collects requests only; it sends no email. Requests are stored separately from accounts and remain unconfirmed until subscription confirmation is introduced. An existing account's verified email does not confirm a request submitted through this public form.

You can withdraw your request or ask us to delete it by contacting piotr@remdo.com. A recorded withdrawal excludes your address from future contact, and submitting that address through the public form again does not undo the withdrawal. Deleting an account alone does not delete a separate update request; a request to delete all your personal data includes both.

Usage statistics

RemDo uses Umami Cloud on remdo.com to count how people find and use the product, so we can see which pages and features are useful and whether people come back. Umami's tracking code does not use cookies.

Umami receives basic usage information such as page views, referrer URLs, browser, operating system, device type and country. RemDo also sends a small set of explicit product events: opening the signed-in app, creating or importing a document, editing a document and using search. It does not send document or note contents, document titles or identifiers, filenames, or search text. Document routes are reduced to a generic route before the statistics are sent.

While you are signed in, RemDo also sends your account's internal user identifier as a pseudonymous ID, so that visits on different days can be connected. It is not sent when you are signed out and it is not your name or email address.

You can turn the statistics off at any time through Privacy settings in the RemDo footer, and RemDo respects your browser's Do Not Track setting. Turning them off does not prevent you from using the core RemDo service. Data already collected stays until it expires; to have it deleted sooner, contact us.

RemDo does not use personal data for advertising and does not use the contents of your documents for advertising.

Cookies and browser storage

RemDo uses browser storage needed to provide the service.

This includes local browser storage used for account-related state and IndexedDB and local storage used for local and offline document functionality. Locally persisted document data is encrypted by RemDo before being stored in the browser.

Authentication methods may also use cookies or similar browser mechanisms necessary to keep you signed in and secure your session.

These technologies are used where necessary to provide functionality you request.

If you turn usage statistics off, your browser stores that choice in local storage so that it applies to later visits.

Authentication

RemDo can support authentication using an email address and password, a one-time code sent to your email address, or third-party authentication providers.

If you choose a third-party provider, RemDo receives information needed to identify your account, such as an account identifier, name or email address, depending on that provider and the permissions involved.

The authentication provider separately processes information under its own privacy policy.

Passwords used directly with RemDo are not stored in readable form.

Your content and third-party integrations

RemDo processes content you provide so that it can provide the functionality you request.

You can also choose to give another service or application access to information in RemDo, for example through an integration, API or MCP connection.

When you deliberately authorize such an integration, RemDo can provide information requested through that connection to the service you authorized. How that third party subsequently processes the information is governed by its own terms and privacy practices.

RemDo does not provide your document content to third-party integrations unless the functionality you use requires it or you authorize the connection.

When you deliberately share or collaborate on content through RemDo, information associated with that content or collaboration may be visible to the people you share it with.

Service providers and other recipients

We use third-party providers where necessary to operate RemDo. These can include providers of:

These providers process personal data only to the extent relevant to the services they provide.

Personal data can also be disclosed:

We do not sell personal data.

International processing

Some service providers can process personal data outside Poland or the European Economic Area.

Where GDPR requires safeguards for such a transfer, we rely on an applicable transfer mechanism, such as an adequacy decision or appropriate contractual safeguards.

You can contact piotr@remdo.com for information about safeguards applicable to transfers of your personal data and, where applicable, how to obtain a copy of them.

How long we keep information

We keep personal data only for as long as needed for the purposes for which it is processed.

In particular:

Information can be retained for longer where required by law or where necessary to establish, exercise or defend legal claims.

Security

We take reasonable technical and organizational measures to protect personal data.

RemDo is, however, an early-stage service under active development. No online service can guarantee absolute security, so you should consider the sensitivity of the information you choose to store in it.

Automated decision-making

RemDo does not currently use solely automated decision-making, including profiling, that produces legal effects concerning you or similarly significantly affects you.

Product experiments such as assigning users to different versions of a feature do not make decisions of this kind.

Your rights

Under the GDPR, depending on the circumstances, you may have the right to:

To exercise these rights or ask a privacy-related question, contact piotr@remdo.com.

You also have the right to lodge a complaint with a data protection supervisory authority. In Poland, the supervisory authority is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych).

Self-hosted RemDo

This Privacy Policy applies to the RemDo service operated at remdo.com.

If you run RemDo yourself or use an instance operated by somebody else, that operator determines how information on its instance is processed. This Privacy Policy does not describe the practices of independently operated RemDo instances.

Changes to this policy

RemDo is under active development, so this Privacy Policy will change as the service evolves.

Minor changes, clarifications or corrections can be published by updating this page.

If a change materially affects how we process existing users' personal data, we will provide appropriate notice before or when the change takes effect where required by applicable law.

The current version and its last-updated date are shown at the top of this page.