GDPR and your data rights

Leenops is designed to help organizations handle personal data responsibly and respond to privacy requests. This page explains the practical safeguards available in Leenops. It is product information, not legal advice.

Who is responsible for your data?

For information that an organization stores in its Leenops workspace, that organization normally decides why and how the information is used. Leenops processes that information to provide the service.

Leenops may separately be responsible for limited account, billing, website, and service-usage information that it collects directly. The applicable Privacy Policy and Data Processing Agreement describe these roles in more detail.

Your rights

Depending on where you live and the circumstances, you may be able to ask for:

access to personal data;
correction of inaccurate data;
deletion of personal data;
restriction of, or objection to, certain processing;
a portable copy of eligible data.

These rights are not absolute. For example, an organization may need to retain limited information to meet a legal obligation, protect security, establish a legal claim, or keep records that must remain accurate.

How to submit a request

If your request concerns information managed by a Leenops customer, contact that organization first. It is normally best placed to verify you and decide how the request applies to its records.

For a Leenops account request, or if you are unsure who to contact, email privacy@leenops.com. Include:

the email address associated with your account;
the organization or workspace concerned;
the right you want to exercise;
enough context for us to locate the correct account.

Do not email passwords, authentication codes, identity-document scans, or other secrets unless our privacy team specifically requests information through an approved secure channel.

What happens next

We verify that the request concerns the correct person and account before making an irreversible change. If a workspace would otherwise be left without an administrator, an ownership transfer may be required first. A request may also pause while a documented legal obligation or legal hold is reviewed.

For an account-deletion request, Leenops uses a controlled workflow that:

stops active Leenops access;
disconnects linked accounts and removes stored connection credentials;
removes or anonymizes personal account data covered by the request;
removes user-owned files covered by the request;
removes the Leenops sign-in identity;
checks for remaining account references;
records limited evidence that the request was handled.

You receive a message when processing starts and another when it completes. If the workflow cannot complete, the request remains visible to the support team for follow-up instead of being silently treated as finished.

Deleting a Leenops account does not delete your Microsoft, Google, or other third-party account. It removes Leenops's connection to that account.

Data that may be retained

Deletion means removing or anonymizing the personal data covered by the request. Limited information may remain when retention is required for legal, security, fraud-prevention, accounting, dispute, or compliance purposes.

Backup copies may also remain protected for a limited period until they expire through the normal backup lifecycle. They are not restored for ordinary product use. If a backup must be restored for disaster recovery, applicable deletion controls must be applied again.

How we protect the process

Deletion requests use identity checks, authorization controls, ownership and legal-hold checks, restricted administrative access, and an observable request history. We avoid relying on a simple sign-in-account deletion because that alone would not address data stored elsewhere in the service.