Docs

Data, privacy & security

How CrunchJunkie connects to your data, protects it, and lets you take it back.

Read-only, scoped, revocable access

Every platform connection uses OAuth — the same standard behind "Continue with Google". You authorize on the provider's own screen and CrunchJunkie receives a scoped, read-only token; we never see or store your platform password, and we never make changes to your campaigns. The access is revocable at any time, from either CrunchJunkie or the provider, and revoking it immediately cuts off our ability to read that source. Because the grant is read-only and scoped to just the accounts you select, the access we hold is the minimum needed to build your reports — nothing more.

How tokens and keys are stored

The OAuth tokens that let us sync your data — and any AI provider keys you bring for AI Visibility — are encrypted in our database with application-level AES-256-GCM, on top of our infrastructure provider's own at-rest disk encryption, and they only ever travel over encrypted (TLS) connections. The same application-level encryption protects your sign-in tokens and, if you use two-factor authentication, your 2FA secret. They're used solely to sync your data or run your own scans — never shared, and never used for anything else. This is also why a provider-side change — a password reset, a removed permission — can invalidate a token: the security model is working as intended. When that happens you'll see a reconnect prompt in Needs attention rather than silent failures.

Account security and 2FA

Protect your own login under Settings → Sign-in and security by turning on two-factor authentication. Scan the QR code with any authenticator app — Google Authenticator, 1Password, Authy — and confirm the six-digit code to pair it. CrunchJunkie then issues one-time recovery codes; save them somewhere safe, as they're shown only once and let you back in if you lose your authenticator. With 2FA on, a fresh code is required at every sign-in, so your workspace stays protected even if your password is ever compromised. Combined with role-based access for team members, it keeps control of your data in the right hands. As a further guard against password-guessing, an account is temporarily locked after several wrong passwords or two-factor codes and unlocks automatically after a short cool-off — so a brute-force attempt is stopped without you having to do anything. You change your password under Settings → Sign-in and security too: enter the current one and the new one twice, plus a code from your authenticator if 2FA is on. Every other device is signed out within a minute, the browser you're using stays signed in, and we email you a confirmation with a link to reset the password in case the change wasn't yours. If you have only ever signed in with Google, there is no password to change yet: use Forgot password on the sign-in page to set one.

Passkeys

A passkey lets you sign in with your fingerprint, your face or your device's PIN instead of typing a code. Add one under Settings → Sign-in and security: give it a name, such as the device it lives on, and follow your browser's prompt. You can add up to 10, for example your laptop, your phone and a hardware security key, and remove each one on its own. After your password, a passkey counts as two-factor authentication, just like the authenticator app: the sign-in offers "Use a passkey" as its second step, and a workspace that requires two-factor authentication accepts it. You can also choose "Sign in with a passkey" on the sign-in page and skip the password. Then the passkey has to confirm it's you on the device, with your fingerprint, face or PIN; a security key that only needs a touch works after your password, not instead of it, and it can't confirm a change to your two-factor authentication either: use a code from your authenticator app or a recovery code for that. Most security keys can confirm changes too once they have a PIN, which you set in your browser's or your system's security-key settings; if such a key is your only second factor and you have no recovery codes left, set a PIN on it or contact support. If a passkey is your first second factor, CrunchJunkie shows you recovery codes once, as when you turn on the authenticator app: they get you back in if you lose your devices. Turning on the authenticator app later gives you a fresh set, and the earlier codes stop working. Removing your last passkey while the authenticator app is off turns two-factor authentication off and removes the recovery codes. Adding or removing a passkey needs a sign-in in the last 15 minutes and, once you have a second factor, a confirmation with it: a passkey, a code from your authenticator app or a recovery code. Both are recorded in our audit log. Passkeys work at app.crunchjunkie.io, the address they are made for. If your workspace requires SSO, sign in with SSO: a passkey doesn't replace it.

Requiring 2FA for your whole team

Workspace owners can make two-factor authentication mandatory for everyone. Turn on "Require two-factor authentication" under Settings → Team, and any member who hasn't set up 2FA is prompted to do so before they can keep using the workspace — no one slips through with a password alone. You'll need your own 2FA turned on first, so enforcing it can never lock you out of the setting. Until a member turns 2FA on, CrunchJunkie stays closed to them: the app sends them to the setup, requests to the API are refused, and AI assistants connected through the CrunchJunkie connector are refused too. Setting 2FA up, signing out and public share links keep working. When you switch the requirement on, members without 2FA are signed out the next time they use the app and taken to the setup after signing in again; turning 2FA on lifts the block straight away. If any workspace you belong to requires two-factor authentication, you need it to use CrunchJunkie, in every workspace you belong to: one sign-in reaches all of them (the AI connector can switch between them too), so the strictest requirement applies to the whole account. REST API keys keep working, and only members who meet the requirement can create new ones. Members who still need to enable it get a reminder by email until they do, so you don't have to chase anyone.

