Awaya
Back to waitlist

Awaya Privacy Policy

Who handles your information

Awaya handles information for its website, waitlist, and any travel beta you separately choose to use. Contact stephen@awaya.io about privacy, requests, or complaints.

Website and waitlist information

When you join, Awaya collects your phone number, the time you first joined, and the initial consent text and version shown for that signup. We normalise the number into an international format. Repeat submissions preserve the first signup record rather than create a new consent history or replace its wording. We also give you a referral link to share, and if you joined through someone else's link, we record which link you used.

We use this information to maintain the waitlist, administer possible access invitations, honour messaging choices, and handle support or disputes about signup. Providing a number is optional, but we cannot save a waitlist signup without one.

Page and API requests also provide technical information to our hosting systems, such as your IP address, browser information, requested page, and request time. This information supports page delivery, reliability, security, and investigation of errors or misuse. If you contact us, we receive the information in your message.

Joining does not verify ownership, create a travel profile, connect Gmail, import emails, or start a beta conversation. A repeated signup does not reverse an earlier opt-out or record fresh acceptance against the original signup.

Optional travel beta information

If you separately use an available beta, Awaya processes the information needed for the functions you choose. This can include your messages, travel preferences, dates, budget, loyalty details, and responses to suggestions. Automated systems, including AI, may interpret requests and prepare recommendations. Their inferences can be incorrect.

An optional account connection requires separate permission. If you connect Gmail, information available through the access you approve may help identify points and travel records. Declining a connection can limit functions that depend on it. Share someone else's details only with permission. Avoid sending sensitive documents or information unless a particular function explains why it needs them.

Providers and disclosures

Cloudflare provides hosting and storage for the website and waitlist. Providers that support messaging, AI, or travel search may process information when you use those separate functions. Information supplied for an approved booking may also go to the relevant travel supplier. We may disclose information when law requires it or where necessary to address misuse or protect legal rights.

Service providers may process information outside Australia. Processing locations depend on the provider and function used. Joining the waitlist does not itself send your number to a travel supplier or connect an AI travel conversation.

Retention and protection

We keep information for the purpose for which it was collected and for necessary legal, security, or dispute-handling reasons. When it is no longer needed, we delete it or remove identifying details. Minimal records may remain to honour opt-outs, prevent duplicate messages, document the initial permission, or meet legal and security needs.

We take reasonable steps to protect personal information. No online system can guarantee complete security. Disconnecting an account stops that connection's future access. It does not itself delete information already imported.

Your choices and requests

Email stephen@awaya.io to request access, correction, deletion, withdrawal of consent, or to complain. We may make reasonable identity checks before providing or changing personal records. We assess requests under applicable law and explain any restriction that prevents us from completing a request. Deletion may leave the minimal records described above.

You can revoke Google access through your Google Account. Contact Awaya separately about information already imported. We publish policy changes with an updated date and seek further permission where required before a new use begins.