Nullgen AI BlockerTrust Center
Security controls
What Nullgen operates today to protect customer data, grouped the way security reviews ask about it.
Tags show which SOC 2 Trust Services Criteria a control supports, so you can cite it in a questionnaire. They describe our alignment work and are not an audit result. We do not hold a SOC 2 report today.
Product and customer data
Prompt detection runs on the device
In placeThe browser extension decides whether a field is an AI prompt using detection that runs inside the browser. There is no cloud classifier, and no page content, field content, or keystrokes are sent to Nullgen to make that decision.
- C1 · Confidentiality
The phone filter answers on the phone
In placeOn iPhone and iPad the blocker appears as a VPN configuration because that is how iOS lets an app filter. It does not route traffic to Nullgen or any remote server. Lookups for known AI destinations are answered on the device; every other lookup goes to the network’s usual resolver.
- C1 · Confidentiality
No prompt text, keystrokes, browsing history, or DNS logs
In placeNullgen does not collect what people type or where they browse, on any platform, for any purpose. There is nothing of that kind to secure, breach, or hand over.
- C1 · Confidentiality
Short-lived device credentials
In placeEnrolled browsers and phones authenticate with access tokens that expire after one hour and rotating refresh credentials that expire after 90 days without use. Deleting a device in the dashboard revokes them.
- CC6 · Access
Role-based dashboard access
In placeOrganization roles are Owner, Admin, Approver, and Viewer. Only Owners and Admins can manage people, devices, billing, and deployment. Approvers act on access requests; Viewers read.
- CC6 · Access
Infrastructure
Hosted on AWS in the United States
In placeThe dashboard, API, and data stores run on managed Amazon Web Services in the United States. Nullgen operates no servers of its own to patch.
- A1 · Availability
TLS everywhere, HSTS with preload
In placeEvery connection from the extension, the apps, the dashboard, and the website uses TLS. nullgen.ai sends Strict-Transport-Security with a two-year max-age, includes subdomains, and carries the preload directive.
- CC6 · Access
- C1 · Confidentiality
Encrypted at rest
In placeDatabases, identity stores, and storage buckets use the AWS services’ built-in encryption at rest.
- CC6 · Access
- C1 · Confidentiality
Infrastructure as code
In placeEvery cloud resource is declared in code and deployed from it, in a repository with review. Nothing is created by hand in a console, so the running environment can be reproduced and reviewed from its definition.
- CC8 · Change
Secrets stay out of the repository
In placeAPI keys, signing keys, and third-party credentials are held in the deployment platform’s secret store and injected at deploy time. They are never committed to source control.
- CC6 · Access
- C1 · Confidentiality
Production stores protected from deletion
In placeProduction databases carry deletion protection and are retained if the stack is ever torn down. Development uses a separate stack, separate credentials, and the payment provider’s sandbox.
- A1 · Availability
Access control
Multi-factor authentication for every staff account
In placeAll staff accounts on our cloud provider, source control, app stores, payment provider, and email provider require a second factor.
- CC6 · Access
Least privilege between components
In placeEach function and service is granted only the permissions it needs to reach the resources it uses, declared alongside the resource in the infrastructure definition.
- CC6 · Access
Verified administrator sign-in
In placeDashboard and admin API access require a signed-in administrator through Amazon Cognito, with a verified email address or Google or Apple sign-in. Nullgen never stores passwords itself. Sessions use HttpOnly cookies.
- CC6 · Access
Zero-trust access, verified on every request
In placeNo request is trusted for where it comes from. Every call from an enrolled browser, phone, or administrator carries a short-lived signed credential that is verified on each request and scoped to one organization, and live-update connections are authorized the same way before they open.
- CC6 · Access
- C1 · Confidentiality
Development and change management
Code review before merge
In placeChanges are reviewed before they are merged and deployed to production.
- CC8 · Change
Automated checks on every change
In placeLinting, type checking, copy consistency checks, and unit tests run in continuous integration on every change. Billing and access code carries dedicated test coverage.
- CC8 · Change
Separate development and production
In placeA development environment with its own credentials and a payment sandbox is where changes land first. Production is a separate, protected stack.
- CC8 · Change
Monitoring and incident response
Error and crash monitoring
In placeErrors from the website, the extension, and the apps are reported to Sentry with technical details only. Reports exclude prompt text, page addresses, browsing history, and DNS lookups, and the component that performs blocking on iOS sends none.
- CC7 · Operations
Failure alerts to the team
In placeScheduled job failures and captured errors raise alerts to the team so they are seen and handled.
- CC7 · Operations
Documented incident response
In placeA written process covers detection, triage, containment, notification of affected customers, and post-incident review. A customer-facing summary is available on request.
- CC7 · Operations
Business continuity
Point-in-time database recovery
In placeProduction databases keep continuous backups that allow restoration to any second in the preceding 35 days.
- A1 · Availability
Managed, redundant services
In placeCompute, database, identity, and delivery run on AWS managed services with the provider’s built-in redundancy. There are no single Nullgen-operated servers to fail or fall behind on patches.
- A1 · Availability
Vendors and payments
A short, published provider list
In placePersonal data is shared only with the service providers listed on the data handling page, and only to operate the service. The same list appears in the Privacy Policy.
- C1 · Confidentiality
Card data never touches Nullgen
In placePayments run on Stripe’s hosted checkout and billing portal or through Apple’s App Store. Nullgen receives subscription identifiers, never full card numbers.
- C1 · Confidentiality
SOC 2
Nullgen is aligning its controls with the SOC 2 Trust Services Criteria for security, availability, and confidentiality. A SOC 2 Type I audit is on our roadmap, and a third-party penetration test will be carried out as part of that process. We do not hold a SOC 2 report today.
Aligning controls with the Trust Services Criteria
In progressMapping the controls on this page to the criteria and closing the gaps the mapping shows.
SOC 2 Type I audit
PlannedAn independent auditor’s report on the design of our controls.
Third-party penetration test
PlannedExternal testing of the website, API, extension, and apps, carried out as part of the audit process.