Skip to main content

Data Retention Policy

Last Updated: January 2025

Overview

This Data Retention Policy defines how long Anchorpipe retains different categories of data. Retention periods are designed to balance service functionality, legal compliance, and user privacy.

General Principles

  1. Minimization: Retain data only as long as necessary for the stated purpose
  2. Compliance: Meet legal, regulatory, and contractual obligations
  3. User Rights: Honor data deletion requests within applicable timeframes
  4. Service Continuity: Retain data necessary for service delivery
  5. Audit and Security: Retain audit logs and security data for compliance and investigation

Retention Periods by Data Category

User Account Data

Data TypeRetention PeriodNotes
Active Account DataWhile account is activeEmail, profile, preferences
Deleted Account Data30 days after deletion requestPersonal data redacted, metadata retained for audit
Authentication DataWhile account is activeOAuth tokens, session data
Account PreferencesWhile account is activeTelemetry, notification settings

Deletion Process: Upon account deletion request, personal data (email, GitHub login, display name) is redacted within 30 days. Account metadata (ID, timestamps) may be retained for audit purposes.

Repository and Test Data

Data TypeRetention PeriodNotes
Test Results30 days (configurable)Raw test results, test runs
Test Run Metadata30 days (configurable)Commit SHA, run ID, framework info
Repository ConfigurationWhile repository is connectedRepository settings, integrations
Aggregated Metrics2 yearsTest scores, trends, analytics

Configuration: Default retention is 30 days. Enterprise customers may configure longer retention periods via environment variables (TEST_RUN_RETENTION_DAYS).

Audit and Security Data

Data TypeRetention PeriodNotes
Audit Logs2 yearsAll audit log entries
Security Events2 yearsFailed logins, rate limit violations, security incidents
Access Logs90 daysAPI access logs, IP addresses
Security Scans1 yearCodeQL, Dependabot, Snyk scan results

Purpose: Audit logs are retained for compliance, security investigation, and legal requirements.

Data Subject Requests (DSR)

Data TypeRetention PeriodNotes
DSR Request Metadata2 yearsRequest ID, status, timestamps
Export Payloads30 days after exportUser data exports (downloadable)
Deletion Records2 yearsConfirmation of deletion, redaction summary
DSR Event Logs2 yearsStatus transitions, operational notes

SLA: DSR requests are processed within 30 days (configurable via DSR_SLA_DAYS).

Communication and Support Data

Data TypeRetention PeriodNotes
Support Tickets2 yearsCustomer support communications
Email Notifications90 daysSent notifications (metadata only)
Telemetry Events30 daysUsage telemetry, event logs
Data TypeRetention PeriodNotes
Legal Documents7 yearsContracts, agreements, legal correspondence
Compliance Records7 yearsCompliance certifications, audit reports
Incident Reports7 yearsSecurity incident reports and resolutions

Data Deletion Process

Automatic Deletion

  • Scheduled Cleanup: Automated jobs delete expired data according to retention periods
  • Cascade Deletion: Related data is deleted when parent records are removed
  • Soft Delete: Some data is soft-deleted (marked as deleted) before permanent deletion

Manual Deletion

  • User Requests: Data deletion requests are processed within 30 days
  • Account Closure: All user data is redacted upon account deletion
  • Legal Requests: Data may be deleted earlier upon legal request or court order

Deletion Verification

  • Confirmation: Users receive confirmation when deletion is complete
  • Audit Trail: Deletion actions are logged in audit logs
  • Certification: Enterprise customers may request deletion certification

Data Archival

Long-Term Storage

Some data may be archived (moved to cold storage) before deletion:

  • Test Results: Archived after 30 days, deleted after 1 year
  • Audit Logs: Archived after 1 year, deleted after 2 years
  • Aggregated Metrics: Retained in aggregated form (no personal data)

Archive Access

  • Read-Only: Archived data is read-only and not accessible via normal APIs
  • Restoration: Archived data can be restored upon request (within retention period)
  • Deletion: Archived data is permanently deleted at the end of the retention period

Special Circumstances

Data may be retained beyond normal retention periods when:

  • Legal Proceedings: Subject to litigation, investigation, or legal process
  • Regulatory Requirements: Required by law, regulation, or government order
  • Contractual Obligations: Required by contract or agreement

Legal holds override normal retention periods and are documented.

Anonymization

Some data may be anonymized (removing personal identifiers) instead of deleted:

  • Aggregated Analytics: Test metrics aggregated without personal data
  • Research Data: Anonymized data used for service improvement
  • Compliance Reporting: Anonymized data for compliance reports

Anonymized data is not subject to data subject rights requests.

Configuration and Overrides

Environment Variables

Retention periods can be configured via environment variables:

  • TEST_RUN_RETENTION_DAYS: Test result retention (default: 30)
  • DSR_SLA_DAYS: DSR processing SLA (default: 30)
  • AUDIT_LOG_RETENTION_DAYS: Audit log retention (default: 730)
  • TELEMETRY_RETENTION_DAYS: Telemetry retention (default: 30)

Enterprise Customization

Enterprise customers may negotiate custom retention periods:

  • Extended Retention: Longer retention for test results or audit logs
  • Shorter Retention: Shorter retention for compliance with specific regulations
  • Custom Policies: Industry-specific or jurisdiction-specific retention requirements

Compliance

This retention policy is designed to comply with:

  • GDPR: Article 5(1)(e) - Storage limitation principle
  • CCPA: Data retention and deletion requirements
  • Industry Standards: SOC 2, ISO 27001 data retention requirements
  • Other Applicable Laws: As required by jurisdiction

Review and Updates

  • Annual Review: This policy is reviewed annually
  • Regulatory Changes: Updated when data protection laws change
  • Service Changes: Updated when service features affect data retention
  • Version History: Changes are documented with version numbers

Contact

For questions about data retention:


Effective Date: January 2025
Version: 1.0