1. Available and Planned Methods
The owner has selected both self-service export and support-assisted privacy requests as the target model. After implementation and testing, an eligible user should be able to obtain the personal data they are entitled to in a reasonably portable format. An authenticated in-app flow may provide structured account/message metadata (e.g., JSON or CSV as technically suitable) and eligible individually owned AVENZERS-managed files as downloads or an archive.
The current codebase has not been verified to offer that complete self-service export workflow. Until it is available, users may submit requests at support@avenzers.tech. We aim to respond to standard privacy requests within 30 days, or sooner where applicable law requires; justified extensions and exceptions are handled under that law. The available contents and export format will be explained based on actual systems.
2. Scope and Rights of Others
Export requests must respect authorization, contractual ownership and other people's privacy. Eligible categories may include profile/account records, applicable messages the user is entitled to access, their owned file metadata, connection descriptors and their personally owned AVENZERS-managed files. Other participants' private content, confidential organization-owned resources, privileged internal security logs, secrets and information legally prohibited from disclosure are excluded or redacted as necessary.
An organization may independently request its own data through a verified authorized representative under its service arrangement. Participation in an organization does not make every organization-owned file the personal property of an individual member.
Original Google Drive or other connected-provider files remain at the provider. An AVENZERS personal-data export does not imply wholesale export of those external originals. Use the provider's own export/download mechanisms where appropriate, and review the provider's terms.
3. Identity, Security and Delivery
We may verify identity, account ownership and, for organizational data, the requester's authority before preparing an export. Do not send passwords, OAuth tokens or full payment details in a request. Export packages should be delivered through authenticated, short-lived access with proper access controls, not unprotected public links.
4. Before Deleting Your Account
Users who want a copy should request/export it before completing account deletion. Under the approved future deletion model, access ends immediately after accepted deletion, with no recovery window. Retained messages in other users' conversation histories and continuing organization-owned resources follow the Data Deletion Policy. Export availability cannot be implied after an account has ceased to exist.
5. Local Rights and Limits
Access, portability, deletion and response rights depend on applicable data-protection laws. This document does not invent a universal right to all provider records or require disclosure of other persons' personal data. Questions and lawful appeals: support@avenzers.tech.