Bawb.ai privacy notice
This beta uses Supabase for accounts, private files, business records and website history; Vercel for the control service and public website; Render for AI worker execution; and Inngest for coordinating background work.
Account processing includes your sign-in email and account identifier. The service saves your business profile, messages, private notes, selected files, website versions and records of requested work. Enabled customer, booking, billing and connected-service features also retain the records described below. These records remain associated with the account or business so that you can return to your work from another session or device.
Current AI processing
The current route uses OpenRouter with OpenAI models for text requests, selected photo and document interpretation, website image generation and optional cloud voice transcription. Your request is sent to that provider when the selected feature requires it.
Your messages, scoped public business details, selected photos and extracted document text may be sent to the model provider to prepare your request. Private owner notes and enquiry data are excluded from website planning. When you ask for a customer reply draft, the relevant enquiry and reply context may be used for that draft. Provider retention and data controls follow separate policies; zero-retention processing has not been established. See OpenAI’s privacy policy and OpenRouter’s privacy policy.
The microphone beside the message box uses on-device dictation when supported by your phone. Its audio stays on the phone; the resulting text is sent only when you send the message. If you choose the separate cloud voice memo option, its recording is uploaded after you send it and its transcript waits for your confirmation before becoming a website request.
Your phone and connected services
Session credentials and saved message drafts use Android Keystore-backed storage on Android and Keychain storage on iPhone. Selected files and voice memo recordings can remain in app-private device storage until sent or removed. Microphone and notification permissions are optional. You choose individual photos or files through the phone’s picker. The current native builds contain no advertising SDK or native app analytics SDK.
Phone alerts are optional. If you enable them, Firebase Cloud Messaging and Firebase Installations process app installation identifiers and notification delivery data. Bawb stores a registration tied to your account, selected websites and phone so that alerts go to the intended device. iPhone delivery also uses Apple Push Notification service. Turning off alerts does not remove saved enquiries, bookings or website work from the app. See Firebase’s privacy information.
When you connect a Microsoft calendar, the selected account supplies calendar availability and receives the booking details needed to create, update or cancel appointments. Billing uses Stripe when paid checkout is enabled. Complimentary beta access requires no card and never starts a paid subscription automatically.
Your Google connections
Once enabled for a website, Bawb prepares standard website Analytics and Tag Manager resources automatically when a published secure website address is verified. These resources are managed through Bawb's Google account and are separate for each website. You can also choose to connect your own Google resources for the business website selected in Bawb. Google shows the permissions requested for each optional connection. Calendar, reporting, Search Console, Tag Manager and Business Profile use their respective permissions. Account access, API approval and website settings can still limit a connected feature.
Google Calendar: Bawb lists writable calendars, checks busy times and reads the booking event when confirming a change. It sends the service, customer name, appointment times and supplied booking message to the selected calendar to create, reschedule or cancel the appointment. If you select Google Meet, it also requests a meeting link. Saved booking instructions can be processed in the background; an uncertain calendar update remains pending for checking.
Google Analytics: once enabled for a website, automatic launch setup prepares a website-specific GA4 property and web stream. Bawb saves the tracking identifiers in website settings and reads measurements for that property's users, sessions, page views and key events. Reports are scoped to the selected website and remain separate from Bawb's saved enquiry and booking counts. Owners can turn measurement off or select their own existing resources. Later owner preferences take precedence over automatic setup. At an owner's request, a connected Google account can also be used to prepare an Analytics property and web stream in that account.
Bawb website measurements: once enabled for a website, launch prepares measurement automatically, and collection begins only when a visitor allows analytics. The consent banner names Google Analytics when visits are sent to Google. Consent previously given only for Bawb's own measurements does not authorize Google measurement; the visitor is asked again first. Bawb records page views, visible sections, action clicks, form starts and references to saved enquiries, subscriptions or bookings. Measurements use public page and design identifiers, coarse device and traffic-source groups, and a random browser-session identifier. Form answers, full referrer addresses and URL query strings are not included. A daily website-specific hash of the network address helps limit automated submissions; the measurement store does not keep the raw address. The measurement store retains the last 25 months, with a daily cleanup. GA4 reporting responses are cached for five minutes. Visitors can decline through Analytics preferences; this clears the measurement session and stops further collection on that browser. Bawb does not yet use these measurements to change designs automatically or share visitor-level data between customers.
Search Console and website verification: Bawb can request a verification tag, save it for your launched website, submit its sitemap after the required checks, and read search-query measurements such as clicks and impressions. The verification tag and published website addresses are public. Reading a report does not itself change your website content.
Tag Manager: once enabled for a website, automatic launch setup prepares a separate website container and publishes its initial Google measurement tag through Bawb's managed account. This default does not publish advertising tags. The container identifier is saved in website settings, and only the selected tracking route runs to avoid duplicate collection. On a managed website, Bawb loads the Analytics or Tag Manager script only after a visitor allows analytics. The script connects the visitor's browser to Google; Bawb's built-in tracking sends activity events rather than form answers. Visitors can choose Decline through Analytics preferences to stop it on that browser; the page reloads. At an owner's request, a connected Google account can also prepare a Tag Manager account and container. This optional customer-owned container setup remains a private configuration for review; preparing it alone does not publish its tags. Tags configured separately in Google Tag Manager have their own behavior.
Business Profile: when Google permits access, Bawb can read the business accounts and locations available to you, listing details, verification status and reviews, including reviewer names, comments, ratings and existing replies. You can import public listing details into website settings. Listing changes and review replies are saved as drafts and sent to Google only after you approve their exact content. Google may still review or reject a change; Bawb does not promise that it appears on Maps.
Google data, processing and your controls
Bawb stores the connection's access and refresh tokens encrypted and tied to the business. The server uses them to perform the connected features; they are not included in website source or model prompts. Selected settings, imported listing details, booking records, meeting links and saved listing drafts, approval records and provider receipts are kept in Bawb's database. Reports and listing reads also pass through Bawb's control service to appear in the app. The Supabase, Vercel and background-work services described above support this processing.
The website-planning route does not automatically send calendar events, Analytics reports or Google reviews to the model provider. Public listing details you import into website settings can become part of the business context sent for website work. Text you put in an ordinary message is also subject to the AI processing described above. Current Business Profile listing and review-reply drafts use saved facts and a standard reply suggestion, with owner editing and approval; that draft path does not call a model.
If you enable appointment emails and the visitor agrees, appointment details and any meeting link are included in updates and reminders. Resend receives the recipient address and message content to deliver them. Each appointment email has a stop-emails link; stopping those emails does not cancel the appointment.
You can remove Bawb's access in your Google Account's third-party connections. Google may also expire or withdraw access. Bawb then needs a new connection when its saved access can no longer be used; pending calendar work is not proof of a confirmed appointment. Turning off a Bawb module changes its use on the managed website, but does not revoke Google permission or erase saved records.
Removing Google access or deleting Bawb data does not delete appointments, Analytics properties or streams, Tag Manager containers, Search Console properties, listings or replies already held by Google. Manage customer-owned resources in the relevant Google service; contact the beta operator below for requests concerning Bawb-managed Google resources. Taking a Bawb website offline stops its public tracking runtime. Account deletion below removes Bawb's connection records with a sole-owner business; it does not send a separate Google permission-revocation request. Saved Bawb records and imported details remain until removed through the applicable Bawb controls or account deletion. Active account and business records remain available while you use the service or until removed through its controls. Provider logs and backup copies have separate expiry schedules; contact the operator below for retention questions.
When you choose a marked website screenshot, the app captures only the website preview and records its page and selected location. You review it before adding it to your message. Sending that message uploads the image as private visual feedback for the requested change. It may be processed by the model provider with your request and remains associated with your saved files and messages. Marked screenshots cannot be published as website photos or used as logos or business material sources.
Original uploads remain private. Photos approved for publication have resized derivatives with camera metadata removed. Messages, results and immutable release history persist independently of the phone. Enquiries remain in the private inbox even if notification delivery fails. Account deletion and exports are described below. Provider logs and backup copies are handled separately from active records.
Export your account
In the app, open the menu, choose Settings → Export website and account to save a ZIP with messages, private facts, enquiries, release history, original files and a portable website. Choose a private location and publish only the website folder. The static copy includes call links and photos; online enquiries, future schedules and new changes require the managed service. Exports are copies you control and are not erased when you sign out or delete your account.
Deleting one website
In Settings, choose Delete this website to review one website while keeping your Bawb login and other websites. Bawb checks whether an export has been reported in the past 14 days; older app downloads may not have been recorded. Before removing the website’s active records and original files, Bawb automatically packages a private recovery ZIP. If packaging cannot be confirmed, records are kept for cleanup and you can retry. The website is taken offline, queued work stops and its subscription is canceled immediately. Prior payments and unused time are not refunded automatically.
The deletion receipt and confirmation email provide a private download link valid for 14 days after deletion. Anyone with the full link can download the copy; keep it private. The recovery file is stored privately, access ends at the stated expiry, and an hourly cleanup erases the stored copy after expiry. You can erase it sooner from the receipt. The copy remains available for its stated period even if you later close your login. It includes website source, saved website records and available original files, without authentication credentials or provider secrets. It does not restore hosting or connected services. Files you download remain under your control. Domain registrations, DNS and external email/calendar services are not canceled by deleting a Bawb website.
Account deletion
You can delete your account and sole-owner beta websites in the app or through this website. Deletion verifies your current password, takes those websites offline, removes original files through Storage, then removes active account and business records. If a file removal fails, the websites stay offline and you can retry to finish. Shared business records remain with their other owners with your account reference removed. An anonymous completion receipt remains.
Provider logs and backup copies follow separate expiry schedules. We do not promise instant removal from those copies. Contact the beta operator, Jake Tlapek, at jake@jakethewizard.com for access, retention or data requests.