Privacy

1243116 B.C. Ltd., Parksville, British Columbia, Canada operates Homie. This notice covers the homie.rocks website, Homie’s tools for makers, and the earlier Homie app for Mac. The responsible position is the Privacy Officer, 1243116 B.C. Ltd.; contact that office through Feedback & help.

Visiting homie.rocks

You can play, watch and listen on homie.rocks without an account, and we do not ask who you are. The games, songs, videos and rooms listed here are served from the studios’ own sites. When you press Play, play a song or a video, open a room’s chat or follow a link to a studio, your browser connects to that studio’s site directly. Cover pictures shown on our pages are loaded from the studio’s site too. That studio, not homie.rocks, receives those requests, and what it collects is handled under the studio’s own practices. Search on homie.rocks runs in your browser against the list of what is listed; what you type into it is not sent to us.

Accounts on homie.rocks

An account is optional. It uses a passkey: there is no password, and we do not ask for an email address. We store an account identifier; the name you choose to be called; for each passkey you add, its identifier, its public half, its signature counter and when it was added and last used; when the account was made and last seen; the games, songs, videos and rooms you chose to keep, with when you kept each; whether you opened that list to people who know your name; and the accounts you chose to follow. When you are signed in and the site’s own video player plays a video, we also store where you were in it, in whole seconds, so that it can carry on from there on another device; the same record can hold a position in a song or a game. A position stays with the account until a newer one replaces it; it is not deleted automatically. The private half of a passkey stays on your device. An opaque cookie keeps you signed in on that browser for up to 90 days. Its server-side session can be revoked, and signing out revokes your sessions. Your account page shows what your account holds.

If you link a household that runs the earlier Homie app to your account, we also store which household it is, the name it gave itself, the box it runs on and when. If you turn on notifications from that household, we store your browser’s push address and keys for that device until you turn them off or the browser withdraws them. A household can then send that device a question to answer, and we keep the question’s words, the answers offered and which one was pressed.

Studios, listings and reports

A site made with Homie’s toolkit introduces itself to homie.rocks the first time its listing file is read. That can happen before the site is listed, and whether or not it ever is. We then store the site’s address, a code that lets the site show it controls that address, and when it was first seen. If the site names the GitHub repository it was deployed from, we store that too, as the owner and repository name, with when and how we learned it. A repository name identifies its maker’s GitHub account. We keep it, and nothing on homie.rocks reads it today. It is not shown on any page of homie.rocks, and Homie’s tools endpoint tells it to nobody, whoever asks and whatever they present. A chat that needs a studio’s repository asks the maker for it.

When a studio is set up from a chat, we keep a setup record for seven days: the studio’s name and a short form of it, the site’s address once it is connected, the repository name once a session attaches from it or the maker gives it (which is shown again only to whoever holds that setup’s own code), the times, and a hashed form of the network address that opened the setup. When a chat opens a build, we keep for 24 hours what the chat sent: the build’s title, the studio’s name, the repository, the game’s name, any folder and source address it gave, and the request in the person’s own words. While a build shares its progress so that it can be shown in a chat, we keep its latest progress for 24 hours after its last update. A record past its time is deleted the next time one of its kind is made.

When a studio asks to be listed, we store its site address, its name and short name, its tagline, the toolkit version it runs and the address of its list of rooms. For each app, game, song, video and post it lists, we store the name, description, links, cover and file addresses, seats or length, date and credits that the studio gave, and for each shared part its name, kind, version, licence and file address. We read the studio’s listing file again from time to time and keep what it says then. Where a studio chooses to share them, we also store how many people are in its public rooms, the list of those rooms as the studio reports it, and how often its games were played in the week. We do not store a studio’s code, its media files or its keys. An office key that a maker’s AI gives to Homie’s tools endpoint is passed on to the maker’s own site and is not written to our database. To limit abuse, publishing, reports and Homie’s tools endpoint are counted against the studio’s address and a hashed form of the caller’s network address; those counts are kept for about two days.

When you report a listing, we store what you chose and wrote, a reply email if you gave one, the time and a hashed network address. The report goes to the directory’s owner, and can be emailed to them with your reply address if you gave one. If homie.rocks has no mail service connected when that email is due, the email’s text, which holds your report and your reply address, is kept in our database instead, for the owner to read there. A report is not sent to the studio. We keep a record of each decision to unlist, take down or restore a listing: which listing, when, who decided and the reason.

