Data Deletion Policy

This page tells you how to delete your data from GPTpostLLM, what happens when you revoke the Service's access at a social platform, and exactly how long each step takes. This is the data deletion instructions page for social platform app review. It is public, needs no account, and no part of it is behind a URL fragment.

The provider is TRIIVON S.R.L., Bucharest, Sector 4, Sos. Giurgiului nr. 131, Bloc 1, Scara 2, Etaj 9, Apartament 65, postal code 040665, Romania, 53596703. Write to contact@oraglegpt.org for anything on this page.

1. The four ways data gets deleted

Each is explained below.

2. Disconnect a single social account

In the Service, open the connected accounts screen and disconnect the account.

The stored credential for that connection is deleted from our systems. The Service can no longer publish to it. Scheduled posts that targeted only that account will not be sent.

This does not delete anything on the social platform itself. Posts already published stay published. That is a hard limit of how the Service works, not a policy choice: every connector is publish-only, so the Service holds no permission to delete or edit anything on any platform and could not remove those posts even if you asked it to. Use the platform's own tools for that.

3. Revoke the Service's access at the platform

You can remove the Service's access from the platform's side, for example in the Facebook or Instagram app settings under business integrations.

For Facebook, Instagram and Threads we receive a signed callback when you do this, and we act on it without waiting for you to tell us:

Both verify an HMAC-SHA256 signature and reject anything older than a five-minute freshness window, so a replayed or forged callback is refused.

On a valid deletion callback we queue the erasure immediately, with no grace period, and return a confirmation code and a status URL, which is what the platform requires. You can check progress at /privacy/deletion-status/{code}. An unknown code returns 404 rather than a misleading answer.

These two endpoints are the only inbound callbacks the Service has. Nothing else is ever pushed to us by any provider.

For the other providers there is no such callback, because those platforms do not send one. Revoking access there stops publishing; to remove the data we hold, disconnect the account in the Service or write to contact@oraglegpt.org.

4. Close a workspace

A workspace owner can close a workspace at Settings, Data Privacy in the Service.

Closure moves the workspace through active to pending_deletion to closed. For 30 days from the moment you close it, the workspace stays readable and exportable: you can sign in, look at the data and download a full export. Publishing stops. The scheduled deletion date is recorded on the workspace so you can see it.

You can reverse this during the 30 days by reopening the workspace. Nothing is lost if you change your mind.

How the final erasure is carried out, stated precisely. The 30-day window, the state changes and the recorded deletion date are all enforced by the software. The final erasure at the end of the window is carried out by us as an operational commitment; it is not executed by an automatic job on this deployment. We are stating this rather than describing an automation that is not switched on. If you want written confirmation that a specific workspace has been erased, ask at contact@oraglegpt.org and we will confirm in writing.

5. Delete your account entirely

Account deletion is requested through the API:

POST /api/v1/privacy/deletion-requests

There is no delete-account button on the Data Privacy screen. If you would rather not call the API, email contact@oraglegpt.org and we will raise the request for you. We will confirm in writing when it is done.

A 30-day grace period applies. For 30 days the request can be cancelled, by you or by us on your instruction, and your data is restored to normal use. The 30 days is fixed in the software, not a discretionary target.

After the grace period your personal data and content are erased, subject only to the narrow exceptions in section 7.

6. Export your data before you delete it

Take a copy first. Data export is at Settings, Data Privacy.

The export runs immediately and downloads a signed archive with the .optenant extension. It contains manifest.json and records.json and covers 48 resource families. The archive carries a SHA-256 payload digest and an HMAC manifest signature, so you can tell whether it has been altered.

Stored credentials are never included in an export. Your social access tokens and API keys stay out of it by design.

There is no import or restore route in the Service. An export is a copy for you to keep, not a backup you can load back in.

7. What we keep, and for how long

Some data outlives a deletion request because the law requires it or because deleting it would destroy the integrity of a security record.

The audit log is append-only by design. It is hash-chained and the database itself refuses updates and deletes, which is what makes it trustworthy evidence. Entries record that an action happened, by which actor and against which record. Where an entry contains personal data and you have exercised a right of erasure, we minimise the entry so the chain stays intact while the personal data goes.

The inbox retention constant in the software has no effect here, because no connector reads an inbox, so no inbox data is ever collected.

8. Deletion at the platform, which we cannot do for you

We want this to be unambiguous, because it is the single most common misunderstanding.

Deleting your data from GPTpostLLM does not delete anything from Facebook, Instagram, TikTok, or any other platform. Content that has been published lives on that platform under that platform's terms and retention rules.

We cannot delete it for you. The Service's connectors are publish-only: they hold no delete permission, and no code path exists that could issue a delete to a platform API. If you want a published post removed, you must remove it using that platform's own tools, or ask that platform directly.

The same applies to your rights as a data subject against a platform: we cannot exercise them on your behalf. See Your Data Protection Rights.

9. Your rights

Deletion is one of the rights in Articles 15 to 22 of the GDPR, read with Legea nr. 190/2018. The right to erasure is Article 17.

How to make a request, how we verify who you are without asking for more documents than necessary, and our response times are in Your Data Protection Rights.

If you are unhappy with how we handle a deletion request you may complain to Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP):

• https://www.dataprotection.ro
• B-dul G-ral. Gheorghe Magheru nr. 28-30, Sector 1, cod poștal 010336, București, România
• anspdcp@dataprotection.ro

You also have the right to a judicial remedy.

10. Timings, in one table

11. Related pages