Privacy Policy
Effective Date: March 18, 2026
Last Updated: October 2, 2026
Welcome to status: 200 | uploads ("Service," "Platform," "we," "us," or "our"). We are committed to protecting your personal data and respecting your privacy. This Privacy Policy explains how we collect, use, disclose, store, and safeguard your information when you use our social media automation platform at status200uploads.com, including our web application, API, and all related services.
By creating an account, connecting social media accounts, uploading media, or using our API, you consent to the data practices described in this Privacy Policy. If you do not agree with this policy, please do not use the Service.
1. Information We Collect
We collect information in several ways depending on how you interact with our Service:
1.1 Account Information
When you create an account, we collect:
- Email address
- Password (stored in hashed form; we never store or have access to your plaintext password)
- Full name
- Account creation date and timestamps
1.2 Social Media Account Data
When you connect social media accounts via OAuth authorization (or, for Skool, with your Skool session cookie), we collect and store the following data from each platform:
TikTok
- OAuth access token and refresh token
- Token expiration timestamps
- TikTok Open ID (unique account identifier)
- Display name and username
- Granted permission scopes (user.info.basic, video.upload, video.publish)
- OAuth access token (long-lived, approximately 60-day validity)
- Instagram User ID
- Username, account type, profile picture URL
- Granted permission scopes (instagram_business_basic, instagram_business_content_publish, instagram_business_manage_insights)
- User access token (exchanged for long-lived token)
- Facebook Page ID and Page name
- Page profile picture URL and page category
- Granted permission scopes (pages_manage_posts, pages_read_engagement, pages_show_list, read_insights)
YouTube
- OAuth access token and refresh token
- YouTube Channel ID and channel title
- Channel thumbnail URL
- Subscriber count and video count
- Token expiration timestamps
- Granted permission scopes (youtube.upload, youtube.readonly)
X (Twitter)
- OAuth 2.0 access token and refresh token
- X User ID and username
- Display name and profile image URL
- Follower count and tweet count
- Token expiration timestamps and PKCE code verifier
- Granted permission scopes (tweet.read, tweet.write, users.read, offline.access)
- OAuth 2.0 access token and refresh token
- LinkedIn Member ID (unique account identifier)
- Name and profile picture URL (via OpenID Connect)
- Email address (via OpenID Connect)
- Token expiration timestamps
- Granted permission scopes (openid, profile, w_member_social)
- OAuth tokens (access token, refresh token)
- Profile information (username, profile image URL)
- Board information (board IDs, board names)
- Token expiration timestamps
- Granted permission scopes (boards:read, pins:read, pins:write, user_accounts:read)
Threads
- OAuth tokens (access token, refresh token)
- Threads user ID and username
- Threads profile picture URL
- Published Threads post IDs and permalinks
- Engagement metrics (views, likes, replies, reposts, quotes) for your posts
- Token expiration timestamps
- Granted permission scopes (threads_basic, threads_content_publish, threads_manage_insights)
Skool
- Your Skool session cookie (auth_token), which you paste in yourself because Skool has no OAuth; stored encrypted
- The cookie's expiry date
- Skool user ID, display name and profile picture URL
- Skool client ID, if it is part of what you paste
- The group and category you choose for each post, and the IDs and links of published Skool posts
The cookie is sent only to Skool and to a posting server we operate, which uses it to obtain the short-lived security token Skool requires before it accepts a post.
1.3 Media and Content Data
When you upload media or create posts, we collect:
- Uploaded image and video files (JPEG, PNG, WebP, MP4, MOV, WebM)
- File metadata including file name, file size, file type, and upload timestamp
- Post content including captions, hashtags, mentions, and platform-specific metadata (e.g., YouTube video titles, descriptions, tags, privacy settings, categories)
- Scheduling preferences such as post time, target platforms, and posting settings (e.g., TikTok privacy levels, branded content flags, comment/duet/stitch toggles)
1.4 Payment Information
When you subscribe to a paid plan:
- We do NOT collect or store your credit card number, CVV, or other payment card details
- All payment processing is handled by Whop, Inc., our third-party payment processor
- We store your Whop membership ID and user ID to link your payment account
- We store subscription metadata including plan type, subscription status, billing period dates, and plan ID
- Whop webhook event records are processed for billing reconciliation, including the date, amount and ID of your latest payment and any refund Whop reports
- If you request a refund, we store the request: the plan and payment it concerns, the reason you give (optional), and its outcome
1.5 API Usage Data
When you use our REST API, we collect:
- API key used for authentication
- API endpoint and HTTP method called
- Request body and response body
- IP address and User-Agent header
- HTTP status code and response time
- Error messages (if any)
- Request timestamp
1.6 Automatically Collected Data
When you access the Service, we may automatically collect:
- IP address
- Browser type and version
- Operating system
- Referring URLs
- Pages visited and features used within the Service
- Date and time of access
Product analytics with PostHog (pages and clicks) runs only if you turn on Analytics in the cookie settings, and session recordings only if you also turn on Session recordings. Error reports go to Sentry. See Section 7.
1.7 How You Found Us (recorded once at sign-up)
When you create an account, we record once how you found us:
- The campaign tags of the link you arrived through (utm_source, utm_medium, utm_campaign, utm_term and utm_content)
- The domain of the website that sent you, for example youtube.com, never the full address of the page
- The first page you opened on our site, as a path only (for example /pricing), without anything after it
- When you first visited
- If the link carried an advertising click ID, only the name of that ID (for example "gclid"), never its value
From this we derive one word for the channel, such as youtube, google, referral or direct. We do not record full web addresses.
Why: to learn which channels bring us new accounts, so we can put our marketing where it works. We rely on our legitimate interest in understanding how people find the Service. It is used only for our own statistics, never for advertising, and never shared with advertising networks.
How long: it is kept with your account and deleted when your account is deleted.
In your browser: during your visit this is held only in the page's memory. It is kept between visits (s200_first_touch, for up to 90 days) only if you allow Analytics in the cookie settings, and it is deleted as soon as you turn Analytics off. If you allowed Analytics and sign in with Google, a copy is kept in your browser tab's session storage (s200_signup_touch) while you are at Google and deleted once your sign-in is handled. See Section 7.
2. How We Use Your Information
We use the information we collect for the following purposes:
- Account Management: Create and manage your user account, authenticate your identity, and maintain your session
- Service Delivery: Connect to your social media accounts, upload and store your media files, schedule and publish posts on your behalf, and provide API access
- Token Management: Store and automatically refresh OAuth tokens to maintain active connections to your social media accounts
- Payment Processing: Process subscription payments through Whop, manage your billing status, and enforce plan-based feature limits
- API Rate Limiting: Monitor and enforce API usage limits based on your subscription plan, including daily post counts and API key quotas
- Security and Fraud Prevention: Detect and prevent unauthorized access, abuse, and fraudulent activity
- Service Improvement: Analyze usage patterns to improve the Service, fix issues, and develop new features
- Marketing Measurement: Learn which channels (for example YouTube, Google search or a campaign link) bring new accounts, from the sign-up information described in Section 1.7
- Communication: Send service-related notifications, updates, security alerts, and support messages
- Legal Compliance: Comply with applicable laws, regulations, and legal processes
Emails we send
We send four kinds of email to the address on your account:
- Account and billing notices: plan changes, changes to our Terms, payments, security, and a confirmation when your account is deleted
- Product updates: new features and new networks
- Alerts: for example a post that failed or a connection that expired
- Offers and promotions
You can switch off product updates, alerts and offers at any time in the app (Settings, then Email notifications) or with the Unsubscribe link at the bottom of any email. Account and billing notices are always sent, because we need them to run your account and to tell you about changes to your plan and our Terms.
3. How We Share Your Information
We do not sell, rent, or trade your personal information. We share your data only in the following circumstances:
3.1 Social Media Platforms
When you publish content through the Service, we transmit your media files, captions, and post metadata to the target social media platform(s) via their official APIs. This includes sending data to:
- TikTok (ByteDance Ltd.) -- via TikTok Content Posting API v2
- Instagram (Meta Platforms, Inc.) -- via Facebook Graph API
- Facebook (Meta Platforms, Inc.) -- via Facebook Graph API
- YouTube (Google LLC) -- via YouTube Data API v3
- X (Twitter) (X Corp.) -- via X API v2
- LinkedIn (LinkedIn Corporation/Microsoft) -- via LinkedIn API
- Pinterest (Pinterest, Inc.) -- via Pinterest API
- Threads (Meta Platforms, Inc.) -- via Threads API
- Skool -- via Skool's website API, using your Skool session cookie
Each platform has its own privacy policy governing how they handle data received through their APIs. We encourage you to review their privacy policies (linked in Section 5).
3.2 Payment Processor
Payment information is shared with Whop, Inc. for processing subscription payments. Whop collects and processes payment details directly. We do not have access to your full card details. See the Whop privacy policy at whop.com/privacy.
3.3 Infrastructure Providers
We use Supabase for authentication, database hosting, file storage, and serverless functions. Your data is stored on Supabase-managed infrastructure. See the Supabase privacy policy at supabase.com/privacy.
We use Sentry (Functional Software, Inc.), with data sent to its EU region, for error monitoring, and, only if you allow it in the cookie settings, PostHog (PostHog, Inc.), hosted in the EU, for product analytics and session recordings. What each receives is described in Section 7.
3.4 Legal Requirements
We may disclose your information if required to do so by law or in response to valid requests by public authorities (e.g., a court order or government agency), or if we believe in good faith that disclosure is necessary to protect our rights, protect your safety or the safety of others, investigate fraud, or respond to a legal request.
4. Data Storage and Security
4.1 Where We Store Data
- Account data, social media connection data, post logs, and API logs are stored in a PostgreSQL database hosted by Supabase
- Uploaded media files (images and videos) are stored in Supabase cloud storage
- Payment data is stored by Whop on their secure infrastructure
- OAuth access tokens and refresh tokens are stored in our database alongside connection metadata
- Skool session cookies are stored in the same database, encrypted with AES-256-GCM
4.2 Security Measures
We implement the following security measures to protect your data:
- All data in transit is encrypted using TLS/HTTPS
- Passwords are hashed using industry-standard algorithms and are never stored in plaintext
- Database access is protected by Row Level Security (RLS) policies ensuring users can only access their own data
- API keys are generated using cryptographically secure random generation
- OAuth state parameters are used to prevent CSRF attacks during social media account connection
- Supabase JWT-based authentication protects all authenticated endpoints
While we strive to protect your information, no method of electronic transmission or storage is 100% secure. We cannot guarantee absolute security of your data.
4.3 Data Retention
- Account data is kept while your account exists, and deleted when you delete your account.
- How you found us (recorded once at sign-up, see Section 1.7) is kept with your account and deleted with it.
- Social media connection data (including tokens) is kept until you disconnect the account or delete your account.
- Uploaded media files may be deleted automatically after a retention period, and are deleted when you delete your account. A deleted file can still be served from our content cache for up to an hour.
- Post history and engagement figures are kept while your account exists, and deleted with it.
- API request logs and your sign-in history are kept for at most 90 days, and deleted earlier when you delete your account.
- Internal alerts about the Service can mention your account. They are deleted after 90 days, and your details in them are replaced when you delete your account. Copies in our team chat are cleared once a month when they are older than 90 days.
- Payment records and invoices are kept by Whop. Our copy of your plan and payment details is deleted when you delete your account; an open refund request is kept, without your name or email, until it is processed.
- Support emails you send us, and our replies, are kept for 1 year.
- Our database backups are overwritten within 7 days.
- Logs kept by our hosting and error-monitoring providers expire within 90 days.
- If you turned on Analytics, we delete your data in PostHog by hand within 30 days of your account deletion.
- When you delete your account in the app (Settings, then Delete Account), your data is deleted within minutes; a deletion you ask for by email is done within one month. What we keep after a deletion is listed in 4.4.
4.4 What We Keep After You Delete Your Account
- A deletion record for 3 years: your receipt code, the dates, counts of what was deleted and how your plan ended. It holds no email address, name or IP address.
- For 30 days after the deletion: your internal account number, and the internal numbers of your profiles, connections, API keys and AI app connections. After that, only a one-way code of the account number stays with the deletion record.
- The masked form of your API keys (the first 8 and the last 4 characters) for 90 days, so that requests made later with a deleted key can be found and deleted.
- Your Whop membership and Whop account numbers for 60 days after the deletion, or until 60 days after your paid period ends if that is later, so that a late message from Whop cannot put your details back into our database.
- An open refund request, without your name or email, until it is processed.
- Used coupon codes stay used.
- If another customer referred you, their referral list keeps an entry for you, without your name or email.
- If you sent a data deletion request through Facebook, Instagram or Threads: a record of the request (its code, date, platform and the id Meta sent us) for 1 year, and which connected accounts it removed for 90 days.
If you joined our free plan on Whop, that free membership stays open at Whop until you leave it at whop.com/orders.
Step-by-step instructions are at status200uploads.com/data-deletion.
5. Third-Party Platform Privacy Policies
Our Service integrates with third-party platforms that have their own privacy policies governing how they collect, use, and share data. We strongly encourage you to review these policies:
TikTok (ByteDance Ltd.)
- Privacy Policy: https://www.tiktok.com/legal/privacy-policy
- Developer Privacy Policy: https://developers.tiktok.com/doc/tiktok-api-privacy-policy
Instagram & Facebook (Meta Platforms, Inc.)
- Meta Privacy Policy: https://www.facebook.com/privacy/policy/
- Instagram Privacy Policy: https://privacycenter.instagram.com/policy
- Meta Platform Terms: https://developers.facebook.com/terms/
YouTube & Google (Google LLC)
- Google Privacy Policy: https://policies.google.com/privacy
- YouTube API Services Terms: https://developers.google.com/youtube/terms/api-services-terms-of-service
- Google API User Data Policy: https://developers.google.com/terms/api-services-user-data-policy
You can revoke YouTube/Google access at any time: https://myaccount.google.com/permissions
X / Twitter (X Corp.)
- X Privacy Policy: https://x.com/en/privacy
- X Developer Agreement: https://developer.x.com/en/developer-terms/agreement
- X Developer Policy: https://developer.x.com/en/developer-terms/policy
You can revoke X access at any time via your X account settings under Apps and sessions.
LinkedIn (LinkedIn Corporation/Microsoft)
- LinkedIn Privacy Policy: https://www.linkedin.com/legal/privacy-policy
- LinkedIn API Terms of Use: https://www.linkedin.com/legal/l/api-terms-of-use
- LinkedIn Developer Agreement: https://legal.linkedin.com/developer-agreement
You can revoke LinkedIn access at any time via your LinkedIn account settings under Permitted Services.
Pinterest (Pinterest, Inc.)
- Pinterest Privacy Policy: https://policy.pinterest.com/en/privacy-policy
Threads (Meta Platforms, Inc.)
- Threads Supplemental Privacy Policy: https://help.instagram.com/515230437301944
- Meta Privacy Policy: https://www.facebook.com/privacy/policy
- Threads API Terms: https://developers.facebook.com/docs/threads
You can revoke Threads access at any time via your Threads account settings under Website Permissions.
Skool
- Skool Privacy Policy: https://www.skool.com/legal?t=privacy
- Skool Terms and Conditions: https://www.skool.com/legal?t=terms
You can remove our access at any time by disconnecting Skool in the Service, which deletes the stored session cookie.
Whop (Whop, Inc.)
- Privacy Policy: https://whop.com/privacy
Supabase (Supabase, Inc.)
- Privacy Policy: https://supabase.com/privacy
PostHog (PostHog, Inc.)
- Privacy Policy: https://posthog.com/privacy
Sentry (Functional Software, Inc.)
- Privacy Policy: https://sentry.io/privacy/
6. OAuth Permissions and Data Access
When you connect a social media account, you are redirected to the respective platform's authorization page where you grant specific permissions. We only request the minimum permissions necessary to provide the Service. Skool is the exception: it has no authorization page or scoped permissions (see the last row).
| Platform | Permissions Requested | Purpose |
|---|---|---|
| TikTok | user.info.basic, video.upload, video.publish | Display account info, upload and publish videos/photos |
| instagram_business_basic, instagram_business_content_publish, instagram_business_manage_insights | Display business profile info, publish content, retrieve engagement insights for your posts | |
| pages_manage_posts, pages_read_engagement, pages_show_list, read_insights | Manage page posts, read engagement, list pages, read insights for your posts | |
| YouTube | youtube.upload, youtube.readonly | Upload videos, read channel information |
| X (Twitter) | tweet.read, tweet.write, users.read, offline.access | Read profile info, post tweets, upload media |
| openid, profile, w_member_social | Read profile info (name, picture, email), share posts | |
| boards:read, pins:read, pins:write, user_accounts:read | Board names and IDs, pin creation, basic profile info | |
| Threads | threads_basic, threads_content_publish, threads_manage_insights | Display profile info, publish threads on your behalf, retrieve engagement insights for your posts |
| Skool | No OAuth: the session cookie (auth_token) you paste, which works like a signed-in session | Used only to list your groups and categories and to publish the posts you create or schedule |
Access tokens are automatically refreshed to maintain active connections. You can revoke our access at any time by disconnecting the account within the Service, or by revoking permissions directly through the respective platform's settings.
7. Cookies and Tracking
We sort the cookies and browser storage we use into three categories. Strictly necessary storage is always on. Analytics and session recordings are optional: they stay off until you turn them on, and you choose each one separately. When you first visit, a cookie banner lets you accept all, reject all, or choose per category. Until you allow Analytics, PostHog does not run at all: nothing is recorded, sent or stored. Your choice is kept in your browser for 12 months; after that we ask again.
7.1 Strictly necessary (always on)
Keeps the site working: signing you in, remembering your cookie choice, security checks when you connect an account, the invite code from a referral link, and the email preference links in our emails. The Service cannot work without these, so they do not need your consent. They are listed in 7.5.
Error monitoring with Sentry (no cookies)
We use Sentry, with data sent to its EU region (ingest.de.sentry.io), to find and fix errors. It runs whatever you choose, on the basis of our legitimate interest in a working service, because it sets no cookies, stores nothing in your browser and does not record your screen. It receives only technical error reports: the error, the page address (with login tokens and one-time codes removed), the recent technical steps before it (such as which button was clicked and which requests ran), and your browser and device type, plus page load timings for a sample of visits. If you are signed in, a report includes your account ID (not your name or email), so we can find the account the problem happened in.
7.2 Analytics with PostHog (optional, off until you turn it on)
If you turn on Analytics, we use PostHog, hosted in the EU (eu.i.posthog.com), to see how the Service is used and make it better:
- The pages you visit and the buttons and links you click
- Browser, device type, screen size and referring website
- Your IP address, which PostHog uses to estimate your approximate location (country and city)
- If you are signed in, your account ID, name and email, so this is linked to your account
- A PostHog cookie and local storage entries that recognise your browser on later visits
Login tokens and one-time codes are removed from web addresses before anything is sent.
With Analytics on, we also keep in your browser, for up to 90 days, how you first found us (s200_first_touch: the campaign tags, the referring website's domain and the first page you opened), so a sign-up on a later visit is counted for the right channel. This is our own storage, not PostHog's. It leaves your browser only if you sign up (see 1.7), and it is deleted as soon as you turn Analytics off.
7.3 Session recordings with PostHog (optional, off until you turn it on)
If you also turn on Session recordings, PostHog records replays of your visits: the screen, your mouse movements and clicks. Everything you type is masked in recordings, and secrets shown on screen, such as your API keys and your Skool cookie, are left out of recordings and click data. Recordings can only be on while Analytics is on: they use the same PostHog storage to know which visit a recording belongs to, so turning Analytics off turns them off too.
7.4 No advertising cookies or tracking pixels
We use no advertising cookies and no tracking pixels, and we share nothing with advertising networks. We do not sell data. The only marketing measurement is our own record of how you found us (see 1.7), which your browser keeps between visits only with your consent (7.2).
7.5 The cookies and storage we use
The same list as in the cookie settings. A name in <angle brackets> stands for a value filled in at run time, such as our PostHog project key or a one-time sign-in code.
Strictly necessaryalways on
sb-app-auth-tokenlocalStorageKeeps you signed in: your login session.
- Provider
- Supabase (our sign-in service)
- Lasts
- Until you sign out (it renews itself while you use the app)
s200_cookie_consentlocalStorageRemembers your cookie choices and the date you made them.
- Provider
- Status 200 Uploads
- Lasts
- 12 months, then we ask again
tiktok_oauth_statelocalStorageSecurity check when you connect TikTok: proves the answer belongs to the sign-in you started.
- Provider
- Status 200 Uploads
- Lasts
- Deleted when the connection finishes
linkedin_oauth_exchange_<code>, pinterest_oauth_exchange_<code>sessionStorageSecurity check when you connect LinkedIn or Pinterest: a one-time sign-in code is used only once.
- Provider
- Status 200 Uploads
- Lasts
- Until the sign-in window closes
tiktok_profile_idlocalStorage and sessionStorageWhich of your profiles a TikTok connection is for.
- Provider
- Status 200 Uploads
- Lasts
- Until the tab closes (sessionStorage); replaced at your next TikTok connection (localStorage)
affiliate_reflocalStorageThe invite code from a referral link (?ref= or ?a=), so whoever invited you gets the credit when you sign up.
- Provider
- Status 200 Uploads
- Lasts
- Until you clear this site’s data in your browser
referral_invite_toast_shown, referral_invite_dismissedsessionStorageShows the “You were invited by” notice once, and keeps it closed after you dismiss it.
- Provider
- Status 200 Uploads
- Lasts
- Until the tab closes
tus::s200-<account id>-<file>::<id>localStorageLets a large upload continue where it stopped if the connection drops.
- Provider
- Status 200 Uploads
- Lasts
- Deleted when the upload completes
current_workspace_idlocalStorageRemembers the workspace you last opened in the dashboard.
- Provider
- Status 200 Uploads
- Lasts
- Until you clear this site’s data in your browser
sidebar_auto_hidelocalStorageRemembers your dashboard sidebar setting.
- Provider
- Status 200 Uploads
- Lasts
- Until you clear this site’s data in your browser
The email preference and unsubscribe links in our emails work without storing anything in your browser.
Analyticsoptional
ph_<project key>_posthogCookie, localStorage and sessionStorageRecognises your browser on later visits: a random ID, the current visit and, once you sign in, your account.
- Provider
- PostHog (EU)
- Lasts
- Cookie: 1 year; sessionStorage: until the tab closes. All deleted as soon as you turn Analytics off
ph_<project key>_posthog__flagslocalStoragePostHog’s settings for this site (feature flags), kept so pages do not wait for them.
- Provider
- PostHog (EU)
- Lasts
- Until you turn Analytics off
__ph_opt_in_out_<project key>localStorageRemembers that you allowed analytics in this browser.
- Provider
- PostHog (EU)
- Lasts
- Until you turn Analytics off
ph_<project key>_window_id, ph_<project key>_primary_window_existssessionStorageTells your browser tabs apart within one visit.
- Provider
- PostHog (EU)
- Lasts
- Until the tab closes
ph_<project key>_session_registered_propertiessessionStorageWhich details PostHog adds to every event in the current visit.
- Provider
- PostHog (EU)
- Lasts
- Until the tab closes
s200_first_touchlocalStorageHow you first found us: the link’s campaign tags (utm_*), the referring website’s domain, the first page you opened and when, so a sign-up on a later visit is counted for the right channel. No full web addresses, and of ad click IDs only the name (such as “gclid”). It leaves your browser only if you sign up.
- Provider
- Status 200 Uploads
- Lasts
- 90 days; deleted as soon as you turn Analytics off
s200_signup_touchsessionStorageOnly during a Google sign-in, and only with Analytics allowed: keeps how you found us (campaign tags, the referring website’s domain, the first page you opened and when) while you are at Google, so a new account is counted for the right channel. No full web addresses, and of ad click IDs only the name (such as “gclid”).
- Provider
- Status 200 Uploads
- Lasts
- Deleted once your sign-in is handled; at the latest when the tab closes (ignored after 1 hour)
Session recordingsoptional
Recordings store nothing of their own: they use the Analytics storage above to know which visit a recording belongs to. That is why they need Analytics.
Changing your choice: use the "Cookie settings" link in the website footer or the button below, or in the app go to Settings, then Cookie settings. You can switch each category on or off. If you turn Analytics off after allowing it, PostHog stops at once and its cookie and local storage are deleted from your browser, and so is s200_first_touch; turning Session recordings off stops recording at once.
8. Your Privacy Rights
Depending on your location, you may have the following rights regarding your personal data:
Right to Access
You may request a copy of the personal data we hold about you, including account information, connected social media accounts, stored media, and usage logs.
Right to Rectification
You may request that we correct any inaccurate or incomplete personal data. You can also update your account information directly through the Service.
Right to Erasure (Right to be Forgotten)
You may request the deletion of your personal data. This includes your login and account, your stored media, connected social media tokens, post history, API keys and AI app (connector) access. You can delete your account yourself in the app (Settings, then Delete Account). What we keep after a deletion is listed in Section 4.4. Step-by-step instructions, including what happens when you remove the app from your Facebook, Instagram or Threads settings, are at status200uploads.com/data-deletion.
Right to Data Portability
You may request a machine-readable copy of your personal data in a structured, commonly used format.
Right to Restrict Processing
You may request that we limit the processing of your personal data in certain circumstances, such as when you contest the accuracy of the data.
Right to Object
You may object to the processing of your personal data for certain purposes, such as direct marketing.
Right to Withdraw Consent
Where we rely on consent for data processing, you may withdraw consent at any time. You can disconnect social media accounts, delete your uploaded media, or delete your account entirely. You can switch analytics and session recordings off with the "Cookie settings" link (see Section 7).
To exercise any of these rights, please contact us at info@status200uploads.com. We will respond to your request within one month.
9. GDPR Compliance (European Economic Area)
If you are located in the European Economic Area (EEA), the United Kingdom, or Switzerland, the following applies:
- Legal Basis: We process your data based on: (a) your consent (connecting social media accounts, uploading content, analytics and session recording cookies); (b) contractual necessity (providing the Service you subscribed to); (c) legitimate interests (security, fraud prevention, service improvement, and learning which channels bring us new accounts, see Section 1.7); and (d) legal obligations
- Data Transfers: Your data may be transferred to and processed in countries outside the EEA where our service providers operate. We ensure appropriate safeguards are in place for such transfers
- Supervisory Authority: You have the right to lodge a complaint with your local data protection supervisory authority
10. CCPA Compliance (California Residents)
If you are a California resident, the California Consumer Privacy Act (CCPA) provides you with additional rights:
- Right to Know: You can request disclosure of the categories and specific pieces of personal information we have collected about you
- Right to Delete: You can request deletion of your personal information, subject to certain exceptions
- Right to Non-Discrimination: We will not discriminate against you for exercising your CCPA rights
- No Sale of Personal Information: We do not sell personal information to third parties as defined by the CCPA
11. Children's Privacy
The Service is not intended for use by individuals under the age of 18 (or the age of legal majority in your jurisdiction). We do not knowingly collect personal information from children. If we become aware that we have collected personal data from a person under 18, we will take steps to delete that information promptly. If you believe a child has provided us with personal data, please contact us at info@status200uploads.com.
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes, we will:
- Update the "Effective Date" and "Last Updated" date at the top of this page
- Post a prominent notice on the Service
- Send an email notification to the address associated with your account for significant changes
Your continued use of the Service after any changes to this Privacy Policy constitutes your acceptance of the revised policy.
13. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:
status: 200 | uploads -- Privacy Inquiries
Email: info@status200uploads.com
General Support: info@status200uploads.com
Website: status200uploads.com
We aim to respond to all privacy-related inquiries within one month.