Hosted studios

When the Homie Team hosts a studio for you, Homie stores your account identifier, the studio’s name and description, its source and hosted files, references to the infrastructure that runs it, and its memberships and access records. We keep a creation request identifier until creation succeeds or the account is deleted. AI connections store the app registration, your approval, studio and permissions, token credentials and expiration times; you can disconnect a connection from the studio’s settings. Talk to Homie keeps each conversation and its attachments until you delete them. To answer, what you send is processed by the model you pick on Cloudflare Workers AI, and is not used to train models. When a hosted studio notifies the phones its owners turned on, we keep for one day the studio, the time and the notice’s title, so the same title is not sent again, and we do not keep who was notified. This is separate from the directory listings described above.

A hosted studio sells through its owner’s own Stripe account; card details go to Stripe and are not stored by Homie. For each sale we keep the order: what was bought, the amounts, Homie’s fee, refunds, disputes and Stripe’s receipt link. The owner’s Sales page shows each buyer’s name as Stripe Checkout collected it, and Stripe’s fee on the sale. Homie keeps that name for 400 days after the sale, and no longer than 30 days after the studio closes. For a booking, Homie keeps the buyer’s email from Checkout with the booking, so the studio can reach them about it, for up to 400 days.

The earlier Homie app for Mac: on your Homie and with your providers

The app is retired. It kept local household and owner-device identities, settings, activity and conversation records, and creations needed to operate your room. Connected credentials were held in local configuration or macOS Keychain, depending on the integration. They were used for services you connected and were not automatically attached to feedback.

The app could run your installed AI command-line tools with the capabilities authorized for a task. Inputs, context and content it sent to an AI or other connected provider were processed under that provider’s account and policies. A local app did not mean AI requests stayed on your Mac.

The earlier Homie app for Mac: enrollment, invitations and updates

Enrollment is closed. It used a device signing identity and household allocation to provide a Homie address and authenticate services. Infrastructure processed allocation, invitation, update and certificate/DNS challenge information. Public hostnames, DNS records and certificate information were not secret; the device’s private signing key was separate.

Invitations processed recipient emails and delivery, eligibility, expiry and redemption records. The website waitlist, offered while access was by invitation, stored your submitted email, AI preference, submission time and a hashed network address to limit abuse. Invitation-related messages were sent for these purposes. The install page used to let a person who was not on a Mac ask to hear if the app ever ran on their computer. It no longer takes those requests. For each person who asked, we still hold the email they gave, which computer they chose, the submission time and the same hashed network address, and you can ask us to delete yours through Feedback & help.

When homie.rocks offered setup codes, getting one used Cloudflare Turnstile, an automated human check that ran in your browser; Cloudflare processed information from your browser and connection to perform it, and told us whether it passed. To limit abuse, we counted requests against a hashed form of your network address, per minute and per day, together with a random identifier your browser sent so that a retry returned the same code. We stored the issued code only in hashed form, with its expiry and whether it was used; it expired after one hour. Expired codes and request counts are deleted. When a code put a household online, the resulting enrollment records are kept like any other household’s. We did not ask for an email or an account to issue a code.

Purchases

Playing, watching and listening on homie.rocks is free, and those pages do not ask for a card. Where the Homie Team hosts a studio, its credit is paid on Stripe’s Checkout page, which collects the card; Homie does not store it. A studio may sell things on its own site, through its own Stripe account. A purchase there is handled by that studio and its payment provider under their own privacy practices. For a studio the Homie Team hosts, “Hosted studios” above says what Homie keeps.

Brands of the earlier Homie app had one-time offers, paid through Stripe’s checkout page; one of them was withdrawn on September 28, 2026. One other, Low Beam’s Night Route, is set up on that brand’s own site and is not on sale; if it is ever opened, a purchase there is recorded in the same way. For each purchase that was started we hold a record: the brand and the offer, the amount and currency, Stripe’s references for the checkout and the payment, the page it was started from, the terms accepted and when, which release it was for, its status and the times it was started, paid or refunded, and any refund or dispute Stripe reported. For a purchase that was paid, the record also holds what the buyer gave Stripe’s checkout, which is their email address, the name for the receipt and the display name they chose, together with their place among the buyers, the private code that opens what they bought, when that access ends, and what was delivered to them and when. A purchase that was started and never paid holds no email address and no name. We never hold a card number. If Stripe reports a late payment, a refund or a dispute for one of those closed offers, it is still recorded.

