Privacy Policy

1. What Brown Family Legacy is

Brown Family Legacy is a private collection of family applications for household finances, records, documents, groceries, assets and long-term household continuity. It is not a public social network, advertising platform, data broker or consumer-data marketplace.

Accounts and households are created for authorized family use. Creating an account does not make household records public. Access to household data is controlled by household membership and permissions.

2. Information the applications store

Brown Family Legacy may store the following categories of information:

• Account information. Your email address and authentication identifiers, plus your name and profile picture when supplied by Google sign-in.
• Household information. Information the household intentionally enters, such as records about people and organizations, financial accounts, balances, income, bills, debt, insurance, assets, documents, groceries and recipes.
• Files and document metadata. Files a household deliberately stores, together with titles, dates, relationships and other information needed to organize them.
• Session information. Cookies required to keep you signed in and remember which household you are using. Brown Family Legacy does not use advertising or tracking cookies.

3. How Google user data is accessed and used

Brown Family Legacy uses Google OAuth only as an authentication option. When you sign in with Google, Google confirms your identity and provides the basic profile information needed to create or locate your Brown Family Legacy account.

Brown Family Legacy does not use Google user data to build advertising profiles or to train its own machine-learning models. Its use of Google data is limited to the authentication and account-identification purposes described here.

4. Where information is stored

Application data is stored in Supabase, which provides the hosted PostgreSQL database, authentication service and private file storage used by Brown Family Legacy. The web applications are hosted on Vercel. Those providers can technically access the infrastructure they operate as necessary to provide their services.

Household records are scoped in the database by household. Row-level security is used so a member of one household cannot read another household's records. Inside a household, permissions determine what each member may see and change.

5. Documents and optional AI-assisted reading

When supported documents are captured, text extraction is performed in the browser. The document file itself is not sent to an outside language model merely to read its text.

Some workflows include an optional intelligence step that can suggest structured fields from extracted text. This step is off unless someone deliberately starts it. When it is used:

• only text is sent to the outside service, not the original file or image;
• social security numbers, payment-card numbers, email addresses and telephone numbers are replaced before sending when they match the application's supported redaction patterns;
• the text sent is limited to the first 24,000 characters;
• the text is sent through OpenRouter to a language model so that it can return suggestions; and
• a person must review and accept or reject those suggestions before they become records.

Grocery uses a similar optional text-based step for recipes and cookbook material. These optional steps are not part of Google sign-in and do not grant access to Google account content.

Redaction is a practical pattern-matching safeguard, not a guarantee. If a document contains unusually formatted sensitive information, the optional intelligence step should remain off for that document.

6. What Brown Family Legacy does not do

• No advertising and no sale of household or Google user data.
• No page-view analytics, session recording or product-behavior tracking.
• No third-party advertising cookies.
• No automated credit, employment, insurance or eligibility decisions about users.
• No access to Gmail, Google Drive, Google Contacts or other Google account content through sign-in.

7. How long information is kept

Household records are generally kept until an authorized person deletes, archives or supersedes them because the purpose of the system is to maintain a durable household record. Historical records may be retained so older transactions and relationships continue to make sense.

A household member may request removal of their account. Some household records associated with that person may remain when they are part of the household's historical record, subject to the permissions and retention rules of the application.

8. Children and family accounts

Children in a household may have managed or authorized accounts under the household owner's supervision. Brown Family Legacy is family software, not a service marketed or offered to children independently. Household permissions determine what a child account may access.

9. Security and access

Brown Family Legacy uses authentication, private storage, database row-level security and household permissions to limit access. No internet-connected service can promise absolute security, so important original records should also be retained in an appropriate independent location.

10. Changes to this policy

This policy is intended to describe the software as it actually operates. If Brown Family Legacy changes how it accesses, uses, stores or shares information — including Google user data — this page will be updated and the date above will change.

11. Contact

Privacy questions, account-removal requests and data-handling questions may be sent to earlstreet61@gmail.com.