Privacy Policy
AWQ Cloud Briefing is a workspace application for flight briefing operations: flight watch, NOTAM, TAF, weather, FIR, and crew briefing report generation. This page explains what data the application processes, including Google account data when you create a report as a Google Sheet.
In short. The application requests only one Google permission: https://www.googleapis.com/auth/drive.file. That permission grants access only to files this application creates or opens — not the entire contents of your Google Drive. The Google access token is used only in your browser for that one upload and is never stored on our servers. We do not sell your data and we do not share it for advertising.
1. Google data we access
When you press the button to create a Google Sheets report, the application asks for your consent through the Google consent screen for a single scope:
| Scope | What it grants | What it does not grant |
|---|---|---|
drive.file |
Creating new files in your Google Drive and modifying files you open or share through this application. | No access to other files in your Drive, no general reading of your Drive contents, and no deletion of files other than those created by this application. |
We do not request access to Gmail, Contacts, Calendar, or any other Google data, and we do not request broader Drive scopes.
2. How Google data is used
- Single purpose: to create one crew briefing report spreadsheet at your request, in the Google Drive of the Google account you choose yourself, and then to open that file's URL in your browser.
- The report contents come from data already inside the application (the flights, NOTAMs, TAF, and weather you selected). Google is not used to analyse your data.
- We do not use Google data for advertising, profiling, credit assessment, or any purpose beyond producing the report you requested.
3. Token and Google data storage
- The Google access token is issued by Google directly to your browser. It is used only for that one upload.
- The token is not stored on our application servers, is not written to
localStorage, and is not sent to our application backend. - We keep no copy of Google Sheets files or of your Google Drive contents on our servers. The files stay in your Drive and remain yours.
- When you close or reload the page, the application will ask for Google consent again the next time you use the feature.
4. Sharing data with third parties
We do not sell, rent, or trade user data. Your Google data is not shared with third parties, except where required by applicable law or to investigate abuse. This application uses no advertising networks, data brokers, or third-party trackers.
5. Google API Services User Data Policy compliance
This application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Google data is used only to provide or improve features that are clearly visible in this application's interface.
- Google data is not transferred to others except as necessary to run those features, for security reasons, or to comply with the law.
- Humans do not read your Google data unless you give explicit consent, or it is necessary for security/abuse purposes, or it is required by law.
- Google data is not used or transferred for advertising, retargeting, credit assessment, or the sale of data.
6. Data we store ourselves (not from Google)
To function, the application stores the following in our own database (Cloudflare D1):
- Accounts: email address, password hash (PBKDF2) with salt, access role (admin/registered/read only), and active status.
- Operator profile: the name, IAA ID, and LIC No. that you enter yourself.
- Operational data: flight, NOTAM, TAF, weather, and waypoint data and the analysis results used for briefing, plus an audit trail of changes.
This data is used only to run the application's operational functions, not for advertising, and it is not sold. Storage and processing are provided through our infrastructure provider, Cloudflare (hosting and database).
7. Retention and deletion
- Operational data and the audit trail are retained for as long as needed for operational and flight-safety purposes.
- You can request deletion of your account and profile data by contacting the address below. We will follow up within a reasonable time.
- Deleting your application account does not delete Google Sheets files already created in your Drive — those files are entirely yours and you can manage them yourself in Google Drive.
8. Your rights and how to revoke Google access
- Revoke this application's permission for your Google account at any time at myaccount.google.com/permissions. Once revoked, the Google Sheets report feature cannot use that account until you grant permission again.
- You have the right to request a copy, correction, or deletion of the account and profile data we store about you.
- Declining the Google permission does not block other features: reports can still be downloaded as an XLSX file without a Google account.
9. Security
Access to the application is restricted by account and role. Passwords are stored as a hash (PBKDF2) with salt, not as plain text. Communication with the application uses HTTPS. Even so, no system can be guaranteed completely secure; report any suspected security issue to the contact below.
10. Changes to this policy
This policy may be updated when application features or legal obligations change. The latest version is always available on this page with the update date at the top.
11. Contact
Questions about this policy or requests relating to your data: christiandaniel@airasia.com.
Summary for Google API reviewers
App: AWQ Cloud Briefing (https://awq.christiandaniel.my.id) — a flight dispatch briefing workspace for NOTAM, TAF, weather, FIR and crew briefing reports.
Requested scope: only https://www.googleapis.com/auth/drive.file (non-sensitive). No other Google API scope is requested.
Why the scope is needed: the "Create Google Sheet" action converts the generated crew briefing report into a native Google Sheets file. The file is created in the signed-in user's own Google Drive using that user's own OAuth grant, and the app then opens the file's edit URL. The scope is limited to files this app creates or that the user opens with it; the app cannot list, read, or modify the user's other Drive files.
Token handling: the access token is obtained in the browser through Google Identity Services and is used only for that single upload. It is never stored on the application backend, never written to localStorage, and never sent to our servers.
Data storage: no Google user data (no Drive content, no Google profile data) is stored on our servers. The app's own account and operational data live in Cloudflare D1 and are unrelated to Google APIs.
Limited Use: our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not sold, not transferred to third parties, not used for advertising or retargeting, and is not read by humans except with explicit consent, for security purposes, or as required by law.
Revocation: users can revoke access at myaccount.google.com/permissions at any time. The XLSX download remains available without any Google account.
Contact: christiandaniel@airasia.com