Security at AtlasClicks

How the product is built so it can watch your money without ever being able to move it · Last updated September 15, 2026

You are asked to connect banks, brokerages, Stripe and ad accounts to a young company. That deserves a straight explanation of what AtlasClicks can and cannot do with those connections, in plain language, and what proof stands behind it.

The one design rule

AtlasClicks never holds your money. Sales from your shop are charged directly on your own Stripe account, the buyer’s card is processed by Stripe, and the funds settle into the bank account you configured in Stripe. There is no AtlasClicks balance, no reserve, no payout schedule of ours in the middle. That is why we can say, structurally rather than as a promise, that AtlasClicks cannot freeze your balance: there is nothing on our side to freeze.

What AtlasClicks can never do

Hold your funds. Set a reserve. Delay or freeze a payout. Change where your Stripe pays out. Log in to your bank. Move money between your accounts. Charge a card without a buyer completing checkout. Act on a fraud alert without your tap.

What it does instead

Read your transactions and balances. Categorise them. Watch your Stripe charges for fraud patterns and propose blocks and refunds that you approve. Create Stripe Checkout sessions on your account when a buyer buys. Send payouts from your Stripe to your own bank only when you press the button.

Connections, one by one

Connection	Access	What it can do
Banks (via Plaid)	Read-only	Balances and transactions for bookkeeping. Plaid does not offer AtlasClicks any way to move money, and you enter your bank login with Plaid, never with us.
Brokerages (via SnapTrade)	Read-only	Positions and balances for the portfolio and trade journal. Trading permissions are never requested.
Stripe (Connect or a restricted key)	Scoped	Reading charges, customers, disputes and Radar signals; creating checkouts for your buyers; refunds, Radar block lists and payouts to your own bank only when you tap them. The payout destination can only be changed inside Stripe, by you. Disconnect at any time from My Store.
Meta & Google Ads	Propose & approve	Reads performance; every budget or campaign change arrives as a proposal you approve or ignore.
Discord	Roles only	Grants and removes the roles you map to products. Nothing else in your server is touched.

How your data is protected

Encrypted at rest. Every third-party access token (Plaid, SnapTrade, Discord, Stripe keys) is encrypted with AES-256-GCM before it is stored. The encryption key lives only in the runtime environment, never in the database.
Encrypted in transit. All traffic to atlasclicks.com and between our servers and providers is TLS.
Hard tenant walls. Every record is stored under your workspace, every API request is verified against your signed-in identity, and there is a single data gateway in the code that requires a workspace on every call. The browser has no direct database access at all; the database rules deny everything except our server.
Card numbers never reach us. Buyers type their card into Stripe Checkout, on Stripe’s pages. We receive the outcome, not the card.
Sign-in. Authentication is handled by Google Firebase (email/password and Google sign-in). Owners can require an app PIN for money-adjacent screens and SMS verification for the account.
Least privilege. Team members you invite see only the areas you grant. Payouts, refunds, Radar changes and account disconnects are owner-only.
Hosting. Google Cloud (Cloud Run and Firestore, US region), with provider-managed patching and encryption of the underlying storage.
AI. Anthropic processes the data an AI feature needs (for example a batch of transactions to categorise). Prompts and results are not used to train models.

Atlas Protect and your Stripe

Protect is a fraud watch, not a fraud model. It reads your recent charges and Stripe Radar’s own risk signals, looks for the shapes of an attack (many cards, identical amounts, a spike of declines, disposable emails, an early fraud warning from a card issuer) and shows you what it found. Every proposed fix is a button on your screen. Blocks go onto Radar value lists on your Stripe account; refunds and fraud reports run on your account, under your name, and each action is logged on the alert. Turn the email alerts off, ignore every proposal, or disconnect Stripe: Protect never acts on its own.

What we are working on

SOC 2 Type I. Controls are being documented against the AICPA trust criteria with the goal of an independent audit. We will publish the report here when it is complete; until then we do not claim it.
Independent penetration test of the app and the storefront before the SOC 2 audit window.
Status page for uptime and incident history.

We deliberately do not offer chargeback guarantees, embedded banking or any form of holding funds. Those are the features that turn a software company into the custodian of your money, and the entire point of AtlasClicks is that nobody but you and your bank should be.

Reporting a vulnerability

If you find a security issue, email security@atlasclicks.com with enough detail to reproduce it. We read every report, reply within two business days, and will credit you if you want us to. Please do not test against other customers’ data.