Privacy

What GetLogOff stores about your workspace, and what actually happens to it, described the way the product actually works today.

What we store

• Your posts: captions, first comments, notes, edit choices like trims and text overlays, and their scheduled and published times.
• The files behind them: what you upload, plus the versions GetLogOff renders (covers, subtitles, mixed audio).
• Connection tokens: when you connect an Instagram account, Facebook Page, or YouTube channel, we store the access token that network issues so the worker can publish on your behalf.
• Performance numbers the connected network reports back for posts GetLogOff itself published (reach, plays, likes, comments, shares, saves).
• Account and workspace info: your login email, your role, and the workspace(s) you belong to.

How it is protected

Connection tokens, and any AI key you add, are encrypted at rest and decrypted only for the one call that needs them; once saved they are never shown back to you, and never written to a log. Passwords are hashed, never stored as plain text. Your workspace's data is scoped to your workspace: every query for it carries a check that refuses another client's workspace. The agency that operates GetLogOff for you can see the workspaces it manages, the same way any agency sees the accounts it runs for a client; that is by design, not a leak.

What each connection is used for

Meta's own review process asks that this be stated plainly, so here it is, permission by permission:

• Instagram account info identifies which Instagram professional account a connection belongs to, so your workspace can label it.
• Instagram publishing is what lets an approved post actually reach that Instagram account.
• Facebook Page list finds which Facebook Pages you administer, so you can pick the one that should publish.
• Instagram insights reads how your own published posts performed, so the Insights page can show real numbers. Nothing here estimates a figure; a number we could not fetch is shown as unavailable rather than guessed.
• Facebook Page engagement reads how your own published Reels performed, for that same Insights page.
• Facebook Page publishing is what lets an approved Reel actually reach your connected Page.
• YouTube upload is what lets an approved Short actually reach your connected channel.
• YouTube read-only reads the view and like counts of the videos GetLogOff published for you, again for Insights. It is never used to browse, collect, or analyse anyone else's videos.

Google user data, and the Limited Use promise

GetLogOff's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Plainly, and with no exceptions:

• Your YouTube data is used only to publish the posts you approved and to show you their performance inside GetLogOff.
• It is never sold and never transferred for advertising. It is never used to build a profile or to train any AI model.
• No human at GetLogOff reads it, except where you have asked us for support in writing, or where the law requires it.
• Disconnect a channel and its stored token is deleted. See data deletion for removing everything else.

Where your content goes

• When a post publishes, it goes to the network you connected it to (Instagram, Facebook, or YouTube), exactly as if you had posted it yourself from that network's own app.
• If your workspace turns on the in-app Assistant, it runs on an AI key you provide (Anthropic or OpenAI). Your prompts and drafts go only to the provider you chose, on your own key, never a shared company account.
• If your workspace generates background music for a post, the mood or prompt text is sent to ElevenLabs, our music-generation vendor, to make that track.
• Account email (password resets, failure alerts, the weekly digest) is sent through Resend, our email delivery provider.
• If your workspace is on a paid plan, card details go straight to Stripe's own hosted checkout page; they never reach GetLogOff's server.

Deleting your data

See the data deletion page for exactly how to ask and what happens.

Questions