Your metadata is uploaded to temporary encrypted storage, processed, and then automatically deleted. Scoring data is processed through secure, isolated API calls with zero retention. When analysis completes, the source data is gone.
MQS analyzes the structure and patterns in your metadata. It does not retain, index, or search your file contents.
Uploaded files are temporarily stored in encrypted cloud storage during processing, then automatically deleted upon completion. No file data is retained after your analysis finishes.
Each analysis runs independently. Your data is never mixed with other clients' datasets, used for model training, or referenced by any other session.
When your analysis completes, the source file is automatically deleted from storage. MQS retains your score and report metadata. The underlying file contents are gone.
Your raw file contents are never stored or shared. Scoring data is processed through secure, isolated API calls with zero retention. No data is used for model training or advertising.
MQS retains only the metadata needed to display your report. Nothing from your file contents is kept.
You can delete any report from your dashboard at any time. Deletion is immediate and permanent. Upon account deletion, all associated report metadata is removed within 30 days.
MQS is built for metadata exports from DAM, PIM, CMS, and MAM platforms. It is not designed for regulated or sensitive data.
MQS is not HIPAA-compliant. The Service does not enter into Business Associate Agreements (BAAs) and is not a Business Associate, subcontractor, or agent of any user pursuant to HIPAA. Uploading Protected Health Information is prohibited under the Data Upload Terms.
Security is enforced at every layer, from transport to database.
All traffic is encrypted in transit. Strict Transport Security is enforced with a two-year max-age, includeSubDomains, and preload directives.
Every response includes X-Frame-Options (DENY), X-Content-Type-Options (nosniff), Referrer-Policy, and Permissions-Policy to prevent clickjacking, MIME sniffing, and unauthorized feature access.
Login is handled via secure magic link email, powered by Supabase Auth. No passwords are stored, transmitted, or at risk of being compromised.
Every database table enforces row-level security. Queries are scoped to the authenticated user. No user can access another user's reports or data.
MQS uses a small number of infrastructure providers. None of them receive your raw file contents. AI-generated narrative sections are produced via isolated API calls that receive only computed scores and field-level metrics, not your source data.
Every user must accept the Data Upload Terms before their first analysis. This is enforced at the application level.
See a four-point summary of data handling practices, a link to the full Data Upload Terms, and a required checkbox confirming their file does not contain protected health information or other prohibited data. The analysis button is disabled until the checkbox is checked.
See a one-line reminder that their upload is subject to the Data Upload Terms and must not contain PHI. No checkbox required on subsequent uploads.
If we make material changes to the Data Upload Terms, all users are required to re-accept the updated terms before their next upload. Acceptance is tracked with a version number and timestamp.
If you have questions about how MQS handles your data, we are happy to help.
info@metadataqualityscore.com