Sidebox

Privacy

Last updated 14 October 2026

Website previews before signup

When you preview a website, Sidebox reads one public page to suggest project details. We do not save the submitted address or preview content on our servers before signup. We keep salted, hashed IP rate-limit counters to prevent abuse. Your reviewed draft stays in your browser for up to 24 hours, or in memory when browser storage is unavailable, and is cleared after saving, discarding, or expiry. Only a local draft identifier is carried through sign-in; website details are not added to auth URLs or analytics. Site icons may be loaded from the website for preview, and selected icons are imported into your project after authentication and email verification.

MCP connection

If you connect an AI assistant through Sidebox MCP, you authorize that assistant to read all current and future owned projects, including archived projects, saved private context, product copy, links, and cached revenue, traffic, deployments, activity, and SEO results within your plan's history allowances. This includes cached Search Console information when connected. Sidebox shares only the data requested through the approved read-only tools; the connection does not refresh providers, run paid research, or edit your workspace.

The external assistant provider processes the information it receives under its own data policies. Sidebox does not provide an AI model service or use these connections to train models. You can revoke future access in Account settings under MCP connection; revocation cannot remove information already received or retained by that external application. Sidebox records the approved client, permission, approval date, last-used time, and bounded usage counters. Tool arguments and results are not included in operational logs.

Google sign-in

If you choose to sign in with Google, Sidebox accesses your Google account identifier, email address, name, and profile picture through the basic identity, email, and profile permissions. We store these details to create or link your Sidebox account, authenticate you, and display your account profile. Google sign-in does not grant access to your Search Console properties, Gmail, Drive, or Calendar.

Google Search Console data

Connecting Google Search Console is a separate, optional authorization. Sidebox requests read-only Search Console access and your Google account identifier and email address to identify the connected account. We access the list of properties you can use and their permission levels so you can select a property to connect to a Sidebox project.

For properties you map to projects, Sidebox accesses and stores bounded search-performance summaries: clicks, impressions, click-through rate, average search position, daily metrics, top search queries and pages, device and country breakdowns, and sitemap information when available. We use this data to show project dashboards, portfolio summaries, trends, connection status, and activity within your workspace, search-click summaries in email digests if you enable them, and read-only information requested by an AI assistant you explicitly connect. Sidebox cannot modify your Search Console properties or submit changes to Google on your behalf.

Use, storage, and sharing of Google data

Google identity information, connection metadata, and Search Console snapshots and metric history are stored in Sidebox's database, operated by Neon, and processed by our application infrastructure on Cloudflare. Data is transmitted over HTTPS. Google authorization tokens are stored encrypted and used by the server to authenticate requests and refresh authorized access. The browser does not receive your Search Console tokens. If you enable email digests, our transactional email provider also processes the search-click summaries included in those messages to deliver them to you.

We use Google data only to provide the account and workspace features described above. We do not sell Google data, use it for advertising, provide it to data brokers, or use it to train generalized AI or machine-learning models. Search Console data is not sent to product analytics. Google data may be processed by infrastructure providers to operate these features, or disclosed when necessary for security or to comply with applicable law. Human access is limited to your permission to investigate a specific support issue, necessary security investigations, or legal requirements.

Sidebox's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Google access, retention, and deletion

Google sign-in profile information is retained while your Sidebox account exists. Search Console credentials and cached data are retained while the connection exists; metric history is limited by your plan's history window. You can disconnect Search Console from Connections in Sidebox. Disconnecting stops future collection and deletes the connection's stored credentials, property mappings, snapshots, and metric history. Sidebox also attempts to revoke the Google authorization; if that attempt fails, local deletion still proceeds.

You can revoke Sidebox's access at any time in your Google Account's third-party connections settings. Revoking access at Google stops future authorized requests, but does not by itself delete data already stored in Sidebox. Disconnect the connection in Sidebox to remove its cached data. Activity entries describing earlier connection events may remain until you delete your Sidebox account.

To remove your stored Google sign-in information and remaining account-owned Google data, delete your Sidebox account in Account Settings. Account deletion removes those records from the active database. Backup copies may persist under the database provider's backup retention; Sidebox uses a deletion ledger to reapply confirmed account deletions after a backup restoration. You can also request access, correction, or deletion by contacting contact@sidebox.dev. Deleting a Sidebox account does not delete your Google account or Search Console properties.

Information Sidebox stores

Sidebox stores account and workspace information you provide, including project names, descriptions, links, brand references, and private assets. None of it is included in product analytics.

Connected providers supply bounded, read-only snapshots needed for the features you use. Sidebox does not retain payment-customer personal information from Stripe or Polar in its product snapshots.

Connected services and credentials

Provider connections are read-only. Sidebox requests narrow permissions and encrypts stored provider credentials. Disconnecting stops future refreshes; cached provider data follows the product's documented deletion behavior.

Service providers that process information for Sidebox include Cloudflare, Neon, Polar, transactional email providers, Sentry (error reports from the web app, with identifiers, query strings, and contact details removed), PostHog (product analytics, only with your consent), and any provider you choose to connect, including GitHub, Vercel, Google Search Console, PostHog, Stripe, and Cloudflare project connections.

Product analytics and cookies

With your permission, Sidebox uses PostHog to understand how the product is used. Nothing is loaded or stored for analytics until you choose Allow in the consent banner. If you decline, or your browser sends a Global Privacy Control signal, analytics stay off.

When allowed, Sidebox records page views as page types (for example, "a project's Revenue page", never the address itself) and a fixed list of actions: account creation and sign-in (including which sign-in method was used), checkout started, project created or imported, link added, asset uploaded, provider connected or mapped, the kind of external service opened, command palette use, date range changes, and digest preference changes. Signed-in events are linked to a random account identifier, never your name or email address.

Events never include project names, URLs, or descriptions, link labels, filenames, search queries, payment records, credentials, asset contents, or data from connected providers. Session recording and automatic click capture are off. PostHog stores a cookie and local storage entry to recognize your browser between visits.

You can change your choice at any time in Account → Privacy, or with Privacy choices in the site footer. Withdrawing consent stops collection and deletes PostHog's cookie and local storage from your browser.

Retention and your choices

Workspace information is retained while your account is active, except uploaded files in never-paid Trial accounts, which expire 30 days after the Trial ends. Project details, links and saved context remain. You can delete your account from Account Settings. Account deletion removes account-owned database records and schedules private object cleanup; object cleanup runs every three hours and may require retries.

You can download individual private assets. For requests to access, correct, delete, or receive your personal data, contact contact@sidebox.dev. There is no self-service bulk export. See Data Handling for more detail.

How we use your information

We use account and workspace information to provide the service, manage subscriptions, and respond to support requests. Where applicable, we rely on performing our agreement with you, legal obligations, and legitimate interests in keeping the service secure. Optional product analytics relies on your consent.

Our service providers may process information outside your country, including outside the European Economic Area. Where required, appropriate safeguards must apply to those transfers. You can contact us about your privacy rights or complain to your local data protection authority.

Contact

Privacy questions: contact@sidebox.dev.

Contact support · contact@sidebox.dev