Data Deletion
Last updated 16 August 2026
You can delete your Crosspost account and everything we hold for you at any time. Nothing survives it: no rows, no stored files, and no access tokens. This page is the deletion instructions URL we give to Instagram, TikTok and YouTube.
Delete from your account
The button below deletes everything in one step — in the app it calls DELETE /api/account. Disconnecting a single platform from your dashboard is the narrower version: it hands that platform's OAuth grant back and removes the data cached for it, leaving the rest of your account intact.
Sign in to delete your account directly, or email us using the request method below.
Request by email
If you can't access your account, email privacy@joincrosspost.com from the address on your account with the subject "Data deletion request". We will delete your data and confirm within 30 days.
What happens, in order
- We ask each platform to hand your permission back first. We call Instagram's, TikTok's and YouTube's own revoke endpoints for every account you connected, before anything local is destroyed — afterwards there would be no credential left to revoke with. This step is best-effort, and not every platform honours it: one that is unreachable, that refuses the request, or that offers no revoke endpoint at all cannot block your deletion, and we log the outcome either way. So that you are certain, remove this app from the connected-apps screen on the platform itself as well — it is listed there under the name the app is registered with on that platform, which may not be the name you see here. That is the only route that does not depend on the platform honouring ours.
- Your files are swept out of storage explicitly. Deleting the database rows does not remove the video files and thumbnails — a database cascade cannot reach into file storage — so every object stored under your account id is removed as its own step, in both private areas:
video-analysisandrepurpose-src. This includes uploads you started and never finished. - The records no foreign key can reach are swept by account id. Your row on the invite list (
public.allowed_emails) and every background-job envelope belonging to you, both queued (pgmq.q_creato_jobs) and archived (pgmq.a_creato_jobs). - Your connected accounts and then your login row are deleted, and the database removes everything that hangs off them.
What gets deleted
Every record below, generated from the same inventory the deletion routine itself is built against — so this list cannot quietly fall behind what the code removes.
Your Crosspost account
- Your first name and app settings
public.user_profiles - What you consented to, and when
public.user_consents - The invite list
public.allowed_emails - Your Crosspost login
auth.users - Your sign-in identity
auth.identities - Your sign-in sessions
auth.sessions - Confirmation and password-reset tokens
auth.one_time_tokens - Two-factor authentication methods
auth.mfa_factors - Sign-in authorisation records
auth.oauth_authorizations - Sign-in consent records
auth.oauth_consents - A sign-in still in progress
auth.flow_state - Your authentication event log
auth.audit_log_entries
The accounts you connect
- The accounts you connected, and their tokens
public.connected_accounts - The cached copy of your profile and posts
public.platform_data - A connection you are part-way through
public.oauth_connect_pending
Your content and your analytics
- Your daily follower and engagement history
public.snapshots - Analyses of your own videos
public.video_analyses - How each post we published performed
public.repurpose_target_metrics
Cross-posting and auto-pilot
- The crossposts you create
public.repurpose_posts - Each account a crosspost went to
public.repurpose_targets - Your auto-pilot settings
public.autopilot_rules - The accounts auto-pilot may post to
public.autopilot_rule_targets - What auto-pilot has already handled
public.autopilot_seen
Files and background work
- The background work queued for your account
public.jobs - The archive of background jobs
pgmq.a_creato_jobs - Background jobs waiting to run
pgmq.q_creato_jobs - The index of the files we hold for you
storage.objects - An upload that did not finish
storage.s3_multipart_uploads - The chunks of an unfinished upload
storage.s3_multipart_uploads_parts
Plus every file under your account id in video-analysis and repurpose-src.
The one caveat we will not hide
Two of the sign-in records above are maintained by our authentication provider rather than written by Crosspost — auth.flow_state and auth.audit_log_entries and storage.s3_multipart_uploads and storage.s3_multipart_uploads_parts. We believe deleting your account removes them, and we are measuring it rather than assuming it. Until that measurement is recorded, email us and we will remove them by hand.