Retention & Deletion Policy
Current record handling and how to request exports or deletion. Expiration, cancellation, archive status, and deletion are different events.
1. Retention principles
We retain information for the agreed workflows, lawful Customer instructions, security, accounting, disputes, and legal requirements. Shops set their own recordkeeping needs for repairs, warranties, tax, payment disputes, employment, signatures, and communications. The platform is not a permanent archive and does not replace independent records. We do not state fixed seven-year billing, three-year support, twelve-month audit, or universal thirty-day backup periods as implemented facts.
2. Current handling by category
| Category | Current behavior and important limits |
|---|---|
| Customer, repair, inventory, transaction and field-service records | Kept for the active business workflows. Available edits/deletes vary by record. Linked sales, signed records, audit evidence, and dependencies can prevent a simple permanent deletion. No universal timed deletion after cancellation is currently promised. |
| Signatures, authorizations, SMS consent and communication history | Retained as business/evidence records. A pending repair signing link ordinarily expires after 12 hours; the underlying request/signature and audit records remain. Communication history has integrity protections and requires assisted handling for a lawful deletion/redaction request. |
| Repair photos and message media | Stored with the relevant records in configured storage. Removing a database record does not establish that every underlying file or outside-provider copy was removed. Assisted verification can be needed. |
| Support tickets and attached photos/videos | Kept with ticket/reply history. Closing or archiving a ticket does not erase it. Unsubmitted staged uploads have a 24-hour expiry; cleanup is triggered during later upload processing and is not an exact deletion-at-24-hours guarantee. |
| Device-repair CSV imports | The current generic import handler processes the uploaded source in memory; imported rows become Customer Data. This is not a promise about every import feature or provider diagnostic. |
| Field-service CSV/XLSX staging | Parsed rows/samples can be kept in database staging. Configured background cleanup clears eligible old uncompleted batches; applied/rolled-back history is handled separately. Do not assume the source-derived rows disappear when the upload request ends. |
| Sessions, reset/invitation/signing tokens and security logs | Access tokens/challenges expire for security. Expiry does not necessarily purge the stored record. Security/acceptance/audit records can remain for investigation and accountability, subject to lawful retention review. |
| Website leads and correspondence | Demo requests and other emails are kept in delivery/mailbox/support systems while needed for the inquiry, relationship or a lawful recordkeeping reason. Contact us to request removal from our own lead/correspondence records. |
| Browser drafts and optional offline cache | Some drafts and preferences are kept in local/session storage; offline field-service records can remain encrypted in IndexedDB. Access expiry is not byte deletion. Use explicit removal controls and secure or clear devices that will be reassigned. |
| Backups and provider-held records | Recovery copies and independent provider records have their own configurations and obligations. We do not promise one confirmed age-out period for every database, file, mailbox, queue, and external vendor. Retained copies must remain protected and used only for a permitted purpose. |
3. Exports and ending service
Export needed records while the account is active. Current device-repair exports cover selected customer, repair, and inventory data; they are not a complete archive of signatures, messages, photos, payments, and every setting. Field-service/accounting reports have their own scopes. Ask support for a return plan if available exports do not satisfy a lawful requirement.
When canceling or requesting deletion, contact us promptly to agree the required scope, format, access, and completion plan. We do not promise a universal thirty-day post-termination export window or a specific restoration service. Any custom migration fee must be agreed in advance where permitted; it does not remove legally required data assistance.
4. Requesting deletion or correction
A signed-in user can initiate deletion of their own login account in the Security Center under Delete my login account. Confirm the current password and submit the request in the app; no email or support conversation is required to initiate it. The request status and completion deadline are shown there. If your workspace subscription is inactive, choose Account deletion on the sign-in screen and verify your password and two-factor authentication; you do not need to renew or reactivate the subscription to initiate or view your request. We complete account-deletion requests within 30 calendar days and provide a completion confirmation and an explanation of any information retained for a legal reason. An authorized owner may separately email admin@techonefixpos.com about business/workspace records, corrections, or other requests. We verify authority, identify linked/protected records and outside storage, and determine applicable deadlines and lawful preservation requirements. Individuals with a shop’s records should contact that shop first; it may instruct us under the DPA.
Account deletion is manually fulfilled after in-app initiation; submitting a request does not immediately erase data, cancel the business subscription, or authorize deletion of the subscribing business or all its customer, repair, sales, financial, or consent records. We remove the login account and associated personal data that we are not legally required to retain. Business-record requests and continuity of authorized access are handled separately. We will provide the request outcome, describe permitted exceptions, and arrange required return/deletion. Restrictions designed to protect financial or consent evidence may need scoped redaction, anonymization, or other lawful handling. They do not mean every privacy request must be refused.
5. Limited preservation and completion
A legal obligation, valid hold, necessary fraud/security investigation, payment dispute, or other legally permitted purpose can require limited preservation. We explain the basis and retained categories where allowed, restrict access/use, and review the need when the reason ends. Opt-out records may be retained to prevent renewed unwanted messages. De-identified statistics may remain if not reasonably linked to a person and maintained as de-identified.
Completion must address the relevant database, file, support, mailbox/provider, and recovery systems, not only removal from a screen. If a backup is restored, applicable deletion instructions must be re-applied as required. External payment/carrier providers may independently retain their records under their own legal duties. No statement here guarantees immediate erasure from every third-party system.
6. Contact
TECHONEFIX POS LLC
PO BOX 543
Red Boiling Springs, TN 37150, United States
admin@techonefixpos.com
Voicemail recordings
Where voicemail is enabled, an authorized user can request deletion of an available recording. The service verifies its association, requests deletion from the recording provider, and marks the voicemail deleted. Related call, association, status, and audit information may remain for the purposes described in this policy. We do not promise an automatic audio or provider-backup deletion period that has not been verified.