The earlier Homie app for Mac: creator payouts

If you set up creator payouts from the app, Stripe’s hosted Connect form collected and verified the legal identity, tax and payout-destination information it required under its own privacy terms. Identity documents and bank or card numbers went directly to Stripe and are not stored by Homie. We store the creator identity your Homie proved, the Stripe connected-account reference, country, verification and payout-readiness status, outstanding requirement names, and the related commercial terms, accrual adjustments and eventual settlement records needed for accounting and support. Completing verification did not itself send a payment.

The earlier Homie app for Mac: the managed brand desk

The desk that took a brief from someone who wanted the earlier app run under their own brand is closed, and no page of homie.rocks offers a way to send one. For a brief that was sent, we hold the account it came from, the brand’s name and domain, the sender and contact email addresses it gave, the catalogue, logo and package supplied for it, and a record of each step taken on it.

The earlier Homie app for Mac: sharing with others

Public publishing from the app sent selected content and display or creator metadata to hosted infrastructure so others could see, play or download it. Public content can be copied. Private remote play was different from public publication, but direct peer connections could reveal network addresses to the other peer. Connection and signaling infrastructure processed information needed to connect devices.

Homie updates (email list)

If you sign up for Homie updates on homie.rocks, we email you a link to confirm. Nothing is kept until you open that link and press Confirm: the link itself carries your address, signed so it cannot be changed, and it stops working after 48 hours. If it was not you, ignoring the email is enough. When you confirm, we keep two things: your email address and when you confirmed. They are kept in homie.rocks’s own database on Cloudflare. The emails are sent through Cloudflare’s email service (Cloudflare also hosts homie.rocks), which processes your address to deliver each one. To stop the form being used to fill someone’s inbox, sign-ups are counted for a minute against a hashed form of your network address, and a hashed form of the address being signed up is remembered for ten minutes; neither is stored with the list. Each email names its sender, 1243116 B.C. Ltd., and a postal address. Updates are plain: no tracking pixels and no link tracking. Every update has a one-click way to leave, and leaving deletes your address from the list. The list is never sold or shared for anyone’s marketing.

The Lounge

The Lounge lives on Homie Official’s own site, official.homie.rocks, a Homie studio like any other. The Lounge page on homie.rocks shows its live feed and its play nights: your own browser connects to the Lounge directly, and homie.rocks passes none of what is said there through its servers and keeps none of it. To show the play nights and how many people are there, homie.rocks asks the Lounge and keeps that answer for about thirty seconds. A reaction or quick line you send from homie.rocks goes from your browser straight to the Lounge, which shows it to everyone there. To type or show what you made, you sign in on the Lounge’s own site with a passkey. What the Lounge keeps is set out in its own notes there: by default nothing said in it is stored; the studio may choose to keep the Lounge’s words for a set number of days, which the Lounge shows, and you can remove your own lines and report other people’s.

Private feedback

Website and in-app feedback explicitly submit a category, message and optional reply email. The website also has an anti-spam field. We store the submitted report, a reference, time and hashed network address. Reports are private and reviewed by the team, which may use service providers and AI-assisted support tools to triage and troubleshoot them. Privacy and legal requests are escalated to the operator; AI tools do not independently decide your legal rights. We do not automatically attach logs, screenshots, credentials or app context. Please leave passwords, keys and private links out of your message. A reply email is for follow-up, not a promise of automatic mail.

If you send email to an address at homie.rocks, we keep the message: the addresses it is from and to, its subject and text, the receiving mail service’s authentication result, and when it arrived.

Notes from Homie’s tools in Claude and Codex

When you use Homie’s plugin, its Claude Code mod or its connector, Claude may offer, at most once in a session, to send the people who make Homie a short note about something that confused you or got in your way, and you can ask it to send one. Nothing is sent unless you have seen the exact text and said yes: by pressing Send on the note’s card or in the mod, by saying yes in the chat, or by choosing Send when Claude Code asks. If you say no, nothing is sent, and Claude does not offer again in that session. A note holds only its kind (stuck, confusing, idea, praise or bug), the words you approved, the step it is about, the versions of Homie’s studio toolkit and plugin, which app it came from, whether Claude offered it or you asked, and how you said yes; a reply email only if you typed one. Before you see a note, keys, tokens, private links, code, file paths with your user name, email addresses, network addresses and your Cloudflare account’s name are taken out, and Homie takes them out again when the note arrives. A note never carries files, logs, screenshots or your studio’s contents. We store it with a reference, the time and a hashed network address used only to limit abuse, privately, with the other feedback above, and handle it the same way.

