Security and data protection overview

What we collect

• Account details: work email address, company name, industry and size range, and your name if you sign in with Google.
• Partnership details you enter: the partner's name (a code name works just as well), industry, size range, stage and start date, and optional logos.
• Assessment answers, in every assessment: scores of 1, 3 or 5, the one-line evidence a score of 5 needs, and notes. In the Partnership Assessment, also STOP marks and any commercial context you add, such as the commercial model or minimum commitments.
• Work you do after results: action plans, owners and due dates, check-ins, comments, and business case figures you enter.
• Records of what happened: which version of the Terms and Privacy Policy each person accepted, when, from which IP address, and the exact words shown. Who viewed or downloaded a released report. Every page an EGP admin opens.
• Usage data from server logs: browser and device type, IP address, pages used, and times of access.
• From the free business case calculator, only if someone asks for the PDF by email: name, email, company, partner name, the partnership model, the headline results, and the consent wording they agreed to.

What we don't collect

• Passwords. There are none to store.
• Payment card numbers. Card payments happen on Stripe's own pages, and PartnerScope® never receives the card details.
• Advertising or tracking cookies, tracking pixels, or session recordings.

Where data is stored and how it is protected

• All PartnerScope® data is stored in the United States, in a managed Postgres database run by Supabase in its US East (Ohio) region. The app runs on Vercel in the United States.
• All traffic is encrypted in transit with HTTPS, and browsers are told never to connect any other way (HSTS).
• The database and its backups are encrypted at rest.
• Logos, the Governance Board Slide template, consent records, share link records and similar data sit in tables the browser can't read at all. Only server code reads them, and only for the people allowed to see them.
• Every page sets a content security policy and refuses to be shown inside another site's frame. Invite and share pages send no referrer, so a private link never leaks to another site.
• Keys for outside services are held in our providers' encrypted settings, never in the code.

Signing in

• There are no passwords. Members sign in with a one-time link sent to their work email, with a Google account, or with a passkey.
• Members can add two-step sign-in with an authenticator app. EGP admins must use it: admin pages and downloads refuse any session without it.
• A company's owners can require two-step sign-in for everyone working in the company, including any consultants. Each person then needs an authenticator code or a passkey, checked on every page, action and download.
• Owners can also limit who can join to their own email domains. Invites to other addresses are refused, and the database refuses them too.
• The server checks who is signed in on every request, not only on screen.
• Sign-in links, invite links and requests for fresh links are rate limited.

Who can see what

• Each company's data is kept apart inside the database by row-level security. A member of one company can't read another company's records, even with a direct call to the database. Automated tests check this, across companies and across the two sides of a partnership.
• Within your company, your members see your company's assessments, reports and action plans.
• If a consulting firm runs PartnerScope® for your company, including the Evolve Growth Partners consulting team, the firm's team are members of your company account and see what your members see.
• Notes are private to the side that wrote them. Sharing a note with the partner is a choice made one question at a time.
• The evidence line behind a score of 5 stays with its own side, even after results release. The database enforces this.
• When a teammate gives you their private view before you answer, only you see it.
• Owners can see who opened or downloaded each released report, and when. Changes to the company's sign-in rules show in the team's activity log.

Joint Partnership Assessments: sealed until both sides submit

• Each side answers in its own sealed session. Until both have submitted, neither side can read the other's answers. The database enforces this, so it holds even for someone calling the system directly.
• Results release to both sides at the same moment, so nobody can adjust their answers after seeing the other side's.
• The partner is invited by a private link sent to the email address the inviting company confirms. It works once, expires after 14 days, and opens only that one assessment. A fresh link goes only to the invited address.
• Before starting, the partner sees who invited them and what will and won't be shared, and must accept the Terms and Privacy Policy. They can decline, and the link stops working.
• The inviting company or EGP can remove a partner's access at once. That ends their session and every link.
• Answers lock on submit. A delivered report never changes, even when the advice library is updated.

What you choose to share

• View-only share links: a released report can be shared by link for up to 30 days. The link holds a random code, and the database keeps only a one-way hash of it. A shared view leaves out notes, evidence, written answers, commercial details and email addresses. You can turn a link off at any time.
• Downloads: report PDFs, summaries, portfolio reports and the Governance Board Slide download only for the company that owns them. Your members can export assessments and action plans as CSV files.
• Result images for LinkedIn: on Organizational Readiness and Data Stewardship reports, the image includes the company name and area scores only if you tick them. PartnerScope® never posts anything for you.
• API keys, on the 10-assessment pack and Unlimited plans: the API reads released results and can add or update partnership records, never answers, notes or evidence. A key is shown once and only a one-way fingerprint is stored. Requests are rate limited, and a key can be revoked at any time.

