FixingLog – Erasure and individual requests
Send a request: [email protected]
1. Where to send a request
For platform accounts, business declarations or FixingLog subscription details contact [email protected], preferably from the account email. Identify the information and action requested. Do not send passwords, full card details or unnecessary identity-document copies. For a professional’s customer/work record, contact the controller named on the reporting page first; FixingLog assists on their instructions. We help identify the appropriate controller if a request is misdirected. Professionals may also start automated deletion under “Delete profile” on the Profile page. Opening the email alone does not erase anything: sign-in and separate confirmation are required. Expired links cannot be reused.
2. When erasure can be requested
Grounds include information no longer being necessary, withdrawal of the sole consent basis without another lawful basis, unlawful processing, a legal deletion obligation, or a valid objection without overriding lawful grounds. Requests may accompany account closure or concern particular records only. Grounds and exceptions are assessed by data category.
3. Response and identification
We act without undue delay and normally provide information about action taken within one month of receipt. Complexity or the number of requests may justify up to two further months, with reasons given within the first month. This is not an automatic three-month waiting period. Where identity is uncertain we request only necessary proportionate verification. Requests are normally free of charge. Manifestly unfounded or excessive requests are handled only under the applicable legal conditions with reasons.
4. Workspace information
Subject to authority and necessary-retention checks, a request may cover profiles, customer/work records, notes, equipment, maintenance, images, attachments, PDFs and exports. Review covers the active database and MinIO/S3 object storage. A single account’s request does not authorise deleting other controllers’ or linked staff’s lawful records. Completion and failures are checked; remaining storage copies are not treated as erased. Anonymisation replaces erasure only if genuinely irreversible.
5. Invoices and other retention exceptions
Flowmind Kft. retains its own invoices, accounting evidence and necessary supporting information for at least 8 years under section 169 of the Hungarian Accounting Act, including invoices held in Billingo. Closing an account does not destroy them. GDPR Articles 6(1)(c) and 17(3)(b) may require this necessary retention. Information necessary to establish, exercise or defend documented legal claims may be retained to a limited extent under Article 17(3)(e). This does not authorise unlimited retention of the whole workspace. Any partial refusal identifies the data, reason, basis and period or criteria for retention.
6. Backups and external copies
Backups are held at Hetzner; a final retention cycle has not yet been specified. Erasure handling therefore requires clarifying affected backups and a concrete removal deadline. Recovery copies are not used for ordinary business processing and prior erasures must be reapplied after restoration. We send processors deletion instructions as necessary. Emails, images and PDFs already delivered to recipients cannot be recalled from their devices/mailboxes by FixingLog; recipient lawful bases and retention require separate consideration. Stripe may retain certain payment and legal information under its own controller obligations.
7. Cancellation, export and the 30-day deadline
Ordinary subscription cancellation, access restriction and permanent profile deletion are separate actions. The 30-day export/deletion review after cancellation does not itself perform automatic full erasure. Permanent account deletion can be requested separately from the profile: after entering the account email, a confirmation link valid for 30 minutes is sent, followed by a separate confirmation button used while signed in. Account access is then disabled. Processing first checks and terminates the linked Stripe subscription, then erases the own workspace database and object-storage records. Failure is not reported as successful deletion: processing retries and the administrator receives a highlighted task-list warning. Completion is shown only after verified execution. Mandatory accounting information and backups follow separate retention rules. Automated account deletion does not limit GDPR request rights or response periods. Exports are available for up to 7 days and three successful downloads; exports of an erased workspace are also removed.
8. Other rights and remedies
You may also request access, rectification, restriction and, where applicable, portability, or object to legitimate-interest processing. Restriction may be appropriate while lawfulness is disputed. Where a request is refused we explain why and describe supervisory complaints and judicial remedies. NAIH: https://naih.hu, or another competent authority. Prior support contact is not a condition for regulatory or court remedies.
9. Teams and processing records
Deleting a team owner also erases their own team workspace, but not members’ accounts. Memberships and outstanding invitations end. Without an appropriate own subscription or another active team, detached professionals are suspended similarly to expired trials; detachment does not start a new trial. A member’s account deletion does not authorise erasing another controller’s workspace; access links and assignments may be reassigned while business records remain. Processing stores the necessary temporary account reference, confirmation/execution times, phase, attempt count and non-content error code. After success, the task’s account reference is cleared; the random receipt reference and progress are available for up to 7 days from completion, then removed by maintenance. Incomplete failed tasks remain until resolved. Only necessary financial references and invoice data are retained for late Stripe events without creating another platform account.
Version: 2026-10-20-v25