Privacy Policy

Application: WAEE (وعي) · Website: https://waee-projects.com
Effective date: 30 September 2026 · Last updated: 30 September 2026

1. Who we are

This Privacy Policy applies to the WAEE (وعي) application operated at https://waee-projects.com (the “Application”). WAEE is a private organizational workspace for authorized members. It is used to manage projects and tasks, write and review reports, work with maps and documents, and send operational messages and notifications.

Google OAuth is used only so the Application can send email from a mailbox that an administrator has explicitly authorized. It is not used as a public sign-in method for every workspace user.

2. Google user data we access

When an administrator connects a Gmail or Google Workspace mailbox, the Application requests only these OAuth scopes:

• https://www.googleapis.com/auth/gmail.send — permission to send email from the authorized mailbox. The Application uses this to deliver messages that the organization or a signed-in user composed in WAEE, including one-time verification codes, password-reset messages, account notices, and other operational mail.
• https://www.googleapis.com/auth/userinfo.email — the email address of the authorized Google account, used only to confirm that the connected mailbox matches the account the administrator intended to authorize.

The Application does not request or use scopes that would allow it to:

• read the authorized inbox, labels, drafts, or message history;
• delete, move, or permanently modify existing mail;
• access Google Drive, Calendar, Contacts, or other Google products;
• sign ordinary WAEE users in with Google.

3. How we use Google user data

Google user data is used only to provide and improve these user-facing features:

• sending mail that the Application or an authorized user asked to send;
• showing administrators which Google account is connected;
• renewing the send authorization so delivery continues to work;
• recording delivery success or failure so administrators can fix send errors.

We do not use Google user data for advertising, retargeting, personalized or interest-based ads, sale to data brokers or information resellers, credit-worthiness or lending, building unrelated databases, or developing, improving, or training generalized or non-personalized artificial-intelligence or machine-learning models. Google Workspace APIs are not used to develop, improve, or train generalized AI or ML models.

4. Limited Use

Use of data obtained through Google Workspace scopes, including any aggregated, anonymized, or derived data, is limited to providing or improving user-facing features that are visible in the Application. Transfers of that data are not allowed except: to provide those features with the user’s consent; for security investigations; to comply with applicable law; or as part of a merger, acquisition, or sale of assets after obtaining explicit prior consent from the user.

Humans may read Google user data only if the user has given affirmative agreement to view specific items, or when it is necessary for security (for example investigating abuse or a delivery failure), or to comply with applicable law, or when the data is aggregated for internal operations in accordance with applicable law.

5. Sharing, transfer, and disclosure

We do not sell Google user data. We do not transfer or disclose Google user data to third parties for advertising, data brokerage, credit, lending, or AI/ML training. We do not share Google user data with third parties except:

• Google, which receives the send request in order to deliver the message;
• the intended email recipients of a message the Application was asked to send;
• infrastructure that hosts the Application for the organization, used only to operate WAEE;
• when required by law, or to investigate abuse or protect the security of the service.

6. Storage, security, and protection

The Application stores the OAuth refresh token, related client credentials, and the authorized mailbox address on the organization’s servers so it can send mail without asking Google for consent on every message. Copies or logs of messages the Application itself composed (recipients, subject, and body needed for delivery and audit) may be kept in the workspace as part of normal operations.

Security procedures are in place to protect the confidentiality of this data. Access is restricted to authorized administrators. Data is protected in transit with encryption (HTTPS / TLS) and is stored on systems controlled by the organization. Tokens and secrets are not published in the public website.

7. Retention and deletion

We retain Google authorization data only for as long as the mailbox remains connected and the authorization is needed to send mail. We retain related delivery records for the period needed to operate and secure the service, unless a longer period is required or permitted by law. When the retention period expires, or when a connection is removed, we delete or destroy the stored refresh token and stop using that Google account.

You may request deletion of stored Google authorization data by:

• opening Google Account → Third-party access and removing access for WAEE / waee-projects.com; and
• emailing [email protected] and asking an administrator to delete the stored refresh token from WAEE.

Revoking access in your Google Account stops new send attempts. Ask the administrator to delete the token in WAEE so the stored credential is removed as well.

8. Other information processed by WAEE

Separately from Google APIs, authorized workspace users create accounts with an email address and password (or an invitation from an administrator). The Application processes workspace content they enter — such as tasks, reports, files, maps, and chat — to provide the workspace. That organizational content is not obtained from Google Workspace APIs unless a user pastes it into a message the Application then sends through Gmail.

9. Children

The Application is not directed to children under 13, and we do not knowingly collect Google user data from children.

10. Changes

If we change how the Application accesses, uses, stores, or shares Google user data, we will update this Privacy Policy, change the “Last updated” date, and obtain any new consent required before using Google user data in a new way.

11. Contact

Privacy questions and deletion requests: [email protected]