Information we collect
We collect account and workspace details such as names, email addresses, organization membership, role assignments, and sign-in information needed to run a protected workspace.
We collect business-submitted audit material such as business profiles, goals, service context, source descriptions, customer journey notes, intake evidence, and documents or links provided for an audit.
Auditors may add evidence collected during the audit, including public website observations, Google profile and review notes, booking-flow findings, screenshots, photographs, staff or customer interaction notes, policy observations, comfort or space observations, and other authorized journey evidence.
How we use audit information
We use audit information to create and manage customer journey audits, organize evidence, normalize signals, prepare findings, build action plans, track retests, generate report snapshots, and deliver completed work to authorized clients.
We may use support messages and product activity to operate the service, troubleshoot issues, protect the workspace, and improve the platform. We may use anonymized or aggregated learnings for product improvement, case-study learning, and service development when they do not identify a specific business, customer, staff member, or private audit record.
Supabase, storage, and security
JustUsability uses Supabase for authentication, database records, and file storage. Workspace data is protected by authenticated access, role checks, and database security rules. Evidence files, source imports, and report exports are treated as private product data rather than public website assets.
No internet service can promise perfect security. We design the product around scoped roles, private storage, and authenticated access patterns, but customers should avoid submitting highly sensitive personal, medical, financial, or legal data unless it has been expressly scoped for the audit.
Report exports and delivery links
Reports may be generated from stored audit records as HTML and PDF snapshots. Those snapshots can include audit summaries, journey-stage narratives, findings, evidence references, action plans, retest plans or results, and an evidence appendix.
Client delivery links route authorized workspace users to protected report packages and private exports. Customers should share delivery links only with people who are allowed to view the report.
Designs assessed with the Figma plugin
What we send. To run a check, the plugin sends a picture of each frame you choose, its layers and text, nearby notes in the file, and the context you confirm.
Who gets it. It goes to the JustUsability server, and from there to Anthropic, which runs the AI model that does the assessment. Anthropic processes it in the United States. Under its commercial terms, Anthropic doesn't train its models on what we send.
What we keep. When you're signed in, we keep the findings, the context, the frame names and a small picture of each frame on our server, so you can see your history. We also keep the Figma file's id, and any useful or not useful marks you give a finding. We do not keep the full pictures, layers or text, and we never keep your designs to learn from. History is for you only; no one else can see it in the plugin.
What we learn from it. We use your useful or not useful marks, the findings and context we keep, which findings go away when you re-run a frame, and how the plugin is used, to improve our checks and build our own tools, including AI ones. Combined across many designers, they also help us publish research on common usability problems. What we publish is counts and patterns, never your findings as written, and nothing that identifies you, your company or your design. We don't use the small pictures for any of this. Once you delete your history, we stop using it; anything already combined into published counts stays in them.
Your internet address. When you connect the plugin to your account, we keep the internet (IP) address the request came from for up to a day, only to limit repeated attempts. Then it is deleted.
How long. Until you delete it, or ask us to delete your account. Deleting history doesn't give back an assessment you've already used this month. We keep a record that a check was counted, with no design content in it.
How to delete it. In the plugin, open Settings and choose “Delete this file's history” or “Delete all my history”. That removes the findings, context, frame names, file id, small pictures and your useful or not useful marks. You can also email hi@justusability.com and we'll do it for you.
When we share information
We share information with people who have authorized access to the relevant workspace, such as business owners, JustUsability admins, auditors, invited clients, and viewers. We also use service providers that help run the platform, including Supabase and email delivery infrastructure.
We may disclose information if required to comply with law, protect the service, investigate misuse, enforce our terms, or respond to a valid legal request. We do not sell customer audit records.
Your choices and requests
Business owners can ask us to correct, export, restrict, or delete account and audit information where practical. Some records may need to be retained for security, dispute handling, backup recovery, accounting, or completed audit delivery history.
Audit report workflows are manual and Supabase-backed. The Figma plugin is the one place we use an AI model, and the section above says what it sends, to whom, and what it keeps.
Contact
For privacy questions, access requests, corrections, deletion requests, or audit-data handling questions, email hi@justusability.com.