Privacy
Privacy Policy
How DIY Credit Repair handles information used to operate the website and member platform.
1. Information we handle
Depending on the features you use, we may handle account and contact details, membership and transaction metadata, Secure Profile information, generated-document inputs and outputs, case and follow-up records, uploaded supporting files, notification preferences, contact-form information, technical/security logs and credit-data information received through an approved provider connection.
2. Why we use information
Information is used to create and secure accounts, provide paid access, personalise member tools, generate requested documents, maintain cases and reminders, process or reconcile payments, deliver support, prevent abuse, maintain security, operate approved credit-data features and meet legal or regulatory obligations that apply to the service.
3. Secure Profile
Identity and residential-address information entered during protected onboarding is stored in a dedicated encrypted profile workflow rather than being intentionally copied into ordinary WordPress user fields or routine WooCommerce order notes. Some document types may require identity details to appear in the final document where the member chooses to generate it.
4. Generated personalised documents
Generated document records are kept in the protected document workflow so members can review and download their own correspondence history. A document can contain personal information supplied through the Secure Profile and structured generator questions. Members should review a document before sending it to any external recipient.
5. Cases, follow-ups and supporting files
Case Tracker records and supported attachments are maintained in the protected case workflow. Routine service notifications are designed to contain limited operational information rather than reproducing full case evidence or complete credit records in email or SMS.
6. Payments
Membership orders and payment status are handled through WooCommerce and the configured payment integration. Hosted payment flows are used so payment-card entry can occur on the payment provider’s infrastructure rather than in the DIY Credit Repair application. We may retain transaction references and status information needed to activate, reconcile or support membership access.
7. Credit bureau consent and report data
Consent is recorded separately for each configured credit bureau/provider connection. A live credit-data request is not made merely because a member has an account. Where a live integration is approved and used, credit-report payloads are stored in dedicated protected records and access is limited to the relevant member and authorised service administration. Withdrawing consent stops future requests through that consent route but does not automatically erase records that must still be retained for legitimate operational or legal reasons.
8. Contact forms and support
Public contact-form information is used to respond to the enquiry. The contact form is designed not to create a separate searchable database of message bodies. Do not submit passwords, full card details, complete credit reports or other unnecessary sensitive information through the public form.
9. Who may receive information
Information may be disclosed to service providers that help operate the website, hosting, communications, payments or approved credit-data functions; to a recipient you instruct through a generated document or submission workflow; or where disclosure is reasonably required by law, security needs or a valid legal process. Credit-data requests are subject to the applicable provider relationship and member consent.
10. Retention
We keep information for as long as reasonably necessary for the purpose for which it was collected, to provide the service, resolve support or transaction issues, maintain appropriate records and comply with applicable obligations. Different record types can have different retention periods. Where a feature provides a deletion or retention control, that control applies subject to any overriding legal or security requirement.
11. Security
We use technical and organisational safeguards appropriate to the platform, including protected member areas and authenticated encryption for designated sensitive records where supported by the server environment. No internet service can promise absolute security. Members should use strong passwords, protect their devices and report suspected account compromise promptly.
12. Your choices and rights
You may update ordinary account details through available account controls, manage notification preferences, withdraw future bureau consent where that feature is available, and contact us about access, correction or deletion of personal information where applicable. Requests may require identity verification before protected information is disclosed or changed.
13. Cookies and session technology
The website uses strictly necessary cookies or similar browser storage for WordPress/WooCommerce sessions, authentication, checkout, security and saving cookie preferences. Optional functional, analytics or marketing technologies are controlled through the site’s cookie-consent foundation where they are configured. See the Cookie Policy and use Cookie Settings to review or change optional choices.
14. Updates and contact
This Privacy Policy may change as the platform and provider integrations develop. Current wording will be published on this page. For privacy enquiries use the contact details shown above or the Contact page.
Case and follow-up records
When a member uses the case tracker, case details, notes and supporting-file metadata are stored in dedicated protected records. Case notes and case payloads are encrypted at rest. Supporting files uploaded through the tracker are encrypted before storage and are not added to the normal WordPress Media Library. Access to case records remains subject to account authentication and membership controls.
