Privacy notice
Advenchores helps households organize routines, chores, progress and rewards. This notice explains the information used to provide that service and how to contact its operator.
Support and privacy requests: hello@kasnet.us.
Information used by the service
- Sign-in information. Clerk provides account authentication. If you choose Google or Facebook sign-in, Clerk and that provider process basic identity information such as your account identifier, email address and profile information, according to your chosen connection and their settings. The Advenchores application stores the Clerk identity identifier and its association with a household. Your Google or Facebook password is not provided to Advenchores.
- Household information. The household name, time zone, participant names or nicknames, adult/child profile choices, chosen avatar, settings, and invitations you create.
- Activity information. Chore and routine definitions, checklist steps, schedules and assignments, completions, approvals, corrections and notes, progress/XP, optional in-app Coins, rewards and reward requests. These records support shared household history and prevent duplicate credit. In-app Coins are not a payment account.
- Security information. Session identifiers and expiration, authorization and parent-unlock state, hashed parent PINs, hashed invitation codes, and rate-limit records. Where a legacy local-password account is used, its password is stored as a salted hash.
- Feedback and support correspondence. If you use the in-app feedback form, the service stores your chosen category, message, submission time and its household association. Submissions are private to the operator for support and product improvement; they are not a public forum or included in other households' views. The form does not automatically attach screenshots, chore content or participant names. Please leave unnecessary identifying details, passwords and parent PINs out of your message. Information you send to the support address is also used to handle your request.
- Technical data. Hosting, network and authentication providers process technical information such as IP addresses and browser/request details to deliver and protect their services; their retention practices may differ from those of the application.
How information is used and shared
Information is used to authenticate accounts, maintain household access, show assigned work and progress, record household decisions, provide support, prevent abuse, and back up or recover the service.
Household information is accessible to people with authorized access to that household. A selected child or adult profile is not a separate private space from the rest of the household. Parent controls restrict administrative actions; they are not a guarantee that each participant's activity is hidden from other authorized household users. Signing up does not itself give access to another household.
The operator may access information when needed for support, security, recovery, or handling a verified data request. Service providers process information as needed to operate their parts of the service. The application does not include advertising pixels or session recordings.
Website and onboarding analytics
Cloudflare provides website traffic and performance analytics. We also use a small first-party funnel to understand whether visitors open the homepage, try a sample quest, select a start button, open sign-in, reach an authenticated session, or create and enter a household. A successful sign-in observation is not treated as proof of a new registration.
This optional funnel uses a random, temporary identifier in sessionStorage for the current browser tab, fixed event names, coarse device categories and a restricted set of source and campaign codes. It does not send names, email addresses, provider or household identifiers, passwords, form contents, chore or reward text, full URLs, raw referrers, IP addresses or user-agent strings to the first-party analytics store. The identifier is cleared when the tab enters a household or identity is cleared; it is not a cross-site or cross-device identity. Optional event tracking stops at household entry.
Temporary first-party event records expire after seven days through automated cleanup. Reports show aggregate counts and estimated tab-level funnels, not a list of identifiable visitors. The operator may separately summarize existing service records, such as counts of households with saved tasks or completion history, without joining those records to anonymous browsing identifiers. These operational summaries do not change the underlying household retention described below.
The first-party funnel honors browser Global Privacy Control and Do Not Track signals. Optional analytics failures do not prevent sign-in or household use. Infrastructure and authentication providers may still process technical information needed to operate and secure the service. The operator-only analytics report is not publicly accessible.
Authentication and infrastructure providers
Clerk handles authentication; Google or Meta/Facebook participates if you select its sign-in method. Vercel serves the public web front door and policy pages. Cloudflare is used for network infrastructure and website analytics and may provide connection-security checks through the authentication flow. These providers have their own privacy notices:
The household application does not request access to your Gmail messages, Drive files, Calendar events, Facebook posts or friends list for basic sign-in.
Cookies and device storage
The application uses a session cookie for authentication and security. Clerk and its security integrations may use their own cookies or browser storage for sign-in and abuse prevention. The current household application does not deliberately persist household records in localStorage or IndexedDB or queue offline changes. A downloaded export or a browser/device copy you retain is outside the operator's direct control. Use trusted devices and sign out on shared devices.
Parents, guardians and child profiles
The account-creation and household-management flow is intended for adults. A parent or guardian can create participant profiles for children without giving each child an email address or a separate Google/Facebook account, and should supervise their use.
Use nicknames where practical. Do not enter unnecessary identifying or sensitive details, including a child's full birth date, school, address, medical information or private contact details, into chore names or notes. Parents or guardians can contact the operator to request access, correction or deletion concerning their child's information. Identity and authority must be verified before information is disclosed or removed.
Retention, backups and security
Household records remain available while the household uses the service unless removed through a supported request or operational change. Completed and corrected activity may remain in history; hiding or archiving a chore or reward is not the same as deleting its records. There is no fixed automatic household-expiration period in the current application.
Backups may contain earlier records, including security data. A deletion request is not a promise that every backup copy disappears immediately. The operator will explain any retained information and applicable limitations when handling a request. No fixed backup-erasure deadline is promised by this notice.
Access controls, hashed authentication secrets, encrypted HTTPS connections when deployed, and private backups are used to reduce risk. No online service can guarantee complete security. Never send a password, PIN, sign-in code or client secret in a support request.
Your choices and requests
Household administrators can edit supported profile and task settings and use the parent-authorized household export. This export is a readable current household view, not a complete database dump or a restorable backup. Changes to visible text do not necessarily remove earlier copies in activity history, definition snapshots or command records. To request access, correction, account unlinking, or deletion, email hello@kasnet.us. See the data deletion instructions for the information needed and the difference between provider disconnection and household deletion.
Changes to this notice
Updates will be posted on this page with an updated date. Contact hello@kasnet.us with questions about this notice or the handling of your information.