Draft foundation
Data Deletion Instructions
This route gives truthful deletion guidance while self-service deletion tooling, privacy mailbox activation, identity verification, and backend deletion workflows remain pending.
What deletion requests cover
Deletion requests may relate to account information, workspace information, user-provided content, generated content, brand/persona settings, presets, publishing configuration, connected-platform metadata, contact enquiry information, or operational records.
Account deletion
Account deletion tooling is not confirmed in the repository. Users may begin a deletion request through Contact by selecting the Privacy enquiry category.
Workspace deletion
Workspace deletion requires operational implementation and scope verification. OXEFY should confirm the workspace, requester authority, and affected data categories before action.
Content deletion
Content deletion may cover user-provided drafts, source material, stored content assets, or publishing configuration controlled by OXEFY systems, subject to product implementation.
Generated-content deletion
Generated-content deletion may cover drafts or outputs stored by OXEFY-controlled systems. OXEFY cannot promise deletion from third-party platforms or user-exported copies outside its control.
Connected-platform disconnection
Users may disconnect integrations through Vocalis where supported. Users may also revoke access through the third-party platform's own account settings. Revocation may stop future access but may not delete historical content, logs, or provider-held data.
Token or credential revocation
Token or credential deletion behavior depends on product implementation, provider controls, and storage architecture. Users should revoke access through provider settings where available.
Contact-enquiry deletion
The public contact form remains disabled, so no public website form submissions are currently collected by this static site. When submission is activated, deletion handling for enquiry records must be defined before publication.
Operational logs
Operational, security, abuse-prevention, delivery-status, and error logs may have limited deletion behavior because they can be needed for reliability, security, troubleshooting, or legal reasons. Final handling remains pending.
Backups
Backup handling is not finalized. Deletion from active systems may not immediately remove data from backups or provider-managed storage.
Legal and security exceptions
OXEFY may need to preserve limited information where required for security, abuse prevention, dispute handling, legal obligations, or operational integrity. Final exception wording requires legal review.
Request verification
OXEFY may need to verify the requester, account, workspace, product, platform connection, and authority before acting on a deletion request. Do not send passwords, tokens, private keys, payment-card data, or sensitive personal data through general contact.
How to submit a request
Until a dedicated self-service deletion workflow or verified privacy mailbox is activated, users may begin a deletion request through the OXEFY Contact page by selecting the Privacy enquiry category.
What information to include
Include your name, contact address, product or workspace, deletion scope, relevant public URL or review reference if applicable, and enough context for OXEFY to identify the request.
What not to include
Do not include passwords, API keys, tokens, private keys, payment-card data, government ID, health data, or highly sensitive content in a general deletion request.
Expected handling stages
Expected stages may include request intake, verification, scope clarification, system search, deletion or restriction where supported, third-party disconnection guidance, exception review, and completion communication. No handling timeframe is promised in this foundation.
Status and limitations
This route is a public deletion foundation. Automated deletion, privacy mailbox activation, verification workflow, provider-specific deletion behavior, backup handling, and completion notices remain pending operational implementation and legal review.
Expected handling stages
-
1
Request entry through Contact using Privacy enquiry
-
2
Identity and authority verification
-
3
Scope clarification
-
4
System search
-
5
Deletion or restriction action where supported
-
6
Third-party disconnection guidance
-
7
Exception and backup handling review
-
8
Completion communication when operationally supported
Version history
| Version | Date | Status | Change type |
|---|---|---|---|
| 0.1 | 18 July 2026 | Draft foundation | Initial A8 public foundation |
Registered office
Floor No. 6, Ruia Chambers, In front of Amanora Gold Towers, Amanora Park Town, Hadapsar, Pune - 411028, Maharashtra, India.