๐Ÿ”’ HomeCentralAI Privacy Policy

Effective Date: November 13, 2026 ยท Version 1.2

HomeCentralAI answers the questions a household asks every evening: what's on tonight, who's playing, what's for dinner, and what's on the calendar. To do that it holds a picture of what your household watches, eats and plans. That is personal, and this policy explains exactly what is collected, why, who it is shared with, and how to get rid of it.

1. Overview & Scope

This Privacy Policy applies to the HomeCentralAI applications for iPhone, iPad and Apple TV (the "App") developed and published by BassTech Consulting Group, together with its backend services hosted on Microsoft Azure.

The App is built around a household. People you invite to your household can see everything in it โ€” the tracked shows, the dinner options and votes, the recipe box, the grocery list, and the family calendar. That is the point of the product, and it is worth being clear about before you invite anyone.

By using the App you agree to the practices described here. If you do not agree, please stop using it and delete your account, which you can do from Settings at any time.

2. Data Controller

BassTech Consulting Group
Developer & Publisher of HomeCentralAI
Privacy inquiries: privacy@support.basstechdev.com
Website: basstechconsulting.com

3. Data We Collect

3.1 Account & Household Data

Data ElementSourcePurposeLinked to You
Apple user identifier (the sub claim)Sign in with AppleAuthentication; identifies your membership of a householdYes
Email addressSign in with Apple, if you choose to share itAccount recovery; permitting inbound recipe email from your own addressYes
Display name and optional nicknameApple, then editable by your householdShowing who is cooking, and whose taste a suggestion matchesYes
Household name, time zone, countryYou, at setupWorking out what "tonight" means where you live, and what streams thereYes
Genre preferences, favourite sports teams, allergies and diet notes per personYou, in SettingsOrdering suggestions by who is watching, showing your teams' games, and leaving unsafe dishes out of dinner optionsYes

3.2 Content You Create

This is everything the App exists to hold. It lives in your household's own records in Azure SQL and is never shown to anyone outside your household.

Data ElementFeature
Tracked TV series, watch-night preferences, and which episodes you have marked watchedTV tracking and the Tonight screen
Films on your watchlistMovie tracking
Recipes: titles, ingredients, steps, servings, timings, tags, your own notes and ratingsRecipe box
Recipe photos and uploaded filesRecipe import; stored in Azure Blob Storage
Dinner options, votes, picks and cook historyDinner decisions
Family calendar events you choose to share: title, time, location and which calendar they came fromFamily calendar; read from the Apple calendars you select on your device and sent to your household
Grocery lists and regular itemsGrocery
Dismissed suggestionsSo the App stops proposing something you rejected

3.3 Device Data

Data ElementPurposeWhere It Lives
Apple Push Notification tokenDelivering the evening nudge and prep remindersAzure SQL
Authentication tokensKeeping you signed iniOS Keychain, on your device only
Offline cache of your household's dataSo the App works with no signalOn your device
Preferences such as filters and reminder settingsRemembering how you left the screenOn your device

The App does not collect location, contacts or health data, and contains no third-party analytics SDK. Calendar access is optional and only used to read the calendars you select; the App never writes to your calendars.

3.4 Advertising

The App shows no advertising, in the free version or in Premium, and contains no advertising SDK. It does not request permission to track you, and no household content โ€” shows, recipes, calendar, votes โ€” is ever shared with advertisers.

4. How We Use Your Data

  • To work out which of your tracked shows have a new episode tonight, in your household's own time zone.
  • To suggest films you can actually watch, on services you actually subscribe to, ordered by the tastes of whoever is watching.
  • To read a recipe out of something you imported โ€” a link, a photo, a file, or an email (Premium).
  • To suggest recipes from ingredients you tell us you have.
  • To plan meals, decide whose turn it is to cook, and build a shopping list from the week's plan.
  • To show your household's calendar events and your teams' games alongside the evening's choices.
  • To send the notifications you have switched on.
  • To diagnose faults and keep the service running.

We do not sell your data. Household content is never used to target advertising. We do not use your data to train artificial-intelligence models โ€” ours or anyone else's.

5. Data Sharing & Disclosure

We share data only with the providers needed to make the App work:

Service ProviderPurposeWhat Is Sent
Microsoft AzureDatabase, file storage, and application hostingAll household data described in Section 3
Apple โ€” Sign in with Apple, APNsAuthentication and push deliveryYour Apple identifier; device push token and notification text
Anthropic (Claude)Reading a recipe out of imported text, and writing recipe suggestions from ingredients you listThe text of the item you imported, or the ingredients you typed. Anthropic does not use API content to train its models.
TVmazeTV schedules and episode dataThe titles you track. No personal data.
TMDBFilm and series metadata and artworkTitle lookups. No personal data.
Streaming Availability (movieofthenight)Where a title can be streamed in your countryTitle lookups and your country. No personal data.
Google (only if you connect Google Calendar or Google Drive, or sign in with Google)Reading the calendars you choose, reading a file you explicitly picked, and signing you inSee Section 6A. Your Google sign-in stays on your device.
Sports data providerScores, schedules and standings for the teams you pickTeam and league lookups. No personal data.
PostmarkReceiving recipes forwarded to your household's recipe addressThe contents of email you send to that address

We may disclose information where the law requires it, and only so far as it requires.

6. Apple Calendar โ€” What We Access and Why