The earlier Homie app for Mac: when a Homie first starts

A new Homie sent one message to homie.rocks about ninety seconds after it first started, to say that it came up. It was the only report the app sent without being switched on, because a box that fails to start cannot press a switch to tell anyone that it failed. It carried five values and nothing else: the release version, whether the box was installed from the .pkg or was running from a source checkout, the macOS major version (for example “26”), the processor architecture, and how many seconds the app had been running when it sent. There was no household, device, account, serial, name, address or typed-in value in it. The door refuses a message carrying any other field outright rather than ignoring it, and the table it is written into has no column to hold one. We keep your network address only as a salted hash, so that one network cannot file more than ten of these a day, and we delete the record after ninety days. A Homie sent this once per install and, once it had been received, never sent it again. It could be switched off with "firstBootPing": false in the Homie’s household.json; with the switch off nothing was sent and nothing was recorded.

Optional diagnostics and website analytics

App telemetry is opt-in, and it is separate from the first-start message above. When enabled, it sends a bounded set of product event counts and a scrubbed crash diagnostic associated with the house identity. Turning it off stops recording those telemetry events. It does not stop network traffic needed for enrollment, updates or features you choose. Scrubbing reduces sensitive content; it is not a guarantee of anonymity.

The homie.rocks website and the games and players it serves also send short diagnostic reports: when something breaks (for example a shared game that does not start, a phone that cannot join, or a song or film that stalls), and a few plain counts that put those faults in context (a new game version loading, a search result pressed, an account sign-in). A report holds only a kind, the part of the site, an outcome, a coded reason, a timing, a game build’s content hash, a screen-size range, whether the screen is touch, and a browser family. It never holds words you typed, what you searched for, a page address, a cookie or who you are. We keep your network address only as a salted hash, to stop one page flooding the service, and delete reports after thirty days. “Don’t send diagnostics” in the site’s footer turns them off in that browser.

We use Cloudflare Web Analytics, a page-visit counter that Cloudflare runs. Cloudflare adds the counter’s script to some pages of homie.rocks as it delivers them to a browser. On October 8, 2026 those were the home page, the Games, Music, Video and About pages, and three pages about the earlier app (install, pricing and hardware). Which pages carry it is a setting in our Cloudflare account, not in the site’s code, so the list can change; the site’s own code adds no counter of its own. Cloudflare says the counter uses no cookies. A studio’s own site may count its visits in its own way, under that studio’s practices.

Cloudflare and other infrastructure providers process request and network information needed to deliver and protect hosted services. Service providers may process information outside Canada, subject to the laws where they operate. AI and connected-service providers have their own policies. We share information as needed for the features you request, with infrastructure providers operating them, or where legally required; this notice is not consent to unrelated purposes.

Safeguards include restricted authorized access and encrypted network transport where implemented. No system or transmission can be guaranteed completely secure.

Retention and your choices

We retain information as needed for the purposes described here, legitimate operational needs and legal obligations. Retention differs by record: for example, active household identity and publication records serve different needs from an expired invitation or a resolved report. When the stated purposes and lawful retention needs no longer require information, we delete or de-identify it. We do not promise one automatic deletion deadline for every record.

You can manage local information on your Mac, change integration and telemetry settings and use supported sharing controls. Local removal and hosted removal are separate. Deletion from backups may take time, and we cannot delete copies other people downloaded or recorded.

If we restrict or remove hosted content, we keep a record of that decision — which page, when, who made it and the written reason — and we keep it after the content is gone, for as long as we need it to show the decision was made properly and to handle a review, a rights claim or a legal request. Asking for the content to be removed does not remove that record.

Access, correction and privacy requests

Use Feedback & help to reach our privacy contact, request access or correction, ask for deletion, withdraw consent where applicable, or raise a concern. Keep the private reference and include an optional reply email for follow-up. We may need to verify your identity or ownership before disclosing or changing information. Do not send identity documents or secrets in the initial form. We will handle requests under applicable law, including any required time limits and exceptions. You may also raise a concern with the applicable privacy regulator.

We will notify you of material changes to this notice or a transfer of Homie to another operator and obtain consent where required, including for materially new purposes. Using the app is not blanket consent to optional telemetry or unrelated data use.