StoryAudit

Privacy Policy

Last updated: October 12, 2026

Your .story files, XLIFF translation exports, and the reports and drafts built from them never leave your browser. We don't receive, see, or store the contents of your course or translation files.

1. Overview

This policy explains what information StoryAudit, operated by Weavara LLC ("we," "us," "our"), collects when you use storyaudit.app (the "Service"), and how it's used. StoryAudit is built so that the actual work, parsing and auditing your Storyline .story files, and checking or drafting a translation from an XLIFF file, happens entirely client-side, in JavaScript running in your own browser. Your course and translation files are read locally from your device using standard browser file APIs; they are never transmitted to our servers, uploaded to cloud storage, or sent to a third party as part of generating a report or a translation draft.

2. Information we do collect

CategoryWhat it isWhy
Account infoEmail address, any profile info you provide (e.g. via Google or Microsoft sign-in), and, on team plans, your organization's name and member list, all handled through our authentication provider, ClerkTo create and secure your account, and to communicate with you about your subscription
Billing infoSubscription status, plan, and billing history. Payment card details are collected and processed directly by Clerk's billing infrastructure and its payment processor; we do not receive or store full card numbersTo manage your subscription and trial
Basic technical dataStandard web server/hosting logs (e.g. IP address, browser type) generated automatically by our hosting provider when you load the siteSecurity, abuse prevention, and troubleshooting
Support correspondenceEmails you send to support@storyaudit.app and any information you choose to include in themTo respond to your question and improve the Service
Anonymous usage countsDaily counts of how the app is used: when it's opened, which tabs are shown, whether a file loaded or couldn't be read, and which export and download buttons are pressed. Each count holds only the tool (for example Course Docs), what happened or the file type (for example PowerPoint), whether it was in the demo or in an account, and the day. No name, account, file name, course content or IP address is stored with itTo learn which features people actually use, so we build and fix the right things

We use Google Ads conversion measurement, through a tag that runs only on our marketing pages and never inside the app itself, to learn which of our ads lead to a sign-up. It records that a sign-up happened after an ad click; it does not receive your name, email, or course files. We do not use any other third-party analytics or advertising trackers on storyaudit.app. We also count which export and download buttons are used in the app, along with app opens, tabs viewed and whether a file loaded, as described in the table above; those counts go only to our own server, never to a third party, and never include anything from your files.

3. Information we do not collect

We do not receive, view, or store: the contents of your .story files or XLIFF translation exports; any reports, exports, drafts, or PDFs StoryAudit generates from them; or any course content, images, audio, video, or text extracted or translated during an audit. All of that processing, translation, and any downloads happen entirely on your own device.

4. How we use information

We use the information above only to:

5. How we share information

We do not sell your personal information, and we do not share it with third parties for advertising. We share it only:

6. Security

We rely on reputable providers (Clerk for authentication and billing, Vercel for hosting) and standard safeguards such as encryption in transit (HTTPS/TLS) to protect the limited account data we handle. No method of transmission or storage is completely secure, so we can't guarantee absolute security. By design, though, the most sensitive material involved in using StoryAudit (your course and translation files, reports, and drafts) never reaches us at all.

7. Cookies and local storage

Our authentication provider, Clerk, sets cookies necessary to keep you signed in. The Service also uses your browser's local storage to remember preferences (like which mode you last used, or which report sections you've toggled off). This stays on your device and isn't sent to us.

To make repeat audits faster and more useful, the Service also stores two things in your browser's own database (IndexedDB), entirely on your device: a cache of recently generated reports (keyed by a fingerprint of the file's contents, so re-opening the same course is quick), and a local run history: the file names, dates, and finding counts of audits you've run on this device, which powers the in-app run history and its PDF/text export. The report cache is never transmitted to us or anyone else. On the Individual plan, neither is the run history. On a Team plan, run history also syncs to your team's workspace, as described in Section 7a. You can erase the run history at any time with the "clear history" control in the app, and remove everything (cache and history both) by clearing your browser's site data for storyaudit.app.

7a. Team workspace data

If you create or join a team, StoryAudit stores the following on our servers so your teammates can see it: your team's name and membership (names, email addresses, roles, invite codes); waived findings (the finding's rule, the slide title and file name it applies to, the reason given, who waived it and when); saved rule sets (Batch Check's pass/fail rule settings and style guide fonts, sizes and colors, who saved them and when); run history (file names, dates, finding counts); and sign-off records (course file name and fingerprint, who signed off, when). This data is stored in a Postgres database hosted by Neon (United States), served through Vercel, with access controlled by Clerk sign-in. It never includes the course file itself, its media, or its slide text beyond the titles named above. Team administrators can delete a team, which deletes this data; individual records are deleted on request to support@storyaudit.app.

8. Third-party services

9. Data retention and deletion

We retain account and billing information for as long as your account is active, plus a reasonable period afterward for legal, tax, and dispute-resolution purposes. Hosting access logs are retained only for the short periods our hosting provider keeps them. Anonymous usage counts contain no personal information and are kept as daily totals. Preferences and the report cache stay on your device until you clear them. Run history stays on your device on the Individual plan. On a Team plan, run history and waived findings are also synced to your team's workspace on our servers, as described in Section 7a. To request deletion of your account and associated data, email support@storyaudit.app.

10. Your rights and choices

You can ask us to access, correct, export, or delete the account information we hold about you at any time by emailing support@storyaudit.app from your account email address (we use that to verify it's really you). We'll respond within a reasonable time, and in any case within the period required by applicable law. You can also cancel your subscription at any time from within the Service.

If you are in the European Economic Area, the United Kingdom, or a similar jurisdiction: our legal bases for processing are performance of our contract with you (account, billing, and providing the Service), our legitimate interests (security, abuse prevention, and troubleshooting), and consent where required. You also have the rights to object to or restrict certain processing, to data portability, and to lodge a complaint with your local supervisory authority.

If you are a California resident: we do not sell or "share" personal information as those terms are defined in the CCPA/CPRA, and we don't use it for cross-context behavioral advertising. You have rights to know, access, correct, and delete personal information, and we will not discriminate against you for exercising them.

Other than the ad-click conversion measurement described in Section 2, we don't track you across other websites or apps, so there is no other cross-site tracking to opt out of; browser "Do Not Track" or Global Privacy Control signals don't change anything beyond that, since we already treat everyone that way.

11. International users

The Service is operated from the United States, and the limited account information we handle is processed in the United States (and wherever our service providers operate), where privacy laws may differ from those in your country. Where account information of EEA, UK, or Swiss users is transferred to the United States, we rely on our service providers' participation in the EU-U.S. Data Privacy Framework and/or Standard Contractual Clauses as the transfer mechanism. By using the Service, you understand your account information will be handled as described in this policy. Your course and translation files, as always, are processed only on your own device wherever you are.

12. Children's privacy

The Service is intended for business and professional use and is not directed at children. Consistent with our Terms of Use, we do not knowingly collect personal information from anyone under 16. If you believe a child has provided us personal information, contact us at support@storyaudit.app and we will delete it.

13. Changes to this policy

We may update this policy from time to time. Changes will be reflected by updating the "Last updated" date above, and for material changes we will make reasonable efforts to provide additional notice, such as an email to your account address or an in-app notice, before they take effect.

14. Contact

Questions about this policy, or want to exercise a data access/deletion request? Email support@storyaudit.app, or write to: Weavara LLC, 6545 Market Ave. North STE 100, Canton, OH 44721 USA.