Data Retention & Deletion Policy
This Policy explains how retention and deletion should be defined for website inquiries, project records, application accounts, uploaded files, business data, logs, backups, and AI-assisted workflows.
1. Retention principle
Information should be retained only for as long as reasonably necessary for the contracted workflow, active support, security, accounting, legal compliance, dispute handling, backup integrity, or another documented business purpose.
2. Project records
Contracts, statements of work, invoices, approvals, acceptance records, change orders, security records, and business correspondence may be retained longer than operational application content because they support legal, tax, accounting, warranty, and dispute obligations.
3. Uploaded files
Documents, images, photos, voice files, transcriptions, forms, attachments, and other uploaded content should follow a project-specific lifecycle. Temporary processing files may be deleted sooner than system-of-record data.
4. Operational business data
Tasks, reports, CRM data, inventory records, maintenance information, and other workflow data should have retention rules aligned with the client’s business requirements. Elqorin Pocket does not assume one universal retention period for every application.
5. Account deletion
Where an application supports account creation, the project should include a process for account deletion when required by Apple, Google, applicable privacy law, or client policy. Requests may require identity verification and may not erase records that the business must legally retain.
6. Logs and security records
Application, access, error, and security logs may be retained for troubleshooting, security, audit, and incident-response purposes. The appropriate retention period depends on the risk and operational needs of the project.
7. Backups
Deleted data may remain temporarily in protected backups until those backups expire or are overwritten through normal cycles. Backup copies should not be restored for ordinary business use after a valid deletion request except where necessary for recovery, legal obligations, or security investigation.
8. AI provider retention
When cloud AI services are used, provider logging, abuse-monitoring, retention, and training settings must be assessed for the selected provider and service tier. No universal “zero retention” or “no training” statement should be made unless it is supported by the actual configuration and contract.
9. End of service
At the end of an engagement, the applicable agreement should determine whether client data is returned, exported, transferred, deleted, or retained for a limited transition period.
10. Deletion requests
Requests should identify the relevant application, client business, account, data category, and desired action. Where Elqorin Pocket processes data for a client, the request may need to be handled by that client as controller.
Company contact information
EMAIL: projects@elqorinpocket.com
ADDRESS: 7950 W Colfax Ave, Lakewood, CO 80214
PHONE: +1 860 846 7486