Privacy policy

1. CONTROLLER AND CONTACT DETAILS

The controller for the TPS website, pre-checkout assent records, private buyer pages, renewal quotations, support-and-updates entitlements, license generation, personalized delivery, security records, and product support is Sistemas de Computación Accesibles del Noroeste, S.C. ("SCA"), La Cieneguita 37, Col. Santa Fe, C.P. 83249, Hermosillo, Sonora, México; privacy requests privacidad@sca.mx; product and order support tpsrep@sca.mx.

The exact Dodo Payments entity identified in hosted checkout and on the receipt acts as merchant of record and separately processes checkout, billing, tax, fraud-prevention, payment, invoice, refund, and dispute information under the notice displayed by Dodo. SCA does not receive complete payment-card details.

2. PRODUCT PROCESSING AND SERVICE BOUNDARY

TPS Repair reads files selected by the user and processes them locally on the user's Windows computer. The product has no telemetry and does not send file contents, records, field values, filenames, or recovered output to SCA. It does not need to contact SCA to run.

SCA does not provide TPS-file repair, recovery, migration, forensic analysis, or customer-data consulting through the website. The site and support workflow do not offer a customer-content upload function. Product support is limited to delivery, installation, licensing, ordinary operation, and non-content diagnostics.

3. INFORMATION SCA PROCESSES

Public-site and consent data Examples: Language, first-party analytics preference, and, only after consent, limited GA4 events and device/browser context Purpose: Operate the site, remember the visitor's choice, and measure aggregate public-page use

Initial checkout and buyer data Examples: Tier, country, buyer type, transaction email, confirmed Licensee display name, organization name, assent text/version/hash, timestamp, and secure checkout-intent identifiers Purpose: Present the correct offer, record assent, prevent fraud or duplicate fulfilment, and deliver the license

Original order and license data Examples: Dodo order/payment reference, product, base/reference amount, charged amount and currency, tax, public license identifier, build identifier, software version, signing/hash evidence, delivery and download events Purpose: Reconcile payment, generate and deliver the licensed build, administer the perpetual license, and maintain transaction evidence

Personalized build archive Examples: Exact issued product archive, product version, issue/delivery and entitlement source, object identifier, archive and component hashes, version-specific legal-bundle reference, availability or withdrawal status Purpose: Preserve replacement copies and allow redownload of versions previously validly issued

Private buyer-page data Examples: Hashed access token, token status/rotation, access time, limited security and request data, complete issued-build list, build status, current entitlement dates, and latest generally available version Purpose: Provide secure buyer access to previously delivered builds and renewal information

Renewal quote and entitlement data Examples: Original Renewal Basis Amount, percentage tier, USD quote amount, quote creation/expiry, proposed coverage dates, accepted legal versions, Dodo session/payment binding, charged amount/currency/tax, extension ledger, refund or reversal status Purpose: Calculate and display the Support & Updates Renewal, prevent customer-controlled pricing, verify payment, extend coverage once, and preserve an audit trail

Support and complaints Examples: Contact details, public license identifier, software and Windows version, exact error text, content-free diagnostic code, correspondence, and resolution Purpose: Provide in-scope product support and handle complaints or legal remedies

Privacy and legal requests Examples: Identity/contact details, request, verification evidence, response, and legal hold information Purpose: Authenticate and respond to rights requests and comply with law

Do not submit TPS files, recovered data, customer databases, credentials, screenshots containing confidential data, or other customer content through email or support. SCA has no customer-content intake service.

4. GOOGLE ANALYTICS 4

On an allowlist of public marketing or informational pages, SCA may use Google Analytics 4 (GA4) for aggregate performance and conversion-interest measurement. GA4 is implemented using Basic Consent Mode: the Google tag is not requested, GA cookies are not set or read, and no analytics event is sent until the visitor selects Accept analytics. Rejecting, ignoring, or withdrawing consent leaves analytics disabled.

GA4 is excluded from legal snapshots, checkout review, private buyer pages, renewal quotations, hosted checkout, payment return, order status, license management, download, delivery, support, complaints, and privacy-request routes. SCA disables Google Signals, advertising personalization, remarketing, Google Ads linking, User-ID, user-provided data, and automatic Enhanced Measurement. The implementation does not send names, emails, transaction or license identifiers, prices, currencies, personalization values, URL queries/fragments, filenames, file contents, or free-form text.

5. PURPOSES AND LEGAL BASES

