Draft. This version is not yet in effect; it takes effect on the date shown here once published.

Security

This page describes how Motionscript LLC protects the work and the data you trust us with. To report a vulnerability, see Reporting a vulnerability below or email security@motionscript.dev.

Where your data lives

Local workspaces never leave your computer unless you choose to upload them or send part of them to the assistant. The Subprocessors page lists every provider that handles personal data.

Encryption

• In transit: all traffic to the Service uses TLS (HTTPS).
• At rest: the database, file storage and backups are encrypted with AES-256 by our hosting providers.

Access control

• Workspace isolation in the database. Every workspace's data is isolated by row-level security policies that the database enforces on every query, so one account can't read another workspace's data even through a bug in the app.
• Private files. Uploaded files are stored privately and reached only through signed links that expire, issued to members of that workspace.
• Roles. Organizations assign roles (owner, admin, creator, viewer). Only owners and admins manage members, and only the owner manages billing.
• Secrets stay on the server. The keys for payments, AI providers and admin access exist only in server-side functions, never in the apps you download or load.
• Our own access. Access to production systems is limited to the people who need it, through accounts protected by two-factor authentication.

Accounts

• Passwords are stored only as salted hashes.
• Two-factor authentication with an authenticator app is available in Settings → Security. Organization admins can see which members have it on.
• Sessions end when you sign out. Deleting your account signs you out on every device.

Backups and availability

The database is backed up daily, and backups are kept for 7 days. We run on managed infrastructure with its providers' redundancy, and we monitor errors so we can fix problems quickly.

AI processing

• No training. Your content isn't used to train AI models, by us or by our providers.
• The assistant. It sends only your message and the project information needed to answer it.

The desktop app

• Builds and updates. Builds are code-signed (and notarized on macOS), and updates are downloaded over HTTPS.
• Local services. Local workspaces are ordinary folders you control. When the app connects to tools on your computer, it uses a local service that can only be reached from that computer and requires a key stored there.

Privacy by design

• No advertising, no analytics cookies, no cross-site tracking.
• Error reports are scrubbed of email addresses, access tokens and file paths before they leave your device.
• Deleted content is permanently purged after 30 days, and leaves backups within 7 days after that.

Incident response

If we learn of a security incident that affects your data, we investigate, contain it, and notify affected customers and authorities as the law requires. Business customers are notified within the time set in our Data Processing Agreement.

Reporting a vulnerability

If you find a security issue in Motionscript, please tell us. Email security@motionscript.dev with:

• a description of the issue and where it is;
• steps to reproduce it, and any proof of concept;
• how you'd like to be credited, if you'd like to be.

We'll acknowledge your report within 3 business days and keep you updated until it's resolved.

Safe harbor. We won't take legal action against good-faith research that:

• only uses your own accounts and test data, and never accesses, changes or deletes other people's data;
• avoids degrading the Service (no denial-of-service, spam or social engineering);
• gives us reasonable time to fix the issue before you disclose it publicly.

We don't run a paid bug bounty at this time. Our security.txt has these contact details in machine-readable form.

Questions

For security questionnaires and other questions, email security@motionscript.dev.