Security

Security is the foundation of Turnitin Connect. We understand that your source text is your most valuable asset, and we have implemented industry-leading security practices across our entire infrastructure to protect it.

1. Encryption

All data in transit between the Turnitin Connect application and our routing servers is encrypted using TLS 1.3 with strong cipher suites. Any metadata stored at rest on our servers is encrypted using AES-256 encryption.

2. Local Indexing & Zero Repository Architecture

When scanning documents for similarity, our stateless RAM engine ensures no submission files are indexed or saved to external databases. Your documents will never be discovered or cited by future Turnitin institutional scans.

3. Authentication and Access Control

We use secure, modern authentication protocols powered by Supabase. Your passwords and OAuth tokens are never exposed to Turnitin Connect developers. Access to production databases is restricted to core engineering leads via secure VPNs and hardware security keys.

4. AI Score Reduction: 24-Hour Ephemeral Security Pipeline

Manuscripts submitted for human paraphrasing (supported exclusively in .docx format) receive specialized security protections:

• Air-Gapped Access: Only the verified academic editor assigned to your manuscript can access your working document under strict non-disclosure obligations.
• Automated 24-Hour Purge: Our immutable storage daemon permanently destroys all source files, working drafts, and Turnitin verification reports exactly 24 hours post-delivery.

5. Strict No-Refund Policy & Fraud Prevention

6. Bug Bounty Program

We maintain an active, private bug bounty program with independent security researchers to continually audit our infrastructure. If you believe you have discovered a vulnerability, please contact security@turnitinconnect.com for responsible disclosure guidelines.