What we collect, why, and how to delete it.

What ReBrandOS stores, how we use data from the accounts you connect, and how to get a copy or have it deleted.

Last updated:: October 12, 2026
Operated by:: Fessburn, LLC

Who controls your data

ReBrandOS is operated by Fessburn, LLC, a Delaware limited liability company, 651 N Broad St, Suite 201, Middletown, DE 19709, United States (Polish VAT number (NIP) 7812056448), which is the controller for the personal data described here. Because ReBrandOS offers its service to people in the European Union, the General Data Protection Regulation applies. You can ask for access, correction, export, restriction, objection or deletion, and you can complain to the data protection authority where you live or work, or UODO (Urząd Ochrony Danych Osobowych) in Poland.

Stripe processes payments and is a separate processor for the payment details you enter with it; Fessburn, LLC never receives or stores your full card details.

Analytics and attribution stay off until you opt in. Only what is strictly necessary to serve a page you asked for runs without consent: session, security, load_balancing.

Information we collect and how it is stored

Information we collect

Account and brand details required to authenticate users and manage access; connected-platform details needed to import destinations, maintain integrations, and route activity; and content, media, publish jobs, receipts, inbox, and reporting data created through product workflows.

Storage, sharing & access

OAuth tokens, scopes, account metadata, publish jobs, and receipts are stored server-side with restricted access. Connected-platform data is transmitted to the platform you selected only to perform the connection, publishing, status, and troubleshooting actions you request.

Subprocessors and retention

Named subprocessors

Named subprocessors and connected platform providers may include Google and YouTube, Meta, TikTok, LinkedIn, X, Stripe for billing, SendGrid for transactional email, OpenAI, Anthropic, and DeepSeek for AI generation when configured, and the VPS or hosting provider that runs ReBrandOS.

Retention timelines

Google, YouTube, and other OAuth tokens are deleted immediately after disconnect, account deletion, or detected provider revocation. Connected-account metadata and uploaded video or post metadata are deleted within 30 days after disconnect, account closure, or a verified deletion request unless retention is legally required or permitted.

Logs and requests

Request traces use route templates rather than full URLs, omit query values and user identity, and are retained for up to 7 days. Other operational, security, and application logs that may reference connected-account actions are normally retained for up to 90 days, then purged or de-identified unless needed for security, abuse prevention, legal compliance, or dispute handling. Verified deletion requests are completed within 30 days through hello@rebrandos.com.

Google user data

How Google user data is shared

When you sign up or sign in with Google, ReBrandOS requests openid, email, and profile only to authenticate you and identify your account. When you connect YouTube, ReBrandOS requests https://www.googleapis.com/auth/youtube.upload to upload approved videos you submit and https://www.googleapis.com/auth/youtube.readonly to read your channel’s name, identifier, and avatar so we can correctly display the connected channel. ReBrandOS does not sell Google user data, transfer it to advertising networks or data brokers, use it for retargeting, or use it to train general-purpose AI models. ReBrandOS shares, transfers, or discloses Google user data only with the Google or YouTube APIs needed to perform actions you request, with infrastructure and security service providers that host, store, monitor, or protect the service, with support personnel when you request troubleshooting, or when required for legal, security, fraud-prevention, abuse-prevention, or compliance reasons.

Data protection mechanisms

Google OAuth tokens and connected-account data are stored server-side and protected with transport encryption, restricted production access, credential-broker storage, least-privilege access controls, audit logging, operational monitoring, and revocation/deletion workflows. Human access is limited to personnel who need it for support, security, legal compliance, abuse prevention, or user-approved troubleshooting.

Limited Use and revocation

ReBrandOS use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including Limited Use requirements. You can revoke ReBrandOS access from your Google Account permissions at https://security.google.com/settings/security/permissions or https://myaccount.google.com/permissions, and you may request access, export, or deletion through hello@rebrandos.com.

Connected platform data

Meta · Facebook, Instagram, Threads

When you connect Meta-powered destinations, ReBrandOS may request approved permissions to read pages, publish content, and manage comments or messages where enabled. It accesses page and account identifiers, granted scopes, and destination status, and uses Meta data only to import destinations you authorize, publish or schedule content, and troubleshoot delivery.

Google · YouTube

When you sign up or sign in with Google, ReBrandOS requests openid, email, and profile only to authenticate you and identify your account. When you connect YouTube, ReBrandOS requests https://www.googleapis.com/auth/youtube.upload to upload approved videos you submit and https://www.googleapis.com/auth/youtube.readonly to read your channel’s name, identifier, and avatar so we can correctly display and identify the connected channel. Google and YouTube data may include your Google account identifier, email address, profile name, YouTube channel identifiers, channel title and avatar, video metadata you submit, upload status, processing status, and delivery receipts, used only to authenticate access, connect the channel, display the channel, upload content you request, show status, and troubleshoot delivery.

TikTok

When you connect TikTok, ReBrandOS may request permissions such as basic profile, video list, upload, and publish, depending on the access approved for your account. It uses TikTok data only to connect the account, publish content you submit, reconcile public video status, and show analytics.

When you connect LinkedIn, ReBrandOS may request approved profile and organization permissions, and uses the data only to connect the authorized profile or organization, publish or schedule content you submit, show delivery history, and troubleshoot.

X · Pinterest · others

For X, Pinterest, and other authorized integrations, ReBrandOS requests only the OAuth tokens and scopes needed to connect the account, publish or schedule content you submit, show status and history, and troubleshoot delivery.

Want a copy of your data, or want it deleted? We’ll help. Make a data request.