Data Use

This Data Use Policy provides full technical transparency regarding how academic manuscripts, digital quotas, and user records move through Turnitin Connect's systems.

1. Stateless RAM Scanning Engine

When you upload a document (.pdf) for similarity and AI detection checking, the payload is held exclusively in volatile RAM on our routing instances. The text is parsed, evaluated against similarity heuristics, and immediately discarded upon report transmission. No copy of your document is ever committed to secondary storage or added to any institutional repository.

2. AI Score Reduction Pipeline & 24-Hour Ephemeral Retention

Manuscripts submitted for the AI Score Reduction & Human Paraphrasing service follow an isolated, high-security workflow:

• Format Requirement: Exclusively .docx files are accepted to safeguard embedded citation codes, bibliography structures, and tables.
• Encryption: Files are stored at rest using AES-256 encryption within a private, air-gapped storage bucket accessible only by authorized academic editors assigned to your order.
• Strict 24-Hour Automated Purge: 24 hours after completion and delivery, our automated cleanup daemon permanently purges the original file, working drafts, and verification PDFs from all storage disks and backup snapshots.

3. Data In Transit

All network communication between client devices and Turnitin Connect edge endpoints uses TLS 1.3 encryption with strict Perfect Forward Secrecy (PFS). Unencrypted HTTP traffic is automatically dropped.

4. Telemetry and Operational Logs

We record non-identifying telemetry (such as HTTP response codes, scan durations, and character counts) solely to balance server load and maintain infrastructure health. We never log or store extracted body paragraphs in operational metrics.

5. Strict No-Refund Policy on All Services