SCA processes transaction, assent, licence, entitlement, renewal, delivery, hosted build-archive, and support information as necessary to take requested pre-contract steps, perform the applicable contract, administer the perpetual license and time-limited entitlement, provide replacement access to versions previously delivered, provide support, prevent duplicate or fraudulent fulfilment, and handle remedies. Security, accounting, tax, compliance, and claim records are also processed to satisfy legal obligations and SCA's legitimate interests in protecting the service and establishing, exercising, or defending legal claims. Optional GA4 processing is based on consent and is not required to evaluate, purchase, renew, download, or use TPS Repair.

6. RECIPIENTS, PROCESSORS, AND INTERNATIONAL PROCESSING

Relevant data may be processed by Dodo Payments as merchant of record; Microsoft Azure services used by SCA for private hosted storage and related infrastructure; email-delivery, domain/DNS, security, code-signing, logging, and support providers engaged by SCA; Google only after analytics consent on allowed pages; and professional advisers, authorities, or courts where legally required. The development team must replace generic provider descriptions with the exact contracted entities, service regions, and transfer safeguards before publication.

Some providers may process information outside Mexico or the visitor's country. SCA uses applicable contractual, statutory, or adequacy mechanisms and limits disclosures to what the service requires. The final provider inventory and international-transfer section must match signed contracts and production configuration.

7. RETENTION

- Analytics preference: normally 180 days or until changed; GA4 event retention: the shortest configured period that meets the documented aggregate-measurement purpose. - Expired, unused renewal quotes and their security bindings: normally 12 months after expiry, unless a shorter fraud/security window is sufficient or a legal hold applies. - Perpetual license and entitlement ledger: for the life of the license plus the applicable claims, tax, accounting, and evidentiary period. - Accepted legal versions, transaction evidence, payment reconciliation, refunds, reversals, and renewal extensions: for applicable tax/accounting and limitation periods, with periodic review. - Hashed private-page tokens: while active and for a short revocation/security period afterward; private-page access logs: normally up to 12 months unless security needs justify a different period. - Personalized build archives and historical versions: there is no fixed scheduled deletion date while the related perpetual license remains valid and SCA continues operating the hosted redownload service. This retention supports replacement after device loss or replacement and access to versions previously validly delivered. An archive may be removed earlier after a full refund or reversal, license termination, a verified buyer deletion request, a security or integrity problem, a legal or third-party-rights restriction, or discontinuation of the hosted service. - Support records: normally three years after closure, unless a shorter period is sufficient or a claim/legal obligation requires longer retention.

Retention is reviewed by category. The purpose for retaining personalized archives is the hosted redownload service, not the low cost of storage. When that purpose or the related license ends, SCA deletes or blocks the artifact as appropriate while retaining only the minimal transaction, license, tax, legal-assent, hash, and audit records needed for the applicable contractual, legal, accounting, claims, or evidentiary period.

8. SECURITY

SCA uses role-limited access, encrypted transport, its existing private Microsoft Azure storage, time-limited per-file download links, hashed and revocable private-page tokens, webhook signature verification, idempotency, server-side payment reconciliation, audit logging, code signing and hash checks, and separation of public analytics from customer-specific routes. No security measure eliminates all risk.

9. RIGHTS AND CHOICES

Depending on applicable law, a person may request access, rectification, cancellation/deletion, objection, restriction, portability, withdrawal of consent, or review of a decision. Send requests to privacidad@sca.mx with enough information to locate the record and verify authority. Withdrawal of analytics consent does not affect processing already carried out lawfully or transaction records SCA must retain.

A buyer may also ask SCA to delete hosted personalized archives associated with the buyer. Deletion ends the hosted redownload convenience but does not remotely disable copies already installed or change the perpetual license. SCA may retain the minimal transaction, license, legal-assent, tax, accounting, claims, and audit records that remain necessary or legally required.

For Mexican ARCO requests, SCA will communicate its determination within twenty days after receiving a complete request and, when granted, implement it within the following fifteen days, subject to lawful extensions and exceptions. Other jurisdictions may provide different time limits and complaint rights. A person may also complain to the competent data-protection authority.

10. CHILDREN AND CHANGES

TPS Repair is a professional utility and is not directed to children. SCA does not knowingly seek children's personal information through the site. Material changes are versioned and dated. A later notice applies prospectively; transaction and assent records retain the notice version applicable at the relevant time.

11. CONTACT

Sistemas de Computación Accesibles del Noroeste, S.C. La Cieneguita 37, Col. Santa Fe, C.P. 83249 Hermosillo, Sonora, México Privacy requests: privacidad@sca.mx Product and order support: tpsrep@sca.mx For Solo Consultant licenses we also collect the designated operator name, retain protected operator assignment and replacement records, and include that name in personalized license information and delivery. We use this information to administer the single-operator license and support permanent replacement requests. The retention, access, security, and rights provisions above apply to these records.

Version 1.4 · Effective 19 September 2026