Security Policy
Effective October 30, 2026
1. Our Commitment to Security
We are committed to protecting the security and integrity of Minus, our users' data and the systems that support our services. This Security Policy describes the measures we have in place today. Where a protection is provided by one of our service providers rather than by Minus itself, we say so.
2. Infrastructure Security
2.1 Hosting and Data Centres
- Minus runs on two service providers. Vercel hosts the application, and Supabase hosts the database, sign-in and file storage. The database is held in Sydney, Australia.
- Vercel and Supabase each hold SOC 2 Type II reports for their own services. Those reports belong to the providers, not to Minus. You can read about them on Vercel's security page and Supabase's security page.
- Physical security, power, cooling and network connections at the data centres are managed by those providers.
2.2 Network Security
- Minus is served only over HTTPS. Every response tells browsers to keep using HTTPS for Minus for two years, including on its subdomains.
- Every response carries security headers. They stop other sites from showing Minus pages inside a frame, stop browsers from guessing file types, limit what is shared with other sites when you follow a link, and block the camera, location, payments and USB. The microphone is allowed only on Minus's own pages, for dictation in the chat.
- Signed-in pages have a strict content security policy, which limits the scripts a page may run, and any script that breaks it is reported to our error monitoring.
- When Minus fetches a web address that someone gives it, it refuses addresses on private or internal networks and checks every redirect, so a link cannot be used to reach Minus's own servers.
- Protection against denial-of-service attacks is provided by Vercel at its network edge, as part of its platform.
3. Application Security
- Every proposed code change runs automated unit tests, a type check, a dependency audit and end-to-end tests before it is merged.
- Some of those tests check that each brand's data stays in its own workspace. They fail if a server action stops checking that the person belongs to the workspace, or if another brand's record can be read or changed.
- Dependabot opens pull requests each week for outdated or vulnerable third-party libraries, and the dependency audit flags any production library with a known high or critical vulnerability.
4. Data Protection
4.1 Encryption
- Data travelling between your browser and Minus is encrypted with TLS.
- The database and file storage are encrypted at rest by Supabase, our database provider.
- On top of that, Minus encrypts the keys and tokens for your connected tools, such as Shopify, Klaviyo, Google, Meta and Gorgias, when it saves them. It uses AES-256-GCM, a standard method that also detects tampering. If the encryption key is missing, Minus refuses to save a key rather than store it as plain text.
- The encryption key is held as a protected server setting. Preview copies of the app use a different key, so test code cannot read production credentials.
- When you disconnect a tool, Minus deletes the keys it stored for that tool.
4.2 Access Controls
- Each brand's workspace is private to its members. Before an action reads or writes workspace data, Minus checks that the person belongs to that workspace. It works out which workspace a record belongs to from the record itself, rather than trusting what the browser sends, and it logs every refused attempt.
- Workspace members have roles: owner, admin, member and viewer. Only owners and admins can choose which AI features the workspace uses. Changes that Minus drafts can be approved by owners and admins, and by Minus staff (see section 5.4).
- Minus staff can open a workspace to support you. Staff access needs a staff account on a Studio Almond email address, and every time they open a workspace they are not a member of, it is logged, whether they use a workspace link or the workspace switcher inside the app.
- Sign-in is handled by Supabase, using an emailed link or code, or Google sign-in. Minus does not store passwords.
4.3 Logging
- An audit log records changes to records in Minus and, when a person made the change, who it was.
- A separate security event log records sign-ins, failed sign-ins, invitations, role changes, API keys created or revoked, tools connected or disconnected, data exported or imported, drafts approved or rejected, staff opening a workspace and refused access. Each entry records who, which workspace, when and the outcome, and anything that looks like a secret is masked before it is written.
- Each time Minus reads a stored key for a connected tool, it records the time, and the person when a person triggered it.
5. What Minus Sends to AI Models
Some Minus features use AI models to analyse your information and write answers, plans and drafts. A workspace owner or admin chooses which of these features run in Settings → Minus AI, and when a feature is switched off, nothing for that feature is sent. Our AI and Your Data page lists every feature and what each one uses.
5.1 Anthropic
Most AI features use Claude models made by Anthropic. Minus calls Anthropic's API directly, using Minus's own account. The features that do this are Minus chat, the plan builder, drafts, the weekly check, the writing and research tools, the brand summary and Brand Brain interview, the website copy check and the drafting of buyer questions for AI visibility.
Depending on the feature, the model can receive:
- what you type into Minus, with email addresses and phone numbers removed
- your Brand pages and Brand Brain answers, documents you upload and public web pages you point it at, with money figures held back
- counts, rates and ratios read from your connected tools, such as order counts, open rates and conversion rates
- the Klaviyo or Roadmap items a draft is about, your brand voice and your feedback on the draft
- 5-star reviews from Roadmap, with reviewer names and contact details removed
These requests are handled under Anthropic's standard commercial terms. Under Anthropic's Commercial Terms of Service, Anthropic may not train its models on the content we send. Anthropic keeps API requests for a limited period under its own retention policy, which is explained in Anthropic's Privacy Center. Minus does not train or fine-tune any AI model on your information.
5.2 Other AI providers
- AI visibility. When AI visibility is switched on for your workspace, Minus asks ChatGPT (OpenAI), Claude (Anthropic), Perplexity and Google Gemini a set of buyer questions, meaning the questions a shopper might ask an AI assistant before buying in your category, and records how they answer. Only the wording of each question is sent, along with your country for the assistants that accept it. No store data, figures or customer details are sent. Minus drafts the questions from your personas, positioning, support ticket subjects and site search terms, drops anything that looks personal, and asks only the questions a person on your team has approved. Questions about your brand include your brand name.
- Spoken answers in the Brand Brain interview. If you record or upload audio in the interview, the audio is sent to OpenAI to be turned into text.
- Image generation in Studio. This is off unless it is switched on for your workspace. When someone presses Generate, the images they chose and their instructions are sent to Higgsfield to make ad images. Before the first generation, an owner or admin of your workspace must accept Higgsfield's notice that it may train on the images sent and on the results.
5.3 What is never sent to AI
- Your customers' personal details. Names, email addresses, phone numbers and postal addresses are removed from every result Minus reads from your connected tools before a model sees it, and a Shopify request that asks for them is refused.
- Money figures. Figures that Minus stores, such as forecasts, targets, baselines and amounts in your exercise answers, are replaced with "[amount withheld]". Amounts read live from your connected tools, such as sales from Shopify or spend from Meta, are left out of the copy the model receives, so it works from counts and rates. You still see the full figures on screen.
- Anything from another brand's workspace.
These filters work by recognising field names and the patterns of emails, phone numbers and amounts. A customer's name written inside a sentence may not be caught, so please don't type customers' names into the chat or tools.
5.4 A person approves what goes live
Nothing an AI agent drafts goes live without a person approving it. Agents and the chat never write to your Shopify, Klaviyo, Gorgias or Roadmap directly. They save a draft, and the change runs only when an owner or admin of your workspace, or a member of Minus staff, approves it. Changes your customers would see, or that cannot be undone, need a second approval. Klaviyo flows and campaigns are created as drafts, and Minus cannot send a campaign. Meta and Google Ads are connected with read-only access.
6. Incident Response
If something goes wrong, our process is:
- Detection: We find problems through our error monitoring, our logs and reports from users.
- Triage: We assess what is affected and how serious it is.
- Containment: We act straight away to limit the problem, for example by rolling back to the last working version of Minus or revoking affected keys.
- Eradication: We find the root cause and fix it.
- Recovery: We restore the affected systems and services and confirm they work.
- Post-Incident Review: We write up what happened, why, and what we changed so it does not happen again.
7. Vulnerability Management
- Third-party libraries are checked for known vulnerabilities on every proposed code change and through Dependabot's weekly updates.
- We fix critical vulnerabilities as a priority once we know about them.
- We welcome reports from external researchers (see section 10).
8. Business Continuity
- If a release causes a problem, we can roll Minus back to the previous working version in Vercel within minutes.
9. Compliance
- We aim to meet our obligations under the New Zealand Privacy Act 2020 and, where they apply to you, the GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy Act). Our Privacy Policy explains what we collect and your rights.
- Card payments are handled by Stripe, which is certified to PCI DSS Level 1. Minus never receives or stores your full card number.
- Minus itself does not hold a SOC 2 or ISO 27001 certification. The certifications mentioned in section 2 belong to our providers.
What we're working towards: we are preparing Minus for a SOC 2 audit. This is work in progress, and Minus is not SOC 2 certified. The security headers, encrypted token storage and security event log described on this page came out of that work in October 2026.
10. Responsible Disclosure
If you discover a security vulnerability, please report it responsibly:
- Email: support@almond.studio
- Do not publicly disclose the vulnerability before we have addressed it
- Provide sufficient detail for us to reproduce the issue
- We commit to acknowledging reports within 24 hours
11. Contact
For security-related questions, contact us at support@almond.studio.