Your Data: Access, Export and Deletion
Publication draft — contact hello@dropsite.hu
Different actions have different effects
| Action | Effect |
|---|---|
| Sign out | Ends the current app session; does not erase saved conversations, the account or all connector grants |
| Cancel subscription | Stops future renewal according to the purchase terms; is not itself an account-deletion request |
| Disconnect a connector | Removes its stored active connection credential in our backend; preferences or saved content may remain |
| Revoke in Google/ClickUp | Withdraws the provider-side grant; may affect several services sharing that grant |
| Delete a conversation | Must remove that conversation from applicable local and cloud stores; verify the implemented UI behaviour before relying on it |
| Clear/uninstall extension | Removes local data according to Chrome's behaviour; does not itself delete backend copies or cancel billing |
| Request account deletion | Starts a verified request to remove account-linked data, subject to legal exceptions and backup lifecycle |
How to make a request
Email hello@dropsite.hu, preferably from your account address. Suggested subject: resolvenengine data request. Say whether you want access/export, correction, deletion, restriction or to object to processing. For example:
Please delete my resolvenengine account and associated personal data. My account email is [email]. Please explain any records you must retain and confirm completion. Please also tell me whether my subscription needs separate cancellation.
We will verify identity proportionately. Do not send passwords, API keys, card details or identity documents unless a justified, secure verification method has been agreed. You may act through an authorised representative with suitable proof.
We will explain the action taken or any lawful reason for declining or limiting it, normally within one month. Complex or numerous requests may permit an additional two months; we will notify you within the initial month. Rights are generally free of charge, subject to the GDPR's limited exceptions.
What a deletion must cover
The operational deletion process must address the account mapping, sessions, OAuth and hand-off records, connector credentials and settings, cloud conversations and attachments held on our servers, and relevant local data when the extension next synchronises. Deletion must not allow an old local copy to silently re-create cloud data. Provider revocation and downstream erasure requests must be considered separately.
Records required for applicable law, necessary legal claims or proportionate fraud prevention may need to be retained with access restricted to that purpose. Polar and other independent controllers handle their own statutory records and rights requests. A backup copy must not return to ordinary use after deletion; any restoration must reapply deletion instructions.
[PUBLISH-14: operationally verify manual deletion/export and backup handling before publication. A self-service delete-account endpoint was not established by the reviewed code. Insert the supported local/cloud deletion steps and actual retention deadlines.]
The Privacy Policy provides complaint information and details of your rights. Deletion of an app account should not silently leave an unwanted recurring subscription active: confirm the billing outcome explicitly with the user and Polar.