Required for owners and admins

Workspace owners and admins who sign in with a password need two-factor authentication: a passkey (Touch ID, Face ID or Windows Hello) or an authenticator app. Owners and admins can see all of a workspace's client data and connect ad accounts, and a password alone is the weakest link. If you sign in only with Google or single sign-on (SSO), there is no password on your account and your provider's own two-factor rules apply instead. Members and read-only seats can turn 2FA on whenever they like, and an owner can still require it for the whole team. When the requirement first applies to you, you get 14 days: an email tells you the date, a banner in the app shows it, and a second email reminds you three days before. From that date, CrunchJunkie asks you to set it up when you next open the app, and the API and AI assistants connected through the CrunchJunkie connector wait until you have; an open session ends once and you sign in again. Nothing is deleted or locked away, and REST API keys keep working. Someone who becomes an owner or admin later gets their own 14 days. While two-factor authentication is required of you, you can't turn off your last second factor: to switch methods, add the new passkey or authenticator app first, then remove the old one.

Security log

Settings → Sign-in and security has a Security log: sign-ins, failed sign-ins and changes to your login from the last 90 days, newest first. It lists when you signed in and how (password, passkey, Google or SSO), wrong passwords and codes, a lockout after too many wrong attempts, the authenticator app or a passkey turned on or removed, a recovery code used, and changes to your password and sign-in email. Each entry shows the network it came from, shortened (for example 203.0.113.0, never your full IP address), and the browser and system ("Firefox on Windows"). A failed sign-in with an address that has no account is never recorded. If you are the workspace's owner or an admin, the log also shows the workspace's own security changes, with who made them: members invited, joined, removed or given another role, "Require two-factor authentication" and "Require SSO" switched on or off, SSO settings, API keys created or revoked, AI assistants connected through the CrunchJunkie connector and their permissions, and data exports. A read-only seat, and a seat limited to some clients, sees only their own entries. The network and browser of a colleague's entry are never shown. Download CSV gives you everything you can see from the last 12 months. The log is kept for 12 months and then deleted; your entries are also in your personal data export (Settings → Export your data → Download my personal data).

Payments and PCI

Billing is handled securely by Stripe, a PCI-compliant payments provider. CrunchJunkie never stores full card details — they go straight to Stripe — and your invoices and receipts are available under Settings → Plan and billing → Invoices, with your company billing details and VAT ID applied. Keeping payment data off our systems and with a specialist provider is the safest place for it.

Data deletion and GDPR

Your data stays yours. Export your entire workspace whenever you like from Settings → Export your data — every client, project, tracked prompt, competitor, goal, report and your full AI-visibility history, as portable JSON plus a CSV of the metric history. Every CSV CrunchJunkie writes opens in Excel and Google Sheets; a text cell that starts like a formula (with =, +, - or @) begins with an apostrophe so it never runs, and numbers stay numbers. The workspace owner and admins can download it; an admin's JSON leaves out the team member list and the email address on each Google Ads change, which the owner's file has; owners and admins download the member list under Settings → Team. Members and read-only seats download their own personal data on the same page. Secrets — API keys, OAuth tokens, passwords — are never included. If you decide to leave, request account deletion from Settings → Workspace. After deletion, account and workspace data is removed or anonymised within 30 days; billing records are retained only as long as the law requires. Revoking an integration likewise stops any further reading of that source. The principle throughout is straightforward: least-privilege access, encryption at rest, and a clean exit whenever you want one — no proprietary lock-in. Prefer a hand? Email hello@crunchjunkie.io and a real person will help.

Reporting a security issue

Found something that looks like a security vulnerability? Email hello@crunchjunkie.io (or security@crunchjunkie.io) with the details and steps to reproduce, and we'll acknowledge it within two business days — please don't post it publicly. Behind the scenes we scan our dependencies and our own code continuously and patch high-severity issues quickly, so a responsible report reaches a team that acts on it.