aiella.my
Privacy policy
How Ella handles data, and Google user data in particular.
Last updated 6 September 2026
1. What Ella is
Ella is a private AI executive assistant run on a single private server for one person. It is not a public service. There is no registration, no other users, and nothing here is offered to the public.
"We" below means the operator of that server. Contact: aiellamy90@gmail.com.
2. Whose Google data is accessed
Ella signs in to Google as her own account only — the account that installed her. She does not request or receive access to any other person's Google account.
3. What is accessed, and why
-
gmail.modify— reads messages in her own mailbox so she can understand what has been received, sends replies and meeting invitations on her principal's behalf, and applies labels or moves messages to Trash to keep the mailbox organised. This permission cannot permanently delete mail. -
drive.readonly— reads files that have been shared with her account, so she can refer to documents she is asked about. -
drive.file— creates and edits only the files she creates herself. It gives no access to any other file in Drive.
No broader scope is requested. In particular Ella does not request
https://mail.google.com/, which would permit permanent deletion.
4. Limited Use
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Google Workspace APIs are not used to develop, improve, or train generalized AI and/or ML models.
Concretely, that means Google user data obtained through these scopes is:
- used only to provide the assistant features described above;
- never sold, rented, or used for advertising or ad profiling;
- never used to train generalised artificial-intelligence models;
- never transferred to anyone except as described in section 5;
- not read by humans, except where the account owner asks for support, where it is necessary for security, or where the law requires it.
5. Processing by a language-model provider
Ella is built on a large language model that runs as an external service. To draft a reply or answer a question, the relevant message text may be sent to that provider for processing and returned as a response. This is necessary to provide the assistant feature itself, and no other purpose.
The provider is configured by the operator and may change. As configured today, model requests are processed outside Malaysia, and the provider may retain request data for a limited period for abuse monitoring under its own terms. The operator is responsible for choosing a provider whose terms are acceptable for the correspondence involved.
Google user data is not sent anywhere else — no analytics service, no advertising network, no third-party integration beyond the model provider and the Google APIs themselves.
6. Storage and security
- Data is held on one private server operated by us in Kuala Lumpur, Malaysia.
- OAuth tokens and other credentials are encrypted at rest with AES-256-GCM on an encrypted volume, and are not readable by the assistant itself.
- Message history is held in a database bound to the local machine and not reachable from the internet.
- The administration interface requires a password and is served only over HTTPS.
7. Retention and deletion
Message and conversation history is retained while the assistant is in use so that it can refer to earlier context. The account owner may delete any or all of it at any time by asking the operator, and everything is deleted when the assistant is decommissioned.
Google data is not copied anywhere beyond what is described here, and no backup is transferred outside the operator's own infrastructure.
8. Withdrawing access
Access can be revoked at any time, without our involvement, at myaccount.google.com/permissions. Revoking it immediately and permanently ends Ella's ability to reach the mailbox or Drive.
9. Children
Ella is not intended for and is not used by anyone under 18.
10. Changes
Any change to this policy will be published on this page with a new date above. Because there is exactly one user, changes are communicated directly.