User Data Deletion

Last updated:

This page explains how individuals can request deletion of personal data processed by SatuBooster (including the Satugram assistant). For general privacy terms see our Privacy Policy.

Who can use this page?

End-users who messaged a customer’s Instagram Page handled via Satugram.
Customers/admins who created an account on SatuBooster.

If you contacted a brand on Instagram, the brand is the data controller. We act as their processor and will pass your request to the brand and delete processor copies accordingly.

Fastest ways to delete your data

Inside the app (for customers/admins): sign in → Settings → Account → Delete account. This removes your workspace, settings, access tokens and logs (backups roll off within 30 days).
Instagram end-users: send the keyword стоп to the brand to disable automation, then use the form below or email us to request deletion of processor copies related to your conversation.

Submit a deletion request

We need enough information to locate your records. We verify requests and respond within applicable legal timeframes.

Prefer email? Write to [PRIVACY CONTACT EMAIL] with subject “Deletion request” and include the details above.

What we delete

Instagram message payloads and metadata processed by Satugram for the specified conversation(s).
Comments/mentions ingested for automation (if applicable).
Account data and configuration (for customers who close the account).
Server/application logs after their rolling retention window.

What we keep (temporarily)

Minimal records required to prevent fraud or comply with law (e.g., audit entries).
Encrypted backups that automatically expire within up to 30 days.

Developer endpoints (for your reference)

If you run your own instance, expose a simple deletion API and link it here.

Example HTTP endpoint

POST /api/privacy/delete-request

{
  "email": "user@example.com",
  "ig_username": "example_user",
  "page_or_business": "satubooster.kz",
  "details": "Please delete messages related to @example_user with Brand X"
}

After verifying identity, your backend should: (1) revoke tokens/disable automation if needed, (2) purge matched message rows, (3) scrub configuration/account (if requested), (4) queue backup redactions, (5) confirm to the requester.

Contact

[COMPANY LEGAL NAME]
[REGISTERED ADDRESS]
Email: [PRIVACY CONTACT EMAIL]