Privacy Policy

SchemaSync is a content metadata validation and delivery pipeline tool used by media companies and distributors. This policy explains what information we collect when you use the service, how it is used, and how long it is kept.

SchemaSync is a B2B tool. We do not build consumer profiles, sell data, or use your content for advertising. The data you upload is used solely to run the validation pipeline and generate delivery outputs.

We collect the minimum necessary to operate the service:

• Uploaded file content — metadata slates you submit for processing (title, cast, synopsis, ratings, identifiers, etc.). This is the content you explicitly send to us.
• Sender email address — if you use the email ingest interface, we record the address the file was sent from so we can reply with your results.
• Run metadata — timestamps, file names, file sizes, and pipeline configuration (which endpoints were validated against). No personal information beyond what's in the uploaded slate.
• Session information — standard web server logs (IP address, browser type, request path). These are retained for up to 30 days for security and debugging purposes and are not linked to run data.

We do not use cookies for tracking, analytics, or advertising. We do not use third-party analytics services on the application.

When you submit a metadata slate, SchemaSync runs it through a multi-stage validation pipeline:

• Canonical normalisation — your content is parsed and mapped to a standardised internal schema.
• Validation — each field is checked against the delivery specifications for the endpoints you selected (e.g. Tubi CSV v1, Amazon MEC XML).
• Output generation — platform-specific delivery files are generated and made available for download.

All processing happens on our servers. Your data is not sent to any third-party service as part of the pipeline. Validation rules are evaluated locally against our schema engine.

Uploaded files and pipeline results are stored in temporary server-side storage. Specifically:

• Run records (canonical records, validation issues, output files) are written to the server's temporary directory (os.tmpdir()) as JSON files.
• Raw uploaded files are held in memory during processing only and are not written to disk separately from the run record.
• Generated delivery packages (CSV, XML, JSON outputs) are available for download immediately after the run and are deleted with the run record.

There is no separate file storage system, object store, or content delivery network used. All data lives in the run record.

Run records are retained under the following policy:

• Session runs — stored in the server's temporary directory and deleted when the server restarts or the temporary directory is cleared by the operating system (typically within 24–72 hours on most systems).
• Demo runs — marked separately and can be cleared immediately using the "Reset Demo" button in the UI.
• Email runs — retained for the same duration as session runs. The response email (and any attached QA reports) are delivered to the sender and are governed by the recipient's own email provider.

You can request deletion of any run at any time by contacting us at hello@schemasync.io. We will confirm deletion within 2 business days.

We take reasonable steps to protect your data in transit and at rest:

• Transport encryption — all connections to SchemaSync are served over HTTPS/TLS. Data in transit between your browser and our servers is encrypted.
• No external data egress — your uploaded content does not leave our servers during pipeline processing.
• No persistent database — run data is stored in ephemeral server-side files, reducing the attack surface associated with a persistent database.
• Tier-based access controls — API and email ingest endpoints are gated by account tier and require a valid session.

No system is perfectly secure. If you discover a security issue, please report it to security@schemasync.io.

SchemaSync does not share your data with third parties for marketing, advertising, or analytics. We may share data in the following limited circumstances:

• Legal compliance — if required by law, regulation, or valid legal process (e.g. a court order).
• Service providers — infrastructure providers (hosting, networking) who process data on our behalf under confidentiality obligations. These providers do not have access to the content of your runs.

You have the right to request access to, correction of, or deletion of any personal data we hold about you. To exercise any of these rights, contact us at hello@schemasync.io.

Because the primary data we hold is content metadata (titles, cast, etc.) that relates to creative works rather than individuals, most requests will be simple to fulfil.

We may update this policy as the service evolves. When we make material changes, we will update the effective date at the top of this page. Continued use of SchemaSync after changes are posted constitutes acceptance of the updated policy.

Questions about this policy should be directed to hello@schemasync.io.