Skip to content

Frontage is in early access. The free score works today, and we're opening accounts in small groups. Request early access

Privacy Policy

Last updated: 1 November 2026

This policy explains what Airez AI collects, why, and the choices you have. It governs the Airez AI products, including Airez AI Frontage and its free tools, and the airezai.com and app.airezai.com sites. Airez AI is a product operated by Airez Innovations LLP, the data controller. We collect only what is needed to operate the products you use, and we do not sell personal data.

Data we collect

Account data — email and authentication identifiers needed to create and secure your account.

Your business profile — the business details you enter (name, services, hours, location, links), so every tool works from one profile.

Your customers' contacts & messages — when you use the inbox, website chat, phone line or campaigns, we store the customer contacts and messages you capture so you can follow up. You are the controller of that data; we process it only to provide the service to you (see “Your customers' data” below).

SMS permission & campaign records — the permission state, when and how permission was collected, your proof note, opt-out time, the reviewed campaign audience, the exact message, the final four digits of each destination, delivery status, replies and outcomes. This keeps a record of what you approved, without treating an inbound enquiry as marketing consent.

Uploaded documents — files you add as knowledge are turned into searchable text so answers can draw on them; the original file is not kept.

Usage & metering — per-run token and cost records that power the run history you see in-product and accurate billing.

Billing data — processed by our payments processor; we store only the minimum needed to operate subscriptions and never store full card numbers.

Content you submit — prompts, inputs and connected-account data you provide to run a workflow or render, plus the generated outputs. Data from your Google accounts is described in its own section below.

How we use it

To operate, secure, meter and bill the products you use; to provide the durable, auditable run history; to prevent abuse; and to communicate service information. We do not sell personal data and do not use your content to train or improve AI or machine-learning models, ours or anyone else's.

Your customers' data (you are the controller)

When you capture your customers' contact details and messages through Frontage, you are their data controller and Airez AI is your processor. You are responsible for having a lawful basis and the consent you need to contact them, including express consent before sending marketing SMS or WhatsApp messages. Frontage holds back messages where SMS permission is unknown or withdrawn, keeps the permission record from the time you reviewed a campaign, checks eligibility again before delivery, and records STOP and START replies.

Processors & sub-processors

Airez AI uses AI model providers for its AI features; a payments processor for billing; the messaging providers you connect, to send on your behalf; object storage for generated assets; and cookieless analytics.

As of 1 November 2026, our AI features run on OpenAI's API, so that is where the data from Google described below is sent when a feature needs a model. OpenAI does not use data sent to its API to train its models, and keeps it for up to 30 days to monitor for abuse (OpenAI's API data controls, read 1 November 2026).

Data from Google

Airez AI Frontage lets you connect your own Google accounts. Each connection asks Google only for what that feature needs, and only when you press Connect.

  • Google Search Console (read-only): the list of your verified sites, and for the site you choose, the search queries that brought visitors in the last 28 days, and Google's index status for a page you ask about.
  • Search Console set-up: only when you press “Set it up for me”. A verification record for your domain, and permission to verify that domain, add it to your Search Console and submit its sitemap. To see whether your domain is already there, we look at your list of sites once and keep only that answer. We use this access only for that domain.
  • Google Calendar: the names of calendars you own, the busy times on the one calendar you choose, and the events on it. We create and update an event for each booking you confirm, and read events back to keep bookings in step. We act only on the events Frontage created, and we do not store your other events. Your open times, worked out from your calendar's busy times, are shown to customers on your booking page, in your website chat and on your phone line, and to AI assistants that ask to book you. They never show what an event is or who it is with.
  • Google Business Profile: the accounts and locations you manage. For the one location you choose: its reviews, its performance figures and the search terms people used to find it, its Google posts, and its Book link. We post a reply, a Google post or a Book link only after you approve it, or under a posting rule you turned on.
  • Your Google account's email address: to show which account each connection uses, and to make sure an undo goes back to the same Google account.

How we use it. Only to provide the features you see in Frontage: your reviews and replies, your bookings and open times, your dashboard, your content plan, and Get found. We do not use data from Google for advertising, we do not sell it, and we do not use it to train or improve AI or machine-learning models, ours or anyone else's.

Who receives it. Some features send part of it to our model provider (see Processors), and only the part that feature needs:

  • a review reply you ask for: that review;
  • your content plan: the search terms and review themes in its brief;
  • suggested knowledge-base answers: the text of up to 15 recent reviews;
  • a change you ask your assistant for: the stars and the start of your recent reviews;
  • a customer asking for a time: your open times.

We never send the contents of your calendar events.

Apart from the open times described above, we share data from Google with no one else, except to comply with the law, to protect the security of the service, or as part of a merger or sale of the business with your prior consent.

Who at Airez AI can read it. No one, except when you ask us to (for example, for support), when it is needed to investigate abuse or keep the service secure, or when the law requires it. We may also use figures aggregated and anonymized across many businesses to run the service.

How it is stored. Your Google access keys are encrypted on our servers and never sent to your browser.

Keeping and deleting it. Press Disconnect on Connections and we delete our saved access at once. If no other Frontage feature still uses that Google access, we also ask Google to revoke it. Reviews, performance figures, posts and bookings you already brought into Frontage stay in your workspace until you delete them, or until you ask us to delete your account at privacy@airezai.com. You can also remove Airez AI's access at any time at myaccount.google.com/permissions.

Limited Use. Airez AI Frontage's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Changes. If we change how we use data from Google, we will tell you and ask for your consent before the new use applies.

Generated assets & storage

Renders and workflow outputs are stored on object storage and served only via signed, expiring URLs. Traces are durable and portable so you can audit and export your own runs.

Retention

Account, profile and billing records are kept while your account is active and as required for legal and accounting obligations. You can edit or delete your business profile, knowledge and captured contacts in the product, and request deletion of your account data. SMS opt-out state is kept while the customer record remains, so later campaigns keep skipping that number; campaign approval and delivery records are kept with the workspace for audit and export. Trace retention follows your plan.

Your rights

Subject to applicable law (including GDPR and CCPA), you may request access, correction, export or deletion of your personal data, and object to or restrict certain processing. Contact privacy@airezai.com and we will respond within the statutory period.

Cookies & analytics

The marketing site uses privacy-first, cookieless analytics — no advertising trackers and no cross-site cookies — so no consent banner is required to browse it. The Frontage app sets a strictly-necessary session cookie only when you sign in.

Security

Encryption in transit and at rest, least-privilege access, connected-account tokens kept encrypted and out of client code, each signed-in owner's data kept separate, rate limits on public endpoints, and metered AI usage you can see. More detail on the security page.

AI-generated content

Some outputs (content, replies, phone and chat answers) are written by AI and may be imperfect — review them before you publish or send. Where an AI assistant speaks to your customers, it says that it is AI, in line with the EU AI Act.

International transfers & children

Data may be processed in regions where we or our processors operate, with appropriate safeguards. The products are not directed to children under 16.

Changes & contact

We will post material changes here with an updated date. Some products are in Beta and this policy may evolve as they reach general availability — changes will be dated and announced, never silent. Questions: privacy@airezai.com.