Account and Data Deletion

Overview

This page explains the current Creaters account and data deletion workflow. It covers how to request deletion, the 7-day grace period, cancellation, what changes after final deletion, and why some records may be retained in anonymized or admin-only form.

Deletion is designed to remove or anonymize personal account identifiers while preserving limited records needed for founder protection, abuse investigation, support, disputes, audit trails, legal compliance, and service integrity.

Before You Request Deletion

Review your projects, applications, files, profile, contact visibility, and connected accounts before requesting deletion. If you need copies of your own information, collect them before the grace period ends.

If you are a founder, consider closing or updating active projects and roles before requesting deletion. Deletion may hide founded projects from public discovery and can affect applicants who interacted with those projects.

If you are an applicant, remember that founders may already have seen information you submitted before deletion. Creaters cannot delete copies that another member saved outside Creaters systems.

How to Request Deletion in the App

Sign in, open your profile page, and use the account deletion control. The product may ask you to type a confirmation phrase before scheduling deletion so accidental deletion requests are less likely.

The deletion request applies to the signed-in account owner. It does not automatically delete records Creaters must retain for safety, security, dispute, abuse-prevention, audit, or legal reasons.

If you cannot access your account, contact support@creaters.org from the email address associated with the account and include enough context for ownership verification.

7-Day Grace Period

After you request deletion, the account enters a 7-day grace period. During this period, the account remains usable so you can cancel the request if it was accidental or if you need to finish exporting information.

The profile page shows the pending deletion state and scheduled deletion date when the account is eligible to display those controls. You should not rely on reminders outside the app unless Creaters separately sends them.

Creaters may pause or review deletion finalization if there is an active abuse investigation, security issue, legal request, support dispute, or operational incident that requires careful handling.

How to Cancel During the Grace Period

Sign in before the grace period ends, open your profile page, and use the cancellation control. If cancellation succeeds, the pending deletion request is marked canceled and normal account behavior resumes.

If you cannot access your account during the grace period, contact support promptly from the account email. Support may require verification before canceling a deletion request.

After final deletion has run, cancellation may no longer be possible. Creaters may need to treat later requests as support, recovery, or data-review requests rather than simple cancellation.

What Happens After Final Deletion

After the grace period, Creaters finalizes deletion through an administrative workflow. The workflow can anonymize profile identifiers, clear or hide private contact fields, remove or anonymize connection records, hide founded projects from public discovery where controlled by the workflow, and prevent new founder-facing document access for deleted users.

Final deletion is not the same as dropping every historical row from every system. Some records may remain in anonymized, limited, or admin-only form so Creaters can understand past actions, protect users, investigate abuse, handle support, maintain audit trails, or comply with legal obligations.

Backups, infrastructure logs, security logs, and provider records may persist for a limited period according to operational retention needs and provider behavior.

Profile Effects

Your public profile should no longer present your active personal identity after final deletion. Profile identifiers may be anonymized or marked as deleted where practical.

Public profile fields such as display name, biography, avatar, contact fields, LinkedIn, GitHub, portfolio, and Telegram may be removed, hidden, anonymized, or made inaccessible according to the deletion workflow.

If another user previously saw or copied your public profile information, Creaters cannot remove their off-platform copies.

Project and Role Effects

Founded projects may be hidden from public feeds, sitemap-driven discovery, public profiles, and role discovery where the deletion workflow controls those records. Active role listings under deleted-founder projects should not continue as normal public opportunities.

Some project or role records may remain internally so Creaters can preserve application history, review past actions, investigate abuse, resolve disputes, or maintain platform records.

If project links, repository links, or public project details were shared outside Creaters, Creaters cannot delete external copies or content hosted by third-party services.

Application and Review Effects

Applications may be anonymized instead of hard-deleted. This lets Creaters preserve a limited record that an application existed, what status it reached, and why a founder's dashboard or historical workflow changed, without continuing to expose the deleted user's personal identifiers.

Founder review history, application status, match history, close-listing records, and abuse or support evidence may be retained where necessary for founder protection, user safety, audit trails, or dispute handling.

Applicant contact fields and private profile details should be removed, hidden, or anonymized where practical after final deletion.

Connection Effects

Connection requests involving a deleted account may be removed, anonymized, canceled, or retained in limited form depending on the status of the request and the reason records are needed.

Accepted connections do not automatically grant permanent access to private contact details after deletion. Creaters should prevent new in-product disclosure of deleted-user private contact details where the deletion workflow controls access.

Resume/CV and File Handling

Resume/CV files submitted with applications may be retained admin-only after final deletion for founder protection, abuse investigation, appeals, disputes, audit trails, and legal compliance. This policy is intended to prevent a deleted account from erasing evidence needed to understand prior application activity.

Founders and public users should not receive new signed links to deleted-user Resume/CV files after final deletion. Authorized file access should stop for ordinary product users once the account is finalized as deleted.

To request manual review or removal of a retained Resume/CV or contact screenshot, contact support@creaters.org from the account email where possible. Creaters may need to retain a file if removal would create safety, legal, audit, or dispute risk.

Contact, Support, and Email Records

Contact submissions, support messages, email delivery events, webhook records, and operational logs may be retained after account deletion if they are needed for support continuity, abuse investigation, deliverability troubleshooting, security, audit trails, or legal compliance.

Creaters may anonymize or minimize support records where practical, but support records often need enough context to explain what happened and who was authorized to request a change.

What May Remain

After deletion, Creaters may retain anonymized application history, project workflow records, rate-limit events, security logs, audit records, email delivery events, provider logs, backups, and admin-only retained files where necessary.

Creaters may also retain records required to enforce these terms, prevent banned users from returning under another identity, investigate fraud or abuse, protect founders and applicants, or comply with legal obligations.

Retention does not mean the information remains public. The goal is to reduce public and ordinary user access while preserving limited records needed for legitimate operational reasons.

Manual Requests and Expected Timeline

Most in-app deletion requests enter the 7-day grace period immediately. Finalization normally happens after the grace period through the scheduled administrative workflow.

Manual requests sent to support may take longer because Creaters must verify account ownership, understand the scope of the request, check for safety or legal conflicts, and coordinate any file-specific review.

When contacting support, include the account email, the request type, relevant project or application references if known, and a concise explanation. Do not include passwords or service-role keys in support messages.

Limits of Deletion

Creaters cannot delete data stored outside Creaters systems, such as screenshots, downloaded Resume/CV files, copied profile text, email inbox copies, browser caches, search engine caches, external repository content, or messages sent off platform.

Search engines and social platforms may take time to refresh snippets, cached pages, icons, or previews even after Creaters updates or removes public content.

Some deletion requests may be limited, delayed, or denied where Creaters has a legitimate need or legal obligation to retain records.