How AI is used

• PartnerScope® uses Claude, from Anthropic, through Anthropic's commercial API. It is called only from our servers. Prompts and the advice library never reach the browser.
• AI plays no part in any score, rating, gap or STOP flag. Those come from fixed rules in code, and the AI has no way to change them.
• Every recommended step comes from the Evolve Growth Partners advice library. AI may reword a step to fit the partnership. Each rewording is checked automatically, and any that fails keeps the library's own words.
• What the AI receives: the company and partner names, any commercial context, the library steps it is rewording, and the respondent's own notes on those questions. The coaching tools receive what a person types into them. The chat on our public pages sees only what a visitor types.
• Anthropic's commercial terms don't allow it to use this data to train its models.
• If the AI is unavailable, reports use the library's own words. Nothing else depends on it.

Research and benchmark data

• Under the Terms of Service, EGP may combine de-identified results across customers for research and benchmarks. We never name a customer, a partner or a person.
• Research records are written by the database itself. They hold scores, gaps, STOP flags, framework version, mode, and industry and size ranges only. Never names, notes, evidence lines or partnership names.
• Organizations are counted by a one-way code, not by name.
• No figure is published from fewer than 20 assessments or fewer than 5 organizations.
• A company can ask us to leave its results out of research data.

Evolve Growth Partners staff access

• A small number of EGP staff have admin access to run and support the service. Admin rights are held in the database and can't be granted from a browser.
• Admins can see customers, partnerships, scores, ratings, gaps and STOP flags by name. Through admin access they never see the text of notes or evidence lines. The one exception is a company that has the Evolve Growth Partners consulting team run PartnerScope® for it, as described above.
• Admins must use two-step sign-in. Every admin page view is logged with who, what and when.
• EGP can hold a report's results, for example after a misdirected invite. While held, the database hides them from both sides.
• Plan access is written only by server code, after a verified Stripe payment or an admin action. A browser can't grant itself access.

Monitoring, backups and recovery

• Errors alert our team right away. Before an error report leaves PartnerScope®, we remove email addresses, sign-in links and codes, form contents, cookies and user details.
• Supabase backs up the database every day and keeps 7 days of backups.
• Every night we also store an encrypted copy of the database off-site with Backblaze, kept for 30 days and locked so it can't be changed or deleted early. Only we hold the key that opens it, and we have tested restoring the database from it.
• Before any change to the database's structure, we take an extra full copy, so the change can be undone.
• Automated tests and a full production build run before each release. Every release is kept, so a faulty one can be rolled back in minutes.

Incident response

• We keep a written incident response plan, with a step-by-step runbook for switching off affected features and an incident log.
• If information is disclosed to the wrong person, we investigate, stop further access, and ask the recipient to delete it. We notify affected customers, people and regulators as the law requires, and may tell an affected company directly where that is appropriate.
• To report a vulnerability, email the address on our security and trust page. It is also listed in the standard security.txt file at /.well-known/security.txt.
• The record of who accepted which terms is append-only and chained, so any edit would show. The database refuses changes and deletions.

Keeping and deleting data

• We keep your data while your account is active. If your plan lapses, new assessments stop, but past results stay viewable.
• You can ask us for a copy of your data, or to delete it. Deleting a company removes its assessments, answers, notes and results. De-identified research records and the consent record are kept.
• We follow a written retention schedule. A company with no active plan and no sign-in for 24 months is deleted, after we email its owners 30 days ahead. Requests to delete are handled within 30 days. Calculator leads, anonymous chat questions and feedback are deleted after 24 months.
• Deleted data can remain in backups until those backups expire.

Certifications and audits

• PartnerScope® does not yet hold SOC 2 or ISO 27001 certification, and has not yet had an independent penetration test. We say so plainly rather than imply otherwise.
• On November 13, 2026, the live site scored A+ (120 points, all 12 tests passed) on Mozilla Observatory, Mozilla's free check of a website's browser security settings, such as its script policy and HTTPS enforcement. It's an automated check, not an audit, and anyone can run it again at developer.mozilla.org/en-US/observatory.
• We're glad to complete your security questionnaire and walk your team through any part of this overview.

Service providers

These companies process data for us to run PartnerScope®. Each is a US company. Each may use the data only to provide its service to us.