What we do with the keys you give us
Affiliate Guardian reads the reporting behind your affiliate income. That access is a responsibility, so this page separates controls that exist today from work that is still pending.
- 01
Tenant-scoped product data has a database backstop
Affiliate Guardian uses Postgres row-level security on tenant-scoped product tables. Member requests use a tenant-scoped database transaction, while the smaller set of cross-tenant system jobs uses a separate privileged connection. Authentication and system tables are not tenant product rows, so we do not claim that every row in the database carries a tenant id or that row-level security makes application bugs harmless.
- 02
Stored network credentials are envelope-encrypted
Each stored network credential set is encrypted with AES-256-GCM using a fresh data-encryption key. That key is wrapped by the deployment's master key before storage. The current deployment uses an environment-held master key; it has not yet moved to a managed key service. Member-facing product paths do not return stored plaintext credentials, and the credential code has tests intended to catch plaintext logging.
- 03
We ask for read-only network access wherever a network offers it
The job is to watch your reports, not to change your account. Where a network supports read-only scopes, that is what we request.
- 04
We do not ask for bank access
Affiliate Guardian currently verifies recovery against affiliate-network reporting. The product does not connect to a customer's bank account or ask for bank credentials.
- 05
We will not drive your browser without asking
Some networks publish nothing we can read from an email or an API. For those, the intended fallback is a check you run in your own browser, under your control, and only after we have tried email or API first. Nothing of the kind runs today. This is written down here, rather than on a marketing page, because it is a commitment about your account rather than a feature to sell.
- 06
Cross-publisher benchmarks are not active
Affiliate Guardian does not currently publish cross-publisher benchmarks from customer data. Before that changes, the aggregation threshold, consent model, and privacy review must be defined and implemented. We will update this page before enabling the feature rather than describe a planned privacy control as if it already runs.
What we have not done yet
We are not SOC 2 certified, and we have not completed an independent penetration test. The deployment master key is not yet held by a managed key service. If your team requires one of those controls before connecting data, please treat it as a requirement rather than assume it is present.
Report a security concern