1. Submit a request
Write from your registered email when possible, identify the account and whether you want account closure, erasure of eligible personal data or a narrower request. Do not include your password, access token, full payment details or unnecessary identity documents. The email action below creates a draft; send it in your email application.
If you cannot access the registered email, explain that to the contact so proportionate alternative verification can be arranged. There is no in-app request status or automatic completion email. Inbox delivery, acknowledgement and staff response are human-operated and have not been tested by sending mail during this phase.
2. Verification and assessment
The operator must verify control of the relevant account proportionately before destructive changes. A signed-in browser alone is not a tested recent-reauthentication deletion flow. Never delete another owner’s records based on a supplied account ID or a shared link.
Assess applicable rights, any specific legal obligation or hold and the scope of eligible erasure. A general assertion that all evidence must be kept is insufficient. Where GDPR applies, the ordinary response period is one month, with lawful extension conditions and explanation; the manual process must meet the applicable rule.
3. Projects, public links and consultation data
A future authorized execution plan must stop relevant public sharing, address project/version/share relationships and assess consultations, feedback and internal notes separately. Submitted snapshots remain separate copies from the source concept; deleting a draft does not automatically erase the consultation snapshot.
Until execution, existing links remain as they were. You can independently revoke a link in My X Stores; that prevents new reads but cannot recover recipients’ copies. Do not assume a prepared deletion email has revoked anything. Retained lawful records must be minimized, restricted and explained.
4. Simulation history, imports and account identity
Eligible owner-linked conversations, decisions, recommendations, settings, job state and import reports must be considered along with account identity. Internal users’ Founder Studio planning records must also be assessed. Immutable import triggers and version/share/consultation dependencies currently prevent a simple reliable bulk deletion. A dedicated authorized erasure operation with transaction safety and audit minimization is required.
After eligible application erasure, authentication identities/sessions must be addressed through the provider’s authorized process; disabling a session is not deletion. Local drafts and preferences on your devices and third-party recipient copies are separate. Do not promise removal from other people’s browsers.
5. Retention, backups and completion
No operational retention schedule has been approved or activated. Proposed criteria are purpose completion, confirmed account closure, specific statutory duties and time-limited security needs. Automated expiry, legal holds and backup/restore safeguards still need approved design and implementation.
The operator should confirm what was erased or anonymized, retained categories and their legal reasons/criteria, remaining copies/backup limitations and complaint options. No automatic completion notification exists. During Phase 3.4 no existing customer, founder, test, import or recommendation record is deleted.
This opens a draft in your email application; nothing is submitted until you send it. No account or data is automatically deleted. If no email application opens, write to the contact below. Receipt, identity verification and completion are handled manually; there is no in-app request tracker or automatic completion notice.
Legal & privacy contact
Nikolov.n.ivaylo@gmail.com- Operating legal entity
- Founder confirmation pending
- Company registration number
- Founder confirmation pending
- VAT number, if applicable
- Founder confirmation pending
- Registered office
- Founder confirmation pending
- Applicable jurisdiction
- Founder confirmation pending
- Data Protection Officer, if required and appointed
- Founder confirmation pending
Legal review required
Operator identity, lawful bases, retention, transfers, eligibility, liability, jurisdiction and the Bulgarian legal wording require qualified legal approval. This draft is not a compliance certification.