Connecting your Apple calendars is entirely optional. The App works fully without it.

  • What is accessed: events from the calendars you tick in Settings, through Apple's EventKit, after you grant calendar permission.
  • Why: to show those events to your household in the Family Calendar and on the Apple TV app.
  • Where it goes: the title, time, location and calendar name of each event in the selected calendars are sent to our Azure backend and stored with your household's records so other members can see them.
  • What we never do: we do not read calendars you did not select, do not write to your calendars, and do not use calendar content for advertising.
  • Revoking access: turn the calendar off in Settings, or remove the permission in iOS Settings โ–ธ Privacy & Security โ–ธ Calendars. Events already shared are removed on the next sync.

6A. Google Calendar, Google Drive and Sign in with Google

Connecting a Google account is entirely optional. The App works fully without it.

What we request, and why

Google permissionWhat it is used for
See your calendars and their events (calendar.readonly)To list your Google calendars so you can tick the ones to share, and to read the events in the calendars you tick so your household sees them in the Family Calendar and on the Apple TV app.
Files you open with this app (drive.file)To read a recipe file you pick in Google's own file picker. The App cannot see any other file in your Drive.
Your name and email address (Sign in with Google, Android)To create and sign in to your HomeCentralAI account.
  • Calendar events: for the calendars you tick, the title, time, location and calendar name of each event (from one month back to three months ahead) are sent to our Azure backend and stored with your household's records so other members can see them. Calendars you do not tick are never read beyond their names. We never create, change or delete anything in your Google Calendar.
  • Drive files: the file you pick is read once, on your device, and its text is sent to our server to import the recipe. As with every recipe import, that text is processed by Anthropic (Claude) solely to read the recipe out of it (Section 5); Anthropic does not use it to train its models. The recipe that results is saved like any other recipe; the file itself is not kept, and nothing is ever written to your Drive.
  • Your Google sign-in: the access granted by Google is kept in the iOS Keychain (or Android's secure storage) on your device, and the App talks to Google directly. Our servers never receive your Google password or Google access tokens.
  • Revoking access: tap Disconnect Google in the App's calendar settings โ€” your Google events leave the Family Calendar on the next sync โ€” or remove HomeCentralAI at myaccount.google.com/permissions.

Limited Use

HomeCentralAI's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Google user data is used only to provide the features described above; it is not sold, not used for advertising, not used to train generalized AI or machine-learning models, and not read by people except with your consent, for security purposes, or where the law requires it. Google Calendar data is never sent to any provider other than our Azure hosting. The only Google data that reaches another provider is the text of a Drive file you pick, which goes to Anthropic for the sole purpose of extracting the recipe you asked to import.

7. Recipe Import โ€” Where Content Comes From

Recipes can arrive several ways, and each is worth describing plainly:

  • From a link: our server fetches the page and reads the recipe from it.
  • From a photo: the text is read on your device first, using Apple's Vision framework. Only the resulting text is sent to our server โ€” not, by default, the picture itself unless you attach it to the recipe.
  • By email: anything sent to your household's private recipe address is processed as a recipe. Only addresses belonging to your own household members are accepted; mail from anyone else is discarded.
  • From Google Drive: you pick a file in Google's picker and the App reads that one file (see Section 6A).
  • From ingredients: you type what you have and Anthropic proposes dishes. Nothing is read from your device to do this.

8. Data Storage & Security

  • Household data is stored in Microsoft Azure SQL in the United States, encrypted at rest with Transparent Data Encryption.
  • Recipe images and uploads are stored in Azure Blob Storage.
  • All traffic between the App and our servers uses TLS 1.2 or higher.
  • Authentication tokens are held in the iOS Keychain on your device and are never sent to our servers.
  • Every query is scoped to your household by an identifier carried inside your signed session token, not by anything the App can choose โ€” one household cannot read another's data.
  • Authentication is Sign in with Apple, or Sign in with Google on Android. We never see, store, or handle a password.

9. Data Retention

  • Your data is kept for as long as your household exists.
  • Deleting your account removes you from the household. If you are the last member, the household and everything in it โ€” recipes, dinner history, tracked shows, grocery lists, calendar events, uploaded images โ€” is permanently deleted.
  • Push tokens are deregistered immediately on account deletion.
  • Tokens held in the iOS Keychain are cleared when you sign out or delete the App.
  • Operational logs that may contain technical identifiers are retained for up to 90 days.

10. Your Privacy Rights

Depending on where you live you may have the right to access, correct, delete, export, restrict, or object to the processing of your personal data. To exercise any of these, write to privacy@support.basstechdev.com and we will respond within 30 days. Account deletion is also available directly in the App, under Settings.

11. Children's Privacy

HomeCentralAI is intended for adults running a household and is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has created an account, write to privacy@support.basstechdev.com and we will delete it promptly.

12. California Privacy Rights (CCPA)

California residents have the right to know what personal information is collected, to have it deleted, and not to be discriminated against for exercising those rights. We do not sell personal information, so there is nothing to opt out of. Requests go to privacy@support.basstechdev.com and are answered within 45 days.

13. International Users (GDPR)

If you are in the European Economic Area, the United Kingdom, or Switzerland, you have the rights described in Section 10.

Legal basis: we process your data to perform the contract you entered into by using the App; on legitimate interests for security and fault diagnosis; and on consent for optional features such as sharing your Apple calendars.

Transfers: data is stored on Microsoft Azure infrastructure in the United States. Transfers from the EEA rely on Standard Contractual Clauses provided by Microsoft.

You may also complain to your local supervisory authority.

14. Changes to This Policy

If this policy changes we will update the Effective Date and Version above, and show a notice in the App for any material change.

15. Contact Us

BassTech Consulting Group
Privacy inquiries: privacy@support.basstechdev.com
General support: support@support.basstechdev.com
Website: basstechconsulting.com

Terms of Service โ†’ โ† BassTech Home