Retention principle
Records should be kept only for appropriate business, legal, security, support, accounting, operational or compliance purposes and should not be kept longer than reasonably necessary for those purposes.
Website enquiries
Website enquiry records may be retained to respond to the enquiry, manage follow-up, keep business history, handle disputes, protect security and comply with legal or accounting requirements.
Technical logs
Technical logs may be retained for security, debugging, performance monitoring, fraud prevention and service reliability. Retention should be proportionate to the risk and operational need.
Valid idle enquiry rate-limit records become eligible for deletion after 24 hours and are checked by an hourly maintenance sweep. Active, malformed or unsafe records are retained for review. This schedule applies to abuse-prevention counters; it does not set the retention period for enquiry tickets, correspondence or other service records.
Customer records
Customer service records, contracts, invoices, support history and platform data should follow the applicable agreement, legal duties, retention schedule and data processing terms.
Deletion requests
Deletion requests can be reviewed where lawful and appropriate, subject to identity verification, contractual duties, legal retention, security needs, backup limitations and legitimate business requirements.
Backups and archives
Deletion from active systems may not immediately remove information from backups, logs or archives. Backup deletion usually follows normal backup rotation unless a specific technical and legal process applies.
Retention examples
Different records may need different retention periods. Enquiry messages, invoices, contracts, support tickets, technical logs, security records and customer data exports may each have separate retention reasons and review cycles.
Customer exports
Where a customer requires data export before cancellation or deletion, the request should be made before access ends and should be handled according to the service agreement, technical feasibility and data protection requirements.