Table of Contents
1 Information We Collect and How We Collect It
My Content Tools LLC limits data collection to the absolute minimum required to operate our B2B SaaS platform securely. We collect account credentials, professional production availability parameters, and anonymized subscription statuses. When a document is signed, we record the time and the IP address of the signing request.
2 Bifurcated Identity Processing & 2257 Firewall
To satisfy cross-border privacy mandates and data minimization principles, My Content Tools LLC enforces an absolute, structural firewall between platform access data and federal compliance records. These two pipelines are never commingled:
Platform Access (The Verify-and-Purge Gate): To verify legal majority (18+) for directory authentication, biometric and ID data is transmitted directly from the user's local device to our third-party Verification Provider. This data bypasses our servers entirely. The provider destroys the raw data immediately upon generation of an anonymized access token.
Federal Compliance (Software Infrastructure): My Content Tools provides software that helps studios organise their records. Records created in the software are kept on the studio's computer and, where captured in Model Release Pro, in our cloud service. The studio or creator using the software is the Custodian of Records and is responsible for keeping them for the period the law requires.
A user's public-facing directory profile contains strictly categorical, pre-approved commercial data and is structurally isolated from any raw compliance records held in the 2257 vault.
2a Data Handling & Security
This section describes the desktop application's data path, and is reproduced verbatim inside the application itself so the two cannot drift apart.
1. Where your data is stored. My Content Tools stores your records on your own computer. If you use Model Release Pro, what you capture on your phone (performer details, ID images, signatures, signed documents, consent videos and media you choose to send) is uploaded to our cloud service, hosted by Google Firebase in the United States, so it can be delivered to your computer when you press Sync. Copies of records remain in our cloud service after Sync. Media sent through phone import is removed from our cloud service once your computer has imported it. AI features run on your computer by default. If you choose to use an optional Grok feature, your request, including the details that feature uses to answer (for example your Train My AI profile, your My Voice settings and the text you typed), is sent to xAI under your own xAI account and is subject to xAI’s terms and privacy policy. We do not receive it. Grok only runs after you accept a one-time notice.
2. Local ID Vault. To guarantee strict isolation for data stored locally on your device, the on-device ID Vault is guarded by an independent, user-generated Custodian Passphrase. Keys are managed through the operating system's native secure storage (Apple Keychain, Windows Data Protection API, Android Keystore). On macOS the vault key is additionally bound to the application's code signature; on Windows it is bound to the signed-in user account. Our company possesses no mechanism to bypass this passphrase, intercept your keys, or decrypt your local vault.
3. Cloud Compliance Vault. Separately, finalized compliance documents (such as generated §2257 records) transmitted to your cloud vault are secured using industry-standard server-side encryption at rest. This ensures these records remain securely vaulted while allowing necessary backend processing, such as cryptographic integrity sealing, and ensuring their availability for lawful inspection.
4. Phone sync and our cloud service. Records captured in Model Release Pro are stored in our cloud service and remain there after your computer imports them. Data in our cloud service is encrypted in transit and at rest by our cloud provider.
5. Integrity Sealing. To cryptographically prove record integrity, a non-identifiable hash of the final document may be transmitted to a secure Time-Stamping Authority. No personal or biometric data is included in this transmission.
3 Legal Compliance Workflows & Mandatory Reporting
We strictly prohibit the transmission or storage of illegal content. In the event that suspected violations of federal law (including Child Sexual Abuse Material) are reported to us or otherwise come to our actual knowledge, the associated account will be immediately terminated. We comply with all mandatory reporting obligations to the National Center for Missing & Exploited Children (NCMEC) and will preserve associated user data, metadata, and communication logs for 90 days, or as otherwise requested by law enforcement pursuant to 18 U.S.C. § 2258A.
4 Payment Processing & Financial Data Isolation
My Content Tools LLC does not collect, process, transmit, or store payment card numbers, bank account details, or raw financial data. All subscription payments and financial transactions are securely outsourced to a PCI-compliant, third-party payment processor acting as Merchant of Record. When initiating a transaction, your payment data is transmitted directly from your browser to that processor via a securely hosted checkout environment operated by them, not by us. The processors we currently use are identified in our Payment Partners schedule, which is maintained outside this Policy so that it can be kept current without altering this agreement. My Content Tools LLC receives only subscription status webhooks (for example: active, canceled, renewed) and a transaction reference identifier, used to grant or revoke platform access.
5 Data Security & Third-Party Sharing
Data in our cloud service is encrypted in transit and at rest by our cloud provider. Data stored on your own computer is protected by your computer's own security; ID images, tax ID numbers and saved credentials are additionally encrypted by the app. We do not sell your personal data to third parties. We share data only with strictly vetted infrastructure sub-processors (such as our payment gateway and age-verification providers) solely to the extent necessary to deliver the Platform functionality.
6 Third-Party Integrations
My Content Tools offers optional integrations with third-party services that you may choose to connect (for example, accounting software such as QuickBooks/Intuit). When you connect such a service and direct us to sync data, you authorize us to transmit the relevant records — which may include personal information such as names, contact details, addresses, and tax identification numbers (such as SSNs or EINs) — to that third-party service on your behalf. This transmission occurs at your direction and is subject to the third party’s own privacy policy and terms. You are responsible for your use of connected services.
My Content Tools LLC
Privacy inquiries: privacy@mycontenttools.com
General support: support@mycontenttools.com
St. Petersburg, Florida