HomeLinq Memory privacy

Privacy in plain words

Mine is private from other members, not from the operator

• The operator reads entries only to fix a problem you report.
• Access to the database is restricted.
• Entry text is kept out of routine logs and error reports.

Forget removes a line from HomeLinq at once

• Copies stay in database backups for up to 30 days.
• Backups are Cloudflare D1 Time Travel: 30 days on Workers Paid, 7 on Free.
• What an assistant already showed or recorded is outside HomeLinq's control.

Removing a member, or leaving, stops future access

• It cannot take back what was already seen.

Join emails are sent through Resend

• Resend sees names (the joiner's, the household's) and email addresses.
• It never sees entry text.

HomeLinq does not sell personal data or use it for ads

• This covers entries, names, email addresses and the Google sign-in identifier.

What to leave out, and why

• Home is readable by current members and anyone who joins later, including older lines.
• Mine is private from other members, but the operator may read it to fix a problem you report.
• Forgotten text can remain in backups for up to 30 days, and your assistant may keep its own chat history.

Health records and tracking

• A brief household safety note, such as an allergy, is fine.
• Please do not use HomeLinq for ongoing measurements (heart rate, sleep, blood pressure), test results or medical files.
• This shared memory is not designed to protect a health history.

Financial details

• Amounts, due dates, payees and who pays are fine, for example "Mortgage: $3,200 monthly, due on the 1st."
• A utility or maintenance charge, or the last four digits of an account, is fine too.
• Please leave out full statements; passwords, PINs and security answers; full account, routing and card numbers; and government ID numbers.
• Those details can expose your transactions or help someone commit fraud. HomeLinq is not a vault.

This is guidance for what you choose to save; HomeLinq does not screen saved text for these details. Whether health or financial privacy rules would apply to HomeLinq has not been reviewed.

Google user data

• At sign-in, HomeLinq asks Google only for your basic identity and email address (the openid and email scopes), and receives what those return.
• HomeLinq keeps your Google account identifier.
• Your email address is kept as the one you were added or invited with. At sign-in, HomeLinq checks it against your verified Google email.
• HomeLinq uses them only to sign you in, to match you to your invite or enrollment, and to send join emails.
• Your display name comes from your enrollment or invite, not from Google.
• HomeLinq does not sell personal data or use it for ads, Google user data included.
• Join emails go through Resend, which sees names and email addresses, never entry text.

What it cannot promise

These depend on the assistant, not on HomeLinq.

• That a save really came from your request.
• That an assistant ignores instructions written inside someone's Home line.
• That an assistant's "Always allow" setting never saves something unwanted.

Risks we accept

• Assistant mistakes, and transcripts the assistant keeps.
• Access by the operator and by the infrastructure (Cloudflare).
• Names and email addresses seen by the email provider (Resend).
• Database history that can be restored, within its backup window.

Contact

Questions or requests: admin@homelinq.ai