Request deletion of Ordr and Meta personal data
Last Updated: October 18, 2026
1. Introduction
This page explains how to delete personal data associated with ordr ("we," "our," or "us"), including workspace accounts and data linked through Meta platforms (Facebook, Instagram, WhatsApp, Messenger). It complements our Privacy Policy and Terms of Service.
2. Ordr Tenant Admins — Delete Account & Data
If you are a Tenant Admin for an ordr workspace, you can permanently delete the workspace and all associated data from Settings:
This action is irreversible. It removes users, catalogs, conversations, orders, bookings, connected channel credentials, and other tenant-scoped records. Sign in to continue.
3. Meta Users — Request Deletion
If you connected Facebook, Instagram, or related Meta products that send data to ordr, you can request deletion through Meta's settings for apps and websites. Meta will call our Data Deletion Request Callback. We verify the signed request, remove matchable ordr data for that Meta user id when found, and issue a confirmation code.
You can also email youssefnaginassif@gmail.com with enough detail to identify the account or channel identity.
4. Check Deletion Status
After a Meta deletion request, use the confirmation code you received:
Open deletion status and enter your confirmation code, or open the status URL returned by Meta.
5. What Is Deleted vs Retained
Workspace deletion removes tenant-scoped operational data. Limited records may be retained where required for security, fraud prevention, accounting, or legal compliance (for example billing dispute logs), and only for as long as needed.
Meta callback deletions remove matchable conversation/client identifiers tied to the Meta user id. If no matching ordr data is found, the request is still recorded as completed with that result.
6. Channels and identifiers we may process
Depending on how you used Ordr, deletion may cover chat transcripts, customer profiles, order and booking records, WhatsApp / Instagram / Messenger / Telegram channel mappings, storefront account data, and integration tokens stored for your workspace. Meta-originated requests are scoped to the Meta user id in the signed payload; email requests should include the workspace name, phone number, or other identifiers that let us locate the right records without guessing.
After we finish a request we keep a minimal audit trail (confirmation code, time, and outcome) so you can check status later. That audit trail is not used for marketing and is retained only as long as needed for security and compliance.
7. Contact
Questions about deletion? Reach out at:
youssefnaginassif@gmail.com