1. What you can delete, and where
| What | Web | Mobile app | Who can do it | Effect |
|---|---|---|---|---|
| A channel (one connected social account) | Brand → Channels → Disconnect | Brand → Channels → Disconnect | Owner, Admin, Editor of that brand | Our access is revoked immediately (the token is revoked on the platform where the API allows, then deleted, or the Aggregator profile is deleted); scheduled posts to that channel move to "Ready — reconnect to post"; the platform account identifiers and insights for that channel are deleted on the timeline in Section 4. |
| A brand | Brand → Settings → Delete brand | Not available (web only) | Owner, Admin (or the agency that owns the brand) | All channels disconnected; posts, drafts, assets, Brand Brain, occasions, approvers, metrics for that brand enter the deletion timeline. |
| Your own account (you, as a member) | Settings → Account → Delete my account | Settings → Account → Delete my account | Any member. An Owner of an organisation with other members must first transfer ownership or delete the organisation; the sole Owner of an organisation is offered "Delete my account and organisation" in one step, on the web and in the app | Your sign-in, profile, preferences, push tokens and staff-access log are deleted; your name on past approvals is replaced by "former member" (identifier retained for the audit trail). |
| Your organisation (everything) | Settings → Organisation → Delete organisation | Settings → Organisation → Delete organisation (so that an Owner can always delete their account from inside the app, as Apple and Google Play require) | Owner only | Every brand, channel, member, approver, asset, ledger row and setting enters the deletion timeline; the subscription is cancelled; any prepaid unused wallet balance is refunded under the Refund Policy. |
| An approver | Brand → Approvers → Remove | — | Owner, Admin, Editor | Magic links are invalidated at once; the approver's contact details are removed; each approval they made stays as a dated audit entry with a pseudonymous reference. |
| Uploaded media | Brand → Kit → remove the asset | — | Owner, Admin, Editor | Removed from storage and from future generations; posts already rendered with it keep their rendered files until those posts are deleted. |
| Consent records (real-person likeness) | Brand → Kit → People → remove | — | Owner, Admin | The consent record is deleted with the assets that relied on it; generation of that person's likeness is blocked again. |
| WhatsApp opt-in contacts (add-on) | Brand → WhatsApp → Contacts → remove or import a removal list | — | Owner, Admin, Editor | Removed from the send list. A contact who replied STOP is kept on a suppression list (number only) so we never message them again. |
| An enquiry from your Brand's page | Brand → Link page → Enquiries → Delete | — | Owner, Admin, Editor | Deleted at once, for good; the record says an enquiry was deleted, never whose. A person who enquired can ask the business, or write to us, to have it deleted. |
| A demo run (no account) | Nothing to do | — | — | Demo runs are deleted automatically after 7 days. |
You do not need to contact us for any of these. If you cannot sign in, e-mail contact@adrologic.com from the address on the account (or reply to a one-time code sent to your phone) and we will run the same deletion for you.
2. What happens when you delete an account or organisation
- Immediately: publishing stops; every channel is disconnected and its token revoked or its Aggregator profile deleted; magic links stop working; Autopilot is switched off; the subscription is cancelled; you receive a confirmation code and a status link (
craivis.com/deletion/{confirmation_code}) by e-mail. - Days 0-7 (cooling-off): the organisation is frozen and invisible in the product. If you sign in and choose "Cancel deletion" within 7 days, everything is restored except channel connections, which you reconnect through the platform's login.
- After day 7: the deletion clock starts. Data is erased from live systems within 30 days (our target is 7 days). The erasure is tenant-scoped and walks every store that holds your data (Section 5).
- Within 30 more days: encrypted backups that contained your data expire (backups are kept for 30 days).
- Status link: shows "requested", "cooling-off", "in progress" and "complete", with dates. Keep the confirmation code; it is the only way to prove the request later. We keep the request record (code, dates, status; no content) for 1 year after completion.
If you only cancel your subscription and do not ask for deletion, your drafts and history stay readable for 30 days after the paid period ends, and then the deletion clock in step 3 starts automatically (Terms, Section 13.1).
3. Removing CRAIVIS from Facebook or Instagram (Meta's Data Deletion Callback)
3.1 Where. Facebook: Settings & privacy → Settings → Apps and websites (or, for business assets, Business Integrations) → find CRAIVIS → Remove. Instagram: Settings → Website permissions → Apps and websites → Active → Remove. Threads: Settings → Account → Apps and websites.
3.2 What Meta does. When you remove the app, Meta sends a signed request to our deletion endpoint with your app-scoped user ID. We verify Meta's signature, create a deletion request, and reply to Meta with a confirmation code and a status URL, which Meta shows you.
3.3 What we do. We disconnect every channel that was connected through that Meta login (the Instagram account, Facebook Pages and Threads profile it granted), delete the tokens, and delete the Meta-sourced data for those channels (account and page identifiers, usernames, profile pictures, insights) on the timeline in Section 4. Your CRAIVIS account, brand profile, drafts and content are not deleted by this route, because they are yours and not Meta's; delete them under Section 1 if you want them gone too.
3.4 During the Aggregator bridge. Until Meta approves our own app, the consent screen you saw showed our white-labelled Aggregator app name and Meta's callback goes to the Aggregator, which deletes its profile for you. Our connection-health check detects the revoked connection within 24 hours and marks the channel "needs re-authorisation"; we then treat it as a Section 3.3 deletion for the Meta-sourced data. If you want that done sooner, disconnect the channel in the product (Section 1) or e-mail contact@adrologic.com.
3.5 Instructions instead of a callback. If for any reason the callback fails, this page is our Data Deletion Instructions: e-mail contact@adrologic.com with the Meta account name and we will run 3.3 by hand and send you a confirmation code.
4. Timelines
| Event | Publishing stops | Access to social accounts revoked | Live data erased | Backups expire | Status |
|---|---|---|---|---|---|
| Disconnect a channel | Immediately (that channel) | Immediately | Meta-sourced data for the channel within 30 days (target 7) | +30 days | In-product |
| Delete a brand | Immediately (that brand) | Immediately | Within 30 days of the request (target 7) | +30 days | In-product |
| Delete account / organisation | Immediately | Immediately | 7-day cooling-off, then within 30 days (target 7) | +30 days | Status link |
| Meta Data Deletion Callback | Immediately (the affected channels) | Immediately | Meta-sourced data within 30 days (target 7) | +30 days | Status URL given to Meta |
| Subscription cancelled, no deletion request | At the end of the paid period | At the end of the paid period | 30 days readable, then within 30 days (target 7) | +30 days | E-mail before the clock starts |
| Non-payment (Terms 12.5) | Day 7 after the failed charge | On cancellation at day 30 | As "subscription cancelled" | +30 days | E-mail at each step |
| Inactive account (no sign-in and no subscription for 12 months) | — | — | We e-mail you at least 48 hours before, then erase within 30 days | +30 days | |
| Erasure request from a person whose data we process for a customer (DPDP / GDPR right) | — | — | Forwarded to the customer within 2 business days; erased on the customer's instruction, or by us if the customer no longer exists | +30 days |
Our target of 7 days applies whenever the erasure job runs without a legal hold; the 30-day outer limit applies in every case.
5. What is erased, store by store
| Store | What is erased |
|---|---|
| Database (our own server in India, hosted by Contabo) | All rows for the organisation, brand or channel: organisation, memberships, brands, brand profile, brand assets, Brand Brain memory chunks and preferences, occasions, approvers, channels, channel tokens (ciphertext), posts, variants, generation jobs, provider-call rows (cost rows are kept as anonymised totals), metrics, moderation events, consent records, white-label settings, site audits, WhatsApp opt-in ledger (except the suppression list of numbers that opted out), deletion request content |
| Object storage and CDN (Cloudflare R2, Images) | Original uploads, generated assets, per-platform variants, C2PA-signed exports, backup files as they expire |
| Rendering worker (Railway) | Transient files are deleted at the end of each render; nothing persists |
| Workflows (Inngest) | Running jobs are cancelled; event history contains identifiers only and expires per the vendor's retention |
| Publishing Aggregator (Upload-Post) | The profile and its tokens are deleted through the Aggregator's API at disconnect |
| AI providers (Anthropic, Google, fal.ai, WaveSpeed) | We keep no data there; prompts and outputs are processed under each provider's retention (no training on inputs; short-lived operational retention). We do not resend your data after deletion |
| LLM traces (Langfuse, from month 4) | Traces for the tenant are deleted |
| E-mail (Resend) | Delivery logs expire per the vendor's retention; we configure or confirm at most 90 days at contracting |
| Analytics (PostHog) | The person profiles for the organisation's members are deleted through the vendor's deletion API; aggregate event counts remain without identifiers |
| Errors (Sentry) | Events expire after 90 days; user IDs are removed from any event that has not yet expired on request |
| Push (Expo, Apple, Google) | Device tokens are deleted |
| Payments (Razorpay) | Mandates are cancelled and card tokens revoked. Razorpay keeps what payment law requires it to keep, as its own controller |
| Search Console and Google data | Cached data is deleted; you can also revoke CRAIVIS at myaccount.google.com/permissions |
| Support (e-mail, WhatsApp Business) | Threads are deleted 2 years after closure or on request |
6. What we keep, and why
| Kept | For how long | Why |
|---|---|---|
| Invoices, ledger entries, refund and mandate records (billing identity and amounts; no content) | 8 years from the end of the financial year | Companies Act, 2013 and GST record-keeping |
| Audit rows for brand transfers (brand ID, from and to organisation IDs, dates, who requested and accepted) | Permanently | Dispute resolution between agencies and clients; the plan's audit design |
| The deletion request record (confirmation code, dates, status; no content) | 1 year after completion | Proof that we deleted, if you or a regulator ask |
| Approval audit entries (date, decision, IP, user agent, pseudonymous reference) after the approver or member is deleted | Life of the brand | Proof of who instructed a publication |
| WhatsApp suppression list (numbers that opted out) | Until the customer's WhatsApp Business Account is disconnected | To honour the opt-out |
| Anonymised cost and usage totals | Indefinitely | Unit economics; contains no personal data |
| Anything under a legal hold | Until the hold ends | A court order, a regulator's request, or a pending claim; we tell you unless the law forbids it |
| Content already published on a platform | — | It lives on the platform under your account; delete it there (or from the product where the API allows: Facebook and Threads at launch, X and Bluesky when offered; Instagram's API does not allow deletion) |
7. Agencies and their clients
7.1 If an agency manages your brand, the agency owns the brand record and can delete it. Ask the agency first.
7.2 If you have left the agency, either ask the agency for a brand transfer (your brand moves to your own organisation with everything intact and you can then delete or keep it) or write to contact@adrologic.com. Where you can show that a connected social account is yours (you can always prove that by revoking access on the platform itself), we disconnect that channel and delete its platform-sourced data whatever the agency says. For the brand's other content, which the agency created for you under its contract with you, we act on the agency's instruction or, if the agency does not respond within 14 days, on yours.
7.3 Approvers (agency clients who only receive links) can ask the agency or us to remove their contact details at any time; Section 1 applies.
8. Mobile app
The iOS and Android apps offer "Delete my account" in Settings → Account and, for Owners, "Delete organisation" in Settings → Organisation, with the same cooling-off, confirmation code and status link as the web. No user is ever sent to the web to delete their account. This meets Apple's App Store Review Guideline 5.1.1(v) and Google Play's account-deletion requirement. Uninstalling the app does not delete your account.
9. Your rights and how to complain
Deletion here is how we honour the right to erasure under India's DPDP Act (and the GDPR where it applies). If a deletion does not complete on the timeline above, or you disagree with what we retained, write to our Grievance Officer at contact@adrologic.com (named in the Privacy Policy). If you are not satisfied you may complain to the Data Protection Board of India.
10. Changes
We will post changes here with a version and date and keep prior versions at craivis.com/legal/deletion/history.