Privacy Policy

We collect information you provide directly, including:

• Account information — name, email address, profile photo, and credentials when you create an account or sign in via OAuth (e.g., Google).
• Startup and business data — company names, product descriptions, brand assets, target markets, and other inputs you submit when using the platform.
• Payment information — billing details processed securely by our payment provider (Stripe). We do not store raw card numbers.
• Third-party platform credentials — for a limited set of platforms that do not offer a public OAuth flow or self-serve API key (currently: Reddit), you may choose to connect an account by providing your username and password directly. This is opt-in per platform: we show you an explicit consent screen describing what will be stored before you connect, and we record a hash of the exact consent text you agreed to along with the date. Credentials collected this way are encrypted at rest (AES-256-GCM) under a dedicated encryption key that is isolated from our other secrets, are never displayed in plaintext to Probe staff, and are only decrypted transiently, in memory, by an automated worker process to perform the login or posting action you authorized — never for any other purpose. Every decrypt operation is written to an append-only audit log. You can revoke a connected platform credential at any time from your account settings, which deletes the stored credential. Where a platform later adds a supported OAuth or API-key integration, we intend to migrate connected accounts to that flow and remove the stored password.
• Communications — messages, feedback, and support requests you send to us.

When you use the Services we automatically collect:

• Usage data — pages visited, features used, actions taken, session duration, and similar interaction logs.
• Device and connection data — IP address, browser type, operating system, device identifiers, and referring URL.
• Cookies and similar technologies — see our Cookie Policy.

We may receive information about you from third-party services you connect to Probe (e.g., social media platforms, advertising networks, CRMs) when you authorize such integrations, as well as from analytics and identity providers.

Two different categories, held separately:

• Tokens and API keys. For platforms that offer OAuth or a scoped API key, we store the access token, refresh token, or key you authorize, together with non-secret metadata such as the service name, the external account name, and the connection date. This is the path used for Vercel, GitHub, Supabase, Stripe, Google, Anthropic, Intercom, and PostHog.
• Usernames and passwords. For the narrow set of platforms that offer neither, and only where you have separately consented on a per-platform basis, we store the username and password you enter. Only platforms on an explicit code-level allowlist are eligible. That allowlist currently contains Reddit and nothing else, and adding to it requires a code change rather than a configuration setting.

We also store a record of your acceptance of the delegation terms: the date and time, the version of the terms in force, and a cryptographic hash of the exact wording you were shown. For a per-platform password connection we store the same kind of record for that platform's own consent screen.

Both categories are encrypted at rest with AES-256-GCM. Passwords are encrypted under a dedicated key that is isolated from the key protecting tokens and from our other secrets, and are held in a separate database table whose row-level security posture denies all access by default, reachable only by server-side infrastructure and never by a client application. No Probe employee can read a stored credential in plaintext through the product, and no interface exists that returns one.

A stored credential is decrypted only in memory, only by an automated server-side process, and only to carry out an action you authorized. A stored Google connection may additionally be used to complete a "Continue with Google" sign-in on a third-party platform on your behalf; in that case we never see or store that platform's own password. Every decryption of a stored password is written to an append-only audit log recording the account, the platform, the action, and the outcome. That log is structurally incapable of holding a credential value, because it has no field for one. Credentials are never used to train models, never shared with other users, and never used for any purpose other than the action you authorized.

Access is limited to the server-side processes that perform your authorized actions. Support and engineering staff can see that a connection exists and its non-secret metadata, and can see the audit log, but cannot retrieve the credential itself. Credentials are not shared with any third party other than the platform the credential is for, and are not disclosed in a data export (see Section 6).

We hold a credential for as long as the connection is active. We delete it when you disconnect that platform, when you withdraw the delegation authority, or when you delete your account. Deletion is immediate rather than queued, and removes the stored value rather than marking it inactive. The audit-log entries and the acceptance records survive deletion of the credential, because they are the evidence of what was authorized and what was done; they contain no credential values. Where a platform later adds a supported OAuth or API-key integration, we intend to migrate connected accounts to that flow and delete the stored password.

Deleting a stored credential does not close the account it belongs to, and does not undo actions already taken. Accounts Probe created in your name remain yours. If you want one closed, close it with that platform directly.

Storing a credential that unlocks an account outside Probe carries risk that encryption reduces but does not remove. A compromise of our systems could expose those credentials and the accounts they unlock. We recommend a unique password for any account you connect, and we recommend using a token-based connection wherever the platform offers one.