Information security policy
How we protect Superpowers, our customers' data and our providers' data. Last updated November 11, 2026.
- Company
- PESSOA DE QUEIROZ GALVÃO LTDA (PQG Ventures)
- CNPJ
- 51.432.376/0001-06
- Security and data protection
- Bruno Galvão · bruno@pqgventures.com
- Report a vulnerability
- bruno@pqgventures.com, subject “Security report”
1Purpose and scope
This policy sets the rules PQG Ventures follows to protect the confidentiality, integrity and availability of Superpowers (superpowers.tools): the website, API, MCP server, apps in ChatGPT and Claude, cloud browsers and browser automation, and the data of customers, suppliers and data providers that passes through them. It applies to everyone who works on Superpowers, including contractors and the automated agents we operate, and to the systems and providers that run it.
Our principles: least privilege (each person, key and system gets only the access it needs); data minimization (we collect and pass on only what a task requires); layered defenses; and a record of every relevant change and incident.
2Responsibilities
- Bruno Galvão, founder, is responsible for information security and is the data protection officer (encarregado). He approves this policy, grants and removes access, and leads incident response.
- Everyone with access keeps credentials and data confidential, uses them only for their work, and reports any suspected incident right away.
- Customers protect their API keys, set spending limits, revoke keys they no longer use, and use data obtained through the tools lawfully (see the privacy policy).
3Infrastructure
- The service runs on Railway in the United States, in a container built from a pinned runtime and a frozen dependency lockfile. The database and files sit on a persistent volume attached to that service.
- All traffic to superpowers.tools uses HTTPS. DNS is managed at Cloudflare.
- Card payments are processed by Stripe on Stripe's own pages and APIs; card numbers never reach our servers.
- Development uses its own database and its own vendor keys.
4Access control
Customers
- Sign-in with a one-time code sent by email (valid for 30 minutes, with a limit on attempts) or with Google (OpenID Connect with PKCE, state and nonce, and the token signature checked).
- Session cookies are HttpOnly, Secure and SameSite=Lax, and expire after 30 days.
- API keys are random, shown once, stored only as SHA-256 hashes and can be revoked at any time. Each key can have its own spending limit, and each account has a monthly limit.
- ChatGPT, Claude and other MCP apps connect with OAuth 2.1 and PKCE (S256). Each connection is a separate key that the customer can revoke in the dashboard.
- Every query is scoped to the account that makes it: one account cannot read another account's runs, files, keys or browser profile.
Internal
- Administration pages open only to signed-in people whose verified email is on the company domain or who were marked as administrators; everyone else gets “not found”. API keys never open administration pages.
- Access to production systems (hosting, payments, code repository, secrets store and email) is limited to the PQG Ventures team (today, the founder) and the automated agents he operates, each with its own credentials. Administrator accounts on those systems use two-factor authentication where the provider offers it.
- Access is reviewed when someone's role changes and removed when they leave, and the credentials they knew are rotated.
5Encryption
- In transit: TLS (HTTPS) on every connection to the site and API, and HTTPS on calls to vendors.
- Credentials at rest: vendor keys that customers connect, suppliers' API credentials and logins saved by our browser automation are encrypted with AES-256-GCM. Customers see only the last four characters of a saved key.
- Hashing: API keys and OAuth codes are stored as SHA-256 hashes. The few test-account passwords used by app directory reviewers are stored with scrypt and lock after ten wrong attempts.
- Signed links: payment links and the file links of our browser automation are signed (HMAC) and expire.
6Secrets management
- Vendor keys and other secrets live in a secrets store (development) and in the hosting provider's environment variables (production). They are never committed to code, written to logs or pasted into chats or tickets.
- Automated tests and builds run without production secrets.
- Each vendor account has a spending ceiling set at the vendor and a monthly budget enforced by our gateway, so a leaked or misused key has a bounded cost.
- Customers' cloud browsers run on a separate browser-provider project and key from the one our own tools use, and the service refuses to start if the two are the same.
- When a secret may have been exposed, we revoke and replace it at once.
7Data protection
- We send each vendor only the input of the call, never the customer's email, password or API key, unless a data provider's contract requires customer identification (see the privacy policy).
- A call made with the customer's own vendor key uses only that key and can never fall back to ours.
- Generated files get random names; the server never serves HTML, SVG or scripts from stored files and tells browsers not to guess file types.
- Site analytics stores no IP addresses, and sign-in tokens and other URL parameters outside an allowed list are dropped before anything is recorded.
- The link that controls a customer's live cloud browser is returned once and never stored in runs, logs or shares.
- Tools check their input before any network call, and tracking links can only point to public addresses (never internal networks).
8Secure development and changes
- Code lives in a private GitHub repository, and changes go through pull requests.
- Every pull request and merge runs automated checks: type checking, tests (including accounting tests), a Docker build and a smoke test of the production container. Production deploys only after those checks pass, and a new deployment must pass a readiness check, which includes an accounting integrity audit, before it receives traffic.
- Build actions and the runtime are pinned to fixed versions, and dependencies are installed from a frozen lockfile.
- A new tool goes live only after its exact code revision passes a two-round live acceptance test; any change to it needs a new test.
- A bad change is reverted through the same pipeline, or the previous deployment is restored.
9Logging and monitoring
- The application writes operational and error logs, kept by our hosting provider. We do not log sign-in codes, passwords, API keys or card data.
- Every charge and credit is recorded in a ledger whose entries are never edited, and an automatic audit checks that balances add up; production reports itself unhealthy when the audit fails.
- We monitor vendor failures (with automatic pauses), failing tools, unusual sign-up spikes and spending against budgets, and alerts go by email to the person responsible.
10Abuse and fraud prevention
- Self-service sign-up through the API is limited per IP address, and new sign-ups pause automatically when volume spikes.
- Disposable email domains get no free credit and cannot run tools, and expensive media generation requires paid credit.
- Account, key, project and vendor spending limits are checked before each paid call.
- We suspend accounts that break the terms of service and block abusive links.
11Vendors and suboperators
- Before adding a vendor we check that its terms allow use through a marketplace, record the account in a vendor register (owner, purpose and ceiling) and set a spending ceiling.
- We prefer vendors that commit by contract to confidentiality and data protection, and we list the suboperators that process personal data in the privacy policy.
- With data providers we follow their contract: we pass their usage restrictions on to customers, may require customer identification and purpose before enabling their tools, keep their data only as the contract allows, and tell them about incidents that affect their data.
- Vendor health is monitored continuously, and a vendor that keeps failing is paused automatically.
12Backups and continuity
- The production volume has daily, weekly and monthly backups at the hosting provider, and we take an extra backup before database migrations.
- Backups are restored into an isolated environment and checked with our accounting audit before any recovered data is used.
- Health and readiness checks run on every deployment; if a new deployment fails them, the previous one keeps serving.
13Incident response
A security incident is any event that compromises, or may compromise, the confidentiality, integrity or availability of data or systems. When we detect one or are told about one, we:
- Contain it: revoke affected keys and sessions, rotate secrets, pause affected tools or vendors, or restore the previous deployment.
- Assess it: what happened, which data and people were affected, and the risk to them.
- Notify: if personal data was affected in a way that may cause relevant risk or damage, we tell the ANPD and the people affected within 3 business days, as Resolution CD/ANPD 15/2024 requires. We tell affected customers and data providers without undue delay and within any deadline in our contract with them.
- Recover and learn: restore the service, fix the cause, and record the incident, its impact and the measures taken. We keep incident records for at least 5 years.
14Reporting a vulnerability
Email bruno@pqgventures.com with “Security report” in the subject, describing the issue and how to reproduce it. This contact is also published at /.well-known/security.txt. Please test only against your own account, do not access or change other people's data, and give us reasonable time to fix the issue before disclosing it. We will not take action against good-faith research that follows these rules.
15People and confidentiality
- Everyone with access to Superpowers data commits to confidentiality and gets only the access their work needs.
- Credentials are personal: people do not share passwords or keys with each other.
16Review
We review this policy at least once a year and after any relevant incident or change to the service. It is published in Portuguese and English; if they differ, the Portuguese version prevails. Questions: bruno@pqgventures.com.