Privacy

Kinwick is built and run by Paul Gi, an independent developer in the United States. There is no company behind it and no investors. For anything on this page, email privacy@kinwick.app.

Your account. An email address, and a password if you set one. Passwords are stored hashed, so nobody at Kinwick can read them. Sign-in times are recorded.

Your profile. The display name you choose, a color, your household role (Admin or Member), and any presentation setting an Admin assigns to you (Grown-up or Youth).

Household content. The household name, chores and their descriptions, review notes, rewards, Home Bucks entries and the reasons attached to them, lists, list requests, invite codes, family goals, announcements, and a seen receipt for each member who views the current announcement.

Announcement seen receipts record that a member has viewed the active announcement. They do not record when it was viewed. Household Admins can see which current members have viewed it; other members cannot see those receipts.

Personal savings goals. A Member’s selected reward goal and the details saved when it was selected.

Proof photos. Pictures uploaded to show a chore is done, which in practice are usually taken by children.

Kinwick+ billing. If you subscribe, Kinwick stores identifiers from Stripe along with your plan, its status and the renewal date. Card numbers never reach Kinwick. Stripe collects them on its own payment page.

Push notifications. If you turn notifications on for a device, Kinwick stores that device’s push endpoint and encryption keys. Notification messages pass through the browser or device push service and may include names and titles on the lock screen. Kinwick sends pushes for announcements, chore and reward decisions, event requests, and calendar reminders.

Assistant questions. When a question needs Kinwick’s assistant provider, Anthropic receives the question you typed and a bounded history of typed query plans. It does not receive household records Kinwick retrieves, member directories, earlier answers, or the finished answer. Kinwick uses the returned plan to retrieve only records you are allowed to see and writes the answer on its own server. Kinwick does not use family data for advertising or model training, and does not opt in to Anthropic model training.

Ordinary server records. Kinwick’s hosting and database providers record IP addresses, browser and device details (such as user-agent strings), request times, and errors to keep the service running and secure. Supabase’s accessible service logs follow its plan retention: one day on Free, seven days on Pro, 28 days on Team, and 90 days on Enterprise. Auth audit records and provider backups may be kept separately from these service logs.

To see whether Kinwick is working and which parts families use, Kinwick keeps a few totals in its own database. No outside analytics company is involved.

Feature counts. How many times per day buttons such as Add chore, Request event, Import Google Calendar and the approval actions were used, and how often the Kinwick+ plans were viewed or chosen. Only the day and the total are stored, never who pressed the button or which household they are in.

Active households. Whether a household opened Kinwick on a given day. Only the household and the date are stored, nothing about who opened it or what they did. These records are deleted after 90 days.

Service health. Per-minute totals of requests to Kinwick’s servers, how many failed, and how long they took, grouped by part of the app. These carry no account, household or address and are deleted after 30 days.

Nothing that a Youth profile does is counted, not even as part of these totals. Only Kinwick’s operator sees the totals, and only as sums across all households. No one can look up a family, a person or a sequence of actions in them.

There are no third-party analytics, advertising or tracking scripts anywhere in the app. Kinwick does not profile anyone, does not track people across other websites. Kinwick does not collect your device’s location or address book. Calendar locations are read when an Admin chooses Google Calendar import or enables calendar sync. Technical device details appear in provider logs as described above.

Kinwick does not sell personal information, and does not share it for advertising. There is no circumstance in which a child’s name, chores or photos are used for marketing.

Kinwick uses strictly necessary cookies to keep you signed in, and nothing else. There are no advertising or analytics cookies, and no other company sets cookies through Kinwick.

Your browser also remembers your light or dark theme choice locally, so the app opens the way you left it.

To run the app: signing you in, showing your household its chores and rewards, and keeping Home Bucks balances correct.

To send the few emails the app needs — sign-in codes and email confirmations.

To deliver the push notifications you choose, including announcements, decisions about chores, rewards and event requests, and calendar reminders.

To take payment for Kinwick+, and to keep the service secure, such as limiting repeated invite-code guesses.

Kinwick separates household permissions from presentation. The permission roles are Admin and Member. Grown-up and Youth change how the app is presented, not what a Member is allowed to do. Youth and Grown-up Members have the same permissions.

Admins manage household members, chores, rewards and requests. Admin views also show member balances and Home Bucks history.

A Member’s personal savings goal is visible only to that Member. Admins cannot see it. A savings goal does not reserve Home Bucks, request a reward or purchase anything.

Family goals show aggregate progress for the household. They do not show individual contribution amounts or rankings.

Only Admins set a Member’s presentation. A Member without a saved presentation uses the Grown-up presentation and appears on the Admin setup list.

Kinwick is meant for households with children, and children have their own logins so they can see their own chores.

A parent or guardian creates the household and invites the child using a household invite. The parent or guardian manages the child’s use of Kinwick through the household’s Admin controls.

Kinwick shows no advertising to anyone, and children are never profiled or tracked.

Proof photos are stored privately. They are never public, never indexed by search engines, and can only be opened through short-lived links, valid for about five minutes, generated for people in the same household. Household members, including children, can view each other’s proof photos.

Photos are shrunk on the device before upload and limited to 250 KB each. The server rejects photos containing camera metadata such as EXIF. Archiving a chore keeps its photos for review and history; it does not delete them. Admins can delete a reviewed submission’s photo in chore details or history, or remove a member and delete their personal data. Household deletion also removes its photos.

An Admin can choose to connect Google Calendar for an import. Kinwick reads the selected calendars and date range, including event titles, descriptions, locations, dates, repeat rules, and attendee email addresses. One-time import does not write to your Google calendar.

Only events you choose to import are added to household content. Attendee emails are used to match household members and are not saved with imported events. Calendar data and the access token are held in an encrypted temporary import session that expires after one hour. The token is cleared when the import finishes. One-time import does not store a refresh token or keep an ongoing connection.

Calendar sync is a separate, optional Kinwick+ feature. Its connection creates a dedicated “Kinwick” calendar in the connecting Admin’s Google account. Sync reads and writes only that dedicated calendar, including event titles, descriptions, locations, dates, and supported repeat rules. It does not sync your other Google calendars or copy Kinwick attendee lists, reminders, pending requests, or private approval notes to Google. Synced events become household calendar content in Kinwick. People who can access the dedicated calendar in Google can see its content under that calendar’s sharing settings. People who can edit that calendar in Google can update approved events in Kinwick without another approval. Google deletions and conflicting edits require a household Admin’s review. Original request approvals and history remain in Kinwick.

Kinwick stores account and calendar identifiers, links between events, last shared versions, changes awaiting review, Admin sync decisions, and deletion records to keep sync reliable and prevent duplicates or deleted events returning. Household Admins can review conflicting changes. These sync records remain after disconnecting so reconnecting can use the existing links. Deleting the household removes its saved sync records from Kinwick.

The sync connection stores encrypted access and refresh tokens so Google access can be renewed without the Admin being present. Kinwick uses Google’s account identifier to reconnect to the same account and calendar. Tokens are available only to the server and are removed when the sync connection is disconnected. Disconnecting stops new sync requests. Sync also pauses if the household no longer has Kinwick+. A request already in progress may finish. Existing events and the dedicated Google calendar remain in place. If Google cannot process revocation, you can remove the grant directly in your Google Account connections.

Kinwick’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used only to provide calendar import and sync, never for advertising or training AI models.

You can revoke Kinwick’s access in your Google Account connections. Revoking access stops future reads and writes; it does not remove events already imported. Remove those using Kinwick’s calendar import controls.

Kinwick has a public demo that gives each visitor a temporary household of made-up sample data. It runs as a separate copy of Kinwick with its own database, apart from real households, and it never sends email.

Anything you change or upload in a demo is deleted with the demo household, within a day of the demo ending. To stop one person from starting a large number of demos, the demo keeps a keyed hash of your IP address for about a day. It never stores the address itself.

Kinwick is built on a small number of services. Each one only handles what it needs to, and none of them may use your data for their own purposes.

Supabase stores the database, accounts and photos. Vercel runs and serves the app. Stripe processes Kinwick+ payments. Anthropic turns assistant questions into typed query plans. It does not receive the household records Kinwick retrieves or the finished answer. Resend, using Amazon SES, delivers the app’s emails. Cloudflare manages the domain.

Kinwick is hosted in the United States. If you use it from elsewhere, your information is processed there.

Household content is kept while the household exists, so chore and Home Bucks history stays intact for the people still using it.

Leaving a household removes you from it and detaches your name from the history you leave behind. Deleting your account removes your profile and your login. Deleting a household removes its content, including its photos. An Admin’s “Remove member and delete their data” action deletes proof photos and personal savings goals and replaces the member’s profile with an anonymous history record. A login created and managed for the household is deleted too; an ordinary invited account keeps its login.

Completed proof photos are deleted by daily cleanup once they are older than 30 days after review, or completion when no review was needed. Pending and rework-required photos are kept so work can still be reviewed. Copies may survive in provider backups and logs until their separate retention periods end.

Daily active-household records are deleted after 90 days and service health totals after 30 days. Feature counts are daily totals with no person or household attached, and are kept.

Everything travels over HTTPS. Passwords are hashed. The database enforces rules, checked on every query, that stop one household from reading or changing another household’s data. Photos live in a private store. Card details are handled entirely by Stripe.

Kinwick is a small project rather than a company with a security team, and it would be wrong to promise perfect security. Problems can be reported to privacy@kinwick.app.

You can change your display name and color in settings, leave a household, or delete your account from inside the app.

You can also ask for a copy of what Kinwick holds about you or your child, ask for corrections, or ask for deletion, by emailing privacy@kinwick.app. Expect a reply within 30 days.

The date at the top shows when this page last changed. Anything significant will be announced in the app or by email before it takes effect.