Tivoraly
Log In
Draft for approval

Proposed Legal Centre wording

Not effective policy. Existing versions and acceptances remain unchanged.

Read effective policies

Tivoraly privacy and Google Play preparation — 29 October 2026

Changes in Preview

  • Replaced public Privacy, Child Privacy, Cookies and AI presentation with checked-in, owner-requested factual wording. Added collection/purpose categories, optional child details and uploads, AI request context, location precision, providers, analytics/marketing, access requests and deletion limits.
  • Corrected Basic/Pro descriptions, eligible seven-day trial language, complimentary Basic/Pro references, AU/US tax-inclusive advertised totals and existing-subscription currency language. Preserved refund, consumer-rights and other operative billing provisions; no billing change.
  • Preserved immediate eligible completion rewards and optional later parent review. Removed hypothetical child messaging/participation controls and complete-export promises.
  • Added public /account-deletion instructions, support request alternative, footer/Legal Centre links and a Privacy Policy entry in the native parent More menu. Existing signup Privacy links remain.
  • Separately labelled the 29 October presentation review date. Shared effective versions, acceptance records and legal-review flags remain unchanged; no new effective policy version was installed.

Evidence and limits

Read-only shared queries retrieved current published policies (Privacy/Cookies 1.1, AI 1.2, Child/Membership/Terms 1.3 and AU/US supplements) and retention categories. Every returned retention period is still Requires legal review. Bucket metadata confirms learning-evidence, nearby-photos and worksheet-uploads are private. No private family rows, files or customer billing records were read for this task.

Source review: learner-context.server.ts and prepare.functions.ts attach saved nickname, age/year, interests, learning/support/engagement context to requested AI; AI transports use the Lovable AI Gateway. This does not establish a provider's retention/training agreement. The retired import source file's existence is not evidence of an active advertised feature.

features/analytics/{analytics,config,provider,events}.ts(x) configure GA4, Clarity and Meta Pixel with environment identifiers and consent gates; the root mounts AnalyticsProvider. This materially contradicts stored categorical “no advertising cookies / anonymous-only logging” wording. Live identifiers, provider-side settings, historical collection and a release-specific network inventory were not verified. The revised policy is conditional rather than asserting all three run in Live.

Nearby location.server.ts processes typed Google Places queries and rounds area centres to three decimals; features/nearby/store.ts stores preferences locally. The Android manifest has camera/audio permissions, not coarse/fine location; no operative GPS lookup was found in this review. Voluntary addresses, typed areas and network metadata are not equated to absence of all location processing.

account.functions.ts schedules a 30-day restoration deadline after cancelling billing. deletion-cleanup.server.ts removes owned files before erasure and can hold failed cleanup for staff. purge-launch.server.ts remains false/inactive. No new claim of active purge suspension or exact-time deletion was made. External workers/privileged paths and deployed server equivalence were not re-certified.

This is current source plus shared policy/configuration evidence, not certification that all Preview changes are already Live. No paid requests, customer writes, policy-store changes, migrations, games/account changes or publication.

Google Play requirements still unresolved

  1. Owner/legal entity and contact: Confirm the legal operator identity displayed in policy/store listing and privacy contact process. Existing [email protected] is reused, not invented.
  2. Retention and providers: Approve actual category periods, backup erasure, provider/subprocessor names/locations, AI retention/training/human access, email retention and request handling. No invented schedule or no-training promise.
  3. Children/Families: Confirm actual target ages and direct Child Mode use; obtain qualified AU/US child privacy/COPPA consent review. Audit child/unknown-age analytics/SDK identifiers and Clarity masking. The current analytics loader has no child-age gate: parent consent and event filtering alone do not establish Families compliance. This task changes wording only, not tracking behaviour.
  4. Data Safety form: Map the shipped Android build and backend providers for parent identity, optional child profile/support details, learning/user content, photos/video/audio/files, approximate/location-related data, account/payment identifiers, device IDs and diagnostics. Determine required versus optional collection, sharing/service-provider exceptions and purposes using Google's definitions. Confirm encryption-in-transit operationally before answering; HTTPS URLs alone are not a complete attestation.
  5. Account deletion: Publish an approved public deletion resource and verify the in-app request/support process on the actual Android build. Confirm final deletion timing/exceptions and operator worker coverage. This Preview URL is not yet a publicly released Play deletion URL.
  6. Android sensitive permissions: Confirm camera/microphone disclosure and runtime requests match actual capture/voice workflows and any prominent consent requirements. Manifest evidence is not a physical-device check.
  7. AI reporting: Assess whether AI-Generated Content rules apply and whether the shipped app provides the required in-app reporting/feedback for covered generated content; a support link is not a verified substitute.
  8. Payments: Verify Play release never sells or steers to Stripe digital-membership checkout outside an applicable enrolled exception. No native purchase flow was changed or certified here.
  9. Release consistency: Approve final policy version/effective date, notices/reacceptance and publication separately; confirm Play Console links and Data Safety answers match the exact app/website release. Existing review flags remain intentional, not a claim of readiness.

Official Google references

Follow-up implementation audit — 29 October 2026

Assessment: not ready to claim the remaining privacy issues are resolved. This focused audit used source, existing read-only evidence and official provider documentation. It did not inspect customer records, access vendor account settings, run deletion/payment/provider operations or verify a shipped Android binary. “Source verified” below means the inspected application implements that behaviour, not that the published release or every privileged pathway matches it.

Analytics and withdrawing consent

  • Source verified: GA4/Clarity load after analytics consent; Meta Pixel after marketing consent. Missing identifiers prevent loading. Default consent denies both; choices/version/timestamp are stored locally and expire after 365 days. GA4 receives page path/title/location and allowed product-event fields; Meta receives page views and mapped registration/trial/payment/search events. Vendor scripts can additionally process network/device/cookie/interaction data. Clarity supports session recordings. No vendor account settings or actual historical collection were verified.
  • Evidence: src/features/analytics/analytics.ts:45–146, consent.ts:20–85, events.ts:1–84, provider.tsx:17–36. GA settings disable signals/ad personalisation, but do not prove anonymity. Some DOM masking and a comment recommending project-wide masking are not proof of the provider's masking configuration.
  • Policy accuracy: vendor/category disclosures were already conditional and accurate. Corrected withdrawal wording: applyConsent only loads permitted vendors; it does not revoke vendor consent or unload existing scripts. Consent-gated application events stop, but vendor collection in the current page may continue. Added page/title transmission and local choice expiry.
  • Code versus wording: stopping already-running vendor collection reliably requires a separately approved code change and vendor-specific validation; wording alone does not fix it. A child/unknown-age exclusion is also absent. No tracking code was changed.
  • Decision/confirmation: decide which optional vendors to retain, and whether tracking should be excluded from all signed-in family/Child Mode surfaces. Confirm enabled production identifiers, project-wide masking, retention and deletion settings. Do not use this audit as evidence that optional trackers are enabled in Live.

Android tracking and permissions

  • Source verified: capacitor.config.ts:13–27 bundles screens locally and has no remote server.url. The web tracker environment check permits production domains or explicit debug mode (src/features/analytics/config.ts:14–40); it does not explicitly distinguish native use. Reviewed direct dependencies contain no dedicated analytics SDK. The checked-in Android manifest declares network, camera and microphone permissions, not coarse/fine location. Google Services is conditional in android/app/build.gradle:48–53.
  • Data: website-style tracking could occur in allowed hosted pages or debug-enabled contexts. Capture/voice features can process selected photos/audio; manifest permissions alone do not prove collection or runtime permission prompts. Backend processing still occurs regardless of whether optional web tracking loads.
  • Policy accuracy: added these qualified source facts, not a “no Android tracking” claim. Final transitive SDKs, merged manifest, bundled settings, installed-app traffic and Play Data Safety answers remain unverified.
  • Code versus wording: a release-specific Android network/permission review is needed before deciding whether changes to native tracking or permission disclosures are required. No Android code was changed.
  • Decision/confirmation: confirm intended child age audience and provide the exact release for verification; decide the native optional-tracking policy. Source-only inspection cannot certify a Play release.

Children, parent authority and notice acknowledgement

  • Source verified: email signup combines Privacy/Child Privacy acknowledgement and separately requires Terms (src/routes/sign-up.tsx:110–116,343–367). src/features/legal/acceptance.ts:17–33,39–53 records account/document version, acknowledgement details, country/locale, source page and browser user-agent where supplied; parent responsibility records are separate. This is not verified parental authority or age verification. Acceptance failure handling and social-signup equivalence were not certified in this audit.
  • Data: saved profile write/read paths include interest strength, parent/support/avoid notes, flow supports/notes and structured engagement preferences (src/lib/learners/learning-profile.functions.ts:20–45,77–98). learner-context.server.ts:43–98 reads these plus confirmed preferences and builds AI context. Learning records, optional uploads, rewards and child-facing assistance may add further content. Support/engagement text can reveal sensitive information.
  • Policy accuracy: expanded the optional-child-data inventory and acknowledgement metadata. Replaced the absolute assertion that children “cannot independently sign up” with the adult-account requirement and explicit lack of independent age/authority verification. Child profiles still have no separate sign-in. Added the concrete absence of a Child Mode analytics exclusion; parent cookie consent can persist into child use.
  • Code versus wording: consent/age/authority controls and child tracking restrictions need a separately approved implementation if qualified review requires them. Do not describe a checkbox, PIN or payment card as sufficient legal parental consent. Existing access controls and rewards were untouched.
  • Decision/confirmation: confirm the intended ages, obtain qualified AU/US child-privacy/consent advice, and decide what optional sensitive context families should be invited to provide and send to AI. No compliance conclusion was reached.

Third-party processing, retention and backups

  • Source verified: AI transports target the Lovable AI Gateway (for example src/lib/ai/responses.server.ts:22); saved child context is assembled by the app. Firecrawl/Places receive feature-specific search/location requests; app messages use the managed sender (src/lib/email-templates/send-email.ts:35–69). Auth emails are a separate path. These source facts do not identify the complete downstream contractual processor chain or deployed settings.
  • Data: prompts/context, selected report/activity content and import/voice material where offered; search queries and typed places; recipient/address and message content for email; account/learning/files for cloud services. Application usage logs and opted-in AI result reuse can also retain outputs separately from external providers (src/lib/ai-usage/limits.server.ts).
  • Policy accuracy: existing explicit unknowns remain accurate; no no-training, no-retention, fixed-region or complete-provider-erasure promise was added. Cloud documentation describes daily database-only backups retained up to roughly 14 days, excluding storage files; that is generic service documentation, not this project's verified backup inventory or deletion commitment.
  • Provider evidence: Lovable DPA and subprocessors need confirmation of applicable contract/product scope. Firecrawl security describes enterprise/opt-in zero-retention controls, not a verified setting for Tivoraly. Google Places policies describe API use rules, not this project's retention agreement. Direct OpenAI/Anthropic API terms must not be assumed to govern a Lovable-mediated request.
  • Code versus wording: provider settings/contract clarification and an approved retention schedule come first; minimisation/redaction or automated retention enforcement may then need code changes. This audit did not change transport, caching, model selection or retention behaviour.
  • Decision/confirmation: confirm legal operator, applicable provider agreements/subprocessors/regions, training use, prompt/log/email retention, human access and deletion terms. Approve real category-specific retention periods only after confirming they can be honoured.

Account deletion, restoration and retained data

  • Source verified: grown-up/email-confirmed requests cancel billing before setting a 30-day deadline (src/lib/account/account.functions.ts:19–67). Restoration uses the existing pending-deletion flow; source is not proof of full deployed race/deadline enforcement. The cleanup worker holds on failed/uncertain file removal and attempts files before final erasure (deletion-cleanup.server.ts:44–145). The Preview suspension flag is false (purge-launch.server.ts:2). Prepared pause text is an unused export (deletion-notice.ts:1–2), not evidence of an active pause. /account-deletion imports its instructions directly and invokes no deletion action.
  • Data: pending accounts/files remain until removal; published/shared material, operational records and one-way trial-use identifiers may receive different treatment. Hashing is not proof of anonymity. Provider copies/backups are not erased by assumption.
  • Policy accuracy: qualified the file-first promise as the application worker's design, not all privileged/scheduled pathways. Retained the 30-day window, no guaranteed erasure timestamp, no automatic billing restart and no active-pause announcement. Existing evidence identifies independent privileged/database pathways; current operator coverage/drain remains unconfirmed.
  • Code versus wording: coordinated operator/pathway controls and any required restoration-race fix need separate approval. Publishing pause wording without a proven coordinated pause is not safe. No deletion, worker, database or customer data changed.
  • Decision/confirmation: confirm the responsible operator and complete pathway coverage/drain before any purge-status announcement; approve actual retention exceptions and request handling. The 10 November review date is a proposal, not an automatic restart or currently activated suspension.

Data access and export

  • Source verified: reports are selected editable snapshots, with learning/progress/portfolio/activity/custom types (src/features/reports/types.ts:2–15, sources.ts:161,380–400). Available report/document downloads are not an all-account export; src/routes/trust.tsx:167–172 already says this. A project-owner database export is not a family-facing export and can include other families; it must never be supplied as an individual privacy response.
  • Data: downloads contain selected learning records/documents, not necessarily all profiles, preferences, authentication/billing/operational records or original files. The support link requests handling; it does not implement or verify a complete fulfilment workflow.
  • Policy accuracy: the existing “not a complete account-data export” and support-request wording is accurate. No new export capability, completeness, response deadline or format is promised.
  • Code versus wording: decide and document a secure, identity-verified, family-scoped manual fulfilment process. A self-service complete export is a separate feature requiring approval, not necessary to pretend existing downloads are complete.
  • Decision/confirmation: choose who handles requests, which data/files can be supplied, secure delivery and applicable response deadlines; obtain qualified advice on rights/exceptions.

Focused verification for this follow-up

Three existing network-blocked legal boundary tests passed; stored input/metadata and unrelated documents remain unchanged. Signed-out Chromium read Privacy, Cookies, Child Privacy, account-deletion and legal-review pages: all HTTP 200 with the corrected disclosures present in the rendered main content and zero page errors. The initial network-idle wait timed out; repeating with document/visible-text waits passed. Cookie screenshots still showed a loading view despite the successful text checks, so visual screenshot verification is inconclusive and is not claimed. Preview compilation reported build OK. No tracking scripts were deliberately enabled, no installed Android test was performed, and no provider settings, customer records, shared legal records, account/billing/game functionality or publication were changed.

Verification

Three focused presentation-boundary tests passed: stored input/acceptance metadata unchanged; unrelated policy and unrelated country supplement preserved. Signed-out Chromium opened Privacy, Child Privacy, Cookies, AI, Membership, Terms and account-deletion pages (all HTTP 200), clicked Privacy → deletion and homepage footer → Privacy, with zero page errors. Legal/deletion pages are now exempt from the country-selection overlay, so direct privacy requests are readable immediately. Screenshots of the Cookie and deletion pages were inspected. Preview compilation reports build OK.

Android parent More now contains a dedicated Privacy Policy link; signup links were already present. No signed-in session was created and no installed Android/physical-device launch or Play Console link check was performed. No full account deletion, real subscription or native release test is authorised or claimed.

Proposed Legal Centre wording — 26 October 2026

Draft for owner approval and professional legal review. Not effective policy. No policy version, effective date, acceptance record, membership, billing, reward or database record has been changed by this review. Publishing the website and activating policy versions are separate decisions; neither has been authorised here.

1. Exact proposed Terms of Use wording

Replace clause 4 with the following, retaining the existing numbering:

4. Educational resources and compliance — what Tivoraly provides

Tivoraly is a resource discovery, planning and learning-support platform. It is not a complete curriculum provider, school or accredited educational institution.

The Practice Worksheet Generator, Prepare Learning, activities, projects, lesson-planning tools and AI-assisted tools provide supplementary resources and support. Using these features, individually or together, does not guarantee a complete curriculum or an education program that meets the legal requirements applicable to your family. Tivoraly does not guarantee subject coverage, curriculum alignment, year-level completeness, educational outcomes or compliance with local homeschooling requirements.

Independent providers listed through Tivoraly may offer complete curricula. This clause concerns what Tivoraly itself provides or guarantees; it does not mean that a third-party curriculum is necessarily incomplete. You should assess any provider's claims and resources directly.

Parents and guardians are responsible for researching and meeting the registration, curriculum, assessment, recordkeeping and reporting obligations that apply where they live. Consult the relevant education authority for current requirements. Review generated materials before use, including rule-based worksheets and AI-assisted materials, because they may contain errors or omissions, and adapt them to your child's needs.

Tivoraly does not provide legal, medical or psychological advice or professional educational assessment or certification. Nothing in this clause excludes, restricts or modifies mandatory consumer rights, including any applicable Australian Consumer Law guarantees or United States consumer protections that cannot lawfully be excluded.

Replace clause 5 with:

5. Parent responsibility

You remain responsible for curriculum selection and educational decisions; the obligations described in clause 4; reviewing resources and generated materials before use; supervising your child; and deciding whether an activity, resource, meet-up or external site is appropriate for your child. Tivoraly's planning and recordkeeping tools support, but do not replace, those responsibilities.

Replace clause 12 with:

12. AI-assisted content

AI assists with some planning, activity preparation, suggestions, summaries and explanations. The Practice Worksheet Generator uses rule-based worksheet builders, not AI. AI output may be incorrect, incomplete or out of date and must be reviewed by a parent before use. The educational-resource limitations in clause 4 apply to both AI-assisted and non-AI resources. See AI Transparency for the active uses of AI and the information processed.

2. Affected documents and exact proposed corrections

These are targeted replacements or additions, not wholesale policy rewrites. Existing consumer-rights, appeal, ownership and review protections remain. Version numbers, material-change classification, notices and any renewed acceptance must be decided before activation.

Membership, Trial & Billing Terms (current global version 1.3)

Replace the Basic and Pro bullets under Plans:

  • Basic — family organisation, manual activity creation, My Activities, Lesson Planner, existing saved worksheets, printables, learning records and editable reports. Basic does not include the Practice Worksheet Generator or Child Mode.
  • Pro — everything in Basic, plus Prepare Learning, AI-assisted weekly planning, AI activity import through Add an Activity, the rule-based Practice Worksheet Generator, Child Mode, the Earn-to-Play Arcade and optional AI-assisted report summaries. AI-assisted features remain subject to their applicable access and fair-use limits. Practice worksheet generation does not use AI or the AI generation allowance. PDF worksheet uploads are currently available only to eligible Pro tester accounts, not all Pro members. The retired paste-to-worksheet tools are not available.

Replace the final sentence under Payment, currency and regional pricing:

Changing your country or display preferences does not automatically change an existing subscription's billing currency, billing interval or child add-on pricing. The billing terms confirmed for your subscription continue to apply unless you explicitly arrange a subscription change.

Replace the first sentence under Renewal timing:

Subscriptions renew automatically at the end of the billing period until cancelled. Your payment provider's billing dates determine renewal, including any adjustment where a month does not contain the original billing day. The next scheduled renewal date is shown with your membership details.

Keep seven-day trial wording and current Basic/Pro and additional-child prices: reviewed configuration agrees for Australia and the United States. Keep mandatory consumer rights and the existing refund commitments; no refund automation or legal sufficiency was verified, and no entitlement should be weakened through a wording correction. Counsel should review automatic-renewal notices, price-change consent and the refund procedure.

Privacy Policy (current global version 1.1)

Replace the learner-profile table row:

Learner profiles: required nickname; optional age range, year or grade, country/region and curriculum details, interests, learning preferences and support notes | To organise and personalise family learning and, when you use an AI-assisted feature, provide relevant learning context

Replace the technical-logs purpose:

To keep the Service running, detect abuse and manage the account's two-device limit and sessions

Replace the uploaded-files row:

Supported uploads, including activity-import material, learning evidence, paintings and eligible PDF worksheet originals and annotations | To provide the features you choose to use; material submitted to an AI import or other AI-assisted feature may also be processed as described below

Replace the AI-processing bullet:

AI processing — when you use an AI-assisted feature, we send the information needed for that request to our AI service providers. Depending on the feature, this may include your prompt or lesson topics, relevant learner nickname, year or age range, interests, learning preferences or support information, activity content, conversation context, selected report records, and text, images or files you submit for AI processing. Not every request uses every category. Device read-aloud, manual planning, rule-based practice worksheet generation and PDF annotation do not themselves send their content to AI. Avoid including unnecessary identifying or sensitive details. See AI Transparency. Provider processing locations, retention and any training-use restrictions require confirmation before publication; we do not make an unverified no-training promise.

Add a contact-enquiry table row:

Contact enquiries: name, email, subject, message and related delivery/abuse-prevention records | To respond to enquiries, send an acknowledgement and protect the contact form from abuse; enquiry records are not public

Replace Retention and deletion:

We keep information while your account is active and for the purposes described in this policy. Requesting whole-account deletion cancels an active subscription immediately and schedules permanent account removal for 30 days after the request. You can cancel the pending deletion from Account settings before the scheduled removal; restoring the account does not automatically restart a cancelled subscription. This is different from ordinary membership cancellation, which stops future renewal while access continues for the applicable trial or paid period.

Permanent removal deletes private family records and owned files through our deletion process. Deliberately published shared community projects may remain, with the account link removed where applicable. Protected one-way trial-eligibility records and limited anonymised or operational records may also remain for their stated purposes. Exact retained categories, backup handling and retention periods require a final approved retention schedule; the Trust Centre currently identifies periods that are still being confirmed. We do not promise that all information is erased immediately or exactly at the scheduled time.

Archiving a PDF worksheet does not delete its original or annotations and does not free its storage allowance. Individual-item and learner deletion have their own confirmation and cleanup paths; the account's 30-day restoration period is not a promise of recovery for every individual deletion.

Replace the account-export sentence under Your rights:

You can access and correct information using available account tools and request access, correction, a copy or deletion of your information by contacting us. Available report and document downloads are not a complete account-data export. Depending on where you live, additional privacy rights may apply as described in the country supplements.

AI Transparency (current global version 1.2)

Replace Where AI is used:

Active AI-assisted tools include Prepare Learning and requested refinements, weekly planning, Pro activity import and related learning-link suggestions, saved-activity step help, the Help assistant, optional report summaries, US course-description assistance and nearby mission drafting. Some saved-step voice input may use a paid transcription fallback where offered. Internal curriculum/state research and group-listing screening also use AI; these are distinct from a family's requested learning generation.

Manual activity creation and planning, ordinary activity/project participation, rule-based Practice Worksheet Generator output, PDF annotation and Arcade gameplay do not themselves require AI generation. Retired worksheet and project-generation entry points are not current advertised tools. AI is optional across the platform overall, but using a named AI-assisted tool can involve third-party processing.

Replace Data sent to AI services with the AI-processing paragraph proposed for the Privacy Policy, then add:

AI-assisted and rule-based learning resources are supplementary, not a complete curriculum or a compliance guarantee. The Terms of Use educational-resource clause applies. Review outputs for accuracy, suitability and omissions before use. AI screening of a listing is a moderation signal, not verification of its organiser, credentials or safety.

Do not advertise the proposed eight-credit allowance or a US$2 enforced family limit: spending enforcement remains disabled. Existing feature-specific limits continue. Replace absolute promises that every output is labelled, conflicts are always detected, or all safety guidance can never be removed with:

Tivoraly uses source and AI labels where the relevant feature provides them and instructs AI tools to retain required safety guidance. Labels and automated safeguards are not guarantees of accuracy, completeness or safety. Parents should check important claims, instructions and supervision needs themselves.

Child Privacy Notice (current global version 1.3)

Retain the approved detailed distinction between required nickname, optional profile fields and optional private evidence uploads currently supplied by the presentation adapter. Replace “can be protected with a PIN” with:

Child Mode presents child-facing features within the parent account and requires the grown-up PIN to return to parent controls. It does not replace adult supervision.

Replace the Rewards and Parent review paragraphs:

Rewards: Eligible learning completion awards rewards immediately under the activity's configured rules; optional later parent review does not delay or remove rewards already earned. Parents can set household playtime-reward defaults, set or restore an individual saved activity's override (including zero), and separately disable the mission-evidence/reflection bonus. When enabled, an eligible evidence/reflection bonus can be earned even if the ordinary activity reward is zero. Playtime uses the existing conversion of five coins to one minute; Adventure Points are separate. Changes affect future eligible rewards, not existing balances. Earned or parent-added playtime and parent game limits govern Arcade play, including continued editing of saved paintings; simply viewing a saved painting is free.

Parent review: Parents can review saved work and use the available feedback or removal controls. Review is not a prerequisite for the immediate eligible completion rewards described above and does not reverse them.

Replace unsupported participation/communication-setting promises in Terms clause 6, Child Privacy's Private by default/Your controls and the Trust policy with:

Children use learner profiles within the parent account. Child Mode does not provide a child community-posting or child-to-child messaging feature. Parents manage available child-facing activities and settings; private evidence is not made public merely by completing or submitting work.

Retain the existing disclosure that formal US child-privacy/COPPA review has not been completed. Parent account ownership and PIN protection alone do not establish legal consent or compliance.

Community Guidelines (current global version 1.2)

Add under Independent activities:

Organiser-submitted group listings use rules and AI-assisted publication screening. Lower-risk non-care listings may publish automatically; uncertain or failed AI screening is referred for review. Childcare and drop-off listings are routed for staff review before first publication. Separate Things to Do submissions use manual review. These publication checks do not verify registration, background checks, suitability, insurance or safety, and publication must not be understood as Tivoraly approval or endorsement.

Organisers are responsible for accurate listing information, keeping it current, appropriate supervision arrangements and any registration, screening, permissions or insurance obligations applicable to their own service. Families should independently confirm these details with organisers and relevant authorities before attending or leaving a child in another person's care. Tivoraly does not offer bookings or collect payments for these listings.

Do not promise every material edit is re-screened: the current screened-field list omits changes solely to group type, parent-attendance and care declarations. This is an implementation risk for separate approval, not corrected by this review.

Provider & External Content Policy (current global version 1.2)

Add after Independent providers:

Independent providers may offer complete curricula or individual resources. Tivoraly's listings, comparisons and learning-support tools do not certify their completeness, alignment or suitability for a family's obligations. Check the provider's own description and the relevant education authority's requirements. Tivoraly's own educational-resource limitations are described in the Terms of Use.

Keep provider ownership, attribution, Request an Update review and consumer protections unchanged. Professional review should assess broad external-content exclusions and rights to indexed descriptions, logos and images.

Australian and US supplements

Replace the homeschool-requirements bullet in each Terms supplement:

  • Australia: Registration, curriculum, assessment, recordkeeping and reporting requirements differ by state and territory. Tivoraly's supplementary resources do not certify compliance. Consult your relevant state or territory education authority for current requirements; clause 4 of the global Terms applies.
  • United States: Notification or registration, curriculum, assessment, recordkeeping and reporting requirements vary by state and circumstances. Tivoraly's supplementary resources do not certify compliance. Consult the relevant education authority for current requirements; clause 4 of the global Terms applies.

Preserve existing Australian Consumer Law and mandatory US consumer-rights provisions. Keep unresolved US automatic-renewal, COPPA and DMCA review disclosures. The Australian Privacy supplement's categorical APP, overseas-safeguard and breach-notification claims need a qualified applicability and operational review, not invented assurances. The US Privacy supplement's statutory rights, response/appeal process and applicability also need counsel confirmation. No broader supplement rewrite is proposed without that review.

Other affected Legal Centre documents

  • Acceptable Use 1.2: replace “bypass single-session controls” with “bypass account device limits or session access controls”.
  • Cookie Policy 1.1: replace “single-session controls” with “account device limits and session security”. Replace the Operational row's opt-out claim with: “Browser storage can be cleared; this does not necessarily stop server-side operational or security logging.”
  • Trust policy 1.2: replace the parent-controls bullet with “Parent controls: review, available document downloads, access requests and deletion.” Replace the child-safety bullet with the verified no-child-posting/no-messaging paragraph above. Add the short educational-resource explanation below.
  • Copyright/IP and Copyright Complaint Process 1.2: no factual educational-resource addition needed. Preserve the unresolved DMCA status. The ordinary 14-day platform appeal is not a verified statutory DMCA counter-notice procedure.

3. Exact shorter explanations staged in Preview

Trust Centre and general Help guidance

Tivoraly helps you discover resources, plan learning and practise skills; it isn't a school or a complete curriculum provider. Our worksheets, prepared activities and planning tools are supplementary, whether you use one or several. Review materials before use and check subject coverage and your registration, assessment, recordkeeping and reporting requirements with the relevant education authority. Independent providers listed here may offer complete curricula; check their own details. Your mandatory consumer rights are unchanged.

Practice Worksheet Generator guidance

Practice worksheets support individual skills, not a complete Maths or English curriculum. Review the questions and answers before use, and check that your wider learning plan covers your child's needs and local requirements. Choosing a year or grade does not certify curriculum alignment or completeness.

Prepare Learning guidance

Prepare Learning turns your chosen topics into supplementary activities; it does not check that a complete curriculum or legally compliant program has been covered. Review each draft for accuracy, suitability and missing material, then check your wider plan against the relevant education authority's requirements.

The two tool explanations appear in their existing Help guidance, linked once from each parent tool page. No repeated warnings in child activities, printed questions or gameplay are added.

4. Contradictions found and evidence

Read-only inspection retrieved current published global policies and AU/US supplements from the shared policy store on 26 October. Terms/Membership/Child Privacy are 1.3; the other core documents are 1.1 or 1.2. All retrieved policies still carry professional-review flags. Live server-code equivalence was not independently tested.

  • Trial duration is correct now: stored global Terms and Membership say seven days, as do AU/US active Basic/Pro plan settings. Historical migration text with fourteen days is not evidence of current operative duration. Checkout passes the configured value to Stripe (src/lib/membership/billing.functions.ts, configuredTrialDays/effectiveTrialDays). No new Stripe checkout or provider call was made.
  • Billing-region contradiction: Membership says changing region applies next period; account wording and subscription binding pin existing billing currency/country (src/routes/_authenticated/account.tsx; src/lib/membership/billing.server.ts). Current Basic/Pro and additional-child prices match legal text; legacy family/child rows are not current Basic/Pro offers.
  • Feature descriptions: stored Membership advertises generic worksheets/import; src/features/legal/presentation.ts already corrects public display but not accepted stored text. Practice is deterministic and Pro/grown-up gated (src/lib/worksheets/practice.functions.ts); PDF creation remains tester-restricted (upload-config.ts). Prepare Learning and current active AI must be named separately from retired tools.
  • Rewards: Child Privacy's immediate-completion paragraph conflicts with its later suggestion that review decisions may control rewards. Migration 0130 and src/lib/adventure/activity-rewards.functions.ts/src/features/adventure/activity-reward-policy.ts support prospective defaults, individual overrides and separate evidence control; parent controls remain pending website publication.
  • Security: Privacy, Acceptable Use, Cookies and Trust retain single-session/one-session text; active admission supports two physical devices with explicit third-device replacement (src/lib/sessions/sessions.server.ts, migration 0127). Child Mode exits require PIN; hypothetical child communication switches are not current messaging features.
  • Deletion: src/lib/account/account.functions.ts cancels billing first, schedules 30 days and clears deletion flags on restoration; restoration does not restart Stripe. Cleanup is file-first (deletion-cleanup.server.ts, deletion registry). Restore/purge race and completion timing are unresolved risks, so no exact-time deletion guarantee is proposed. Shared projects and trial-history exceptions need precise disclosure.
  • Retention: every returned retention_categories period remains “Requires legal review”. Privacy's “defined period” and Trust's complete schedule claims overstate this evidence. Contact storage is private (docs/contact-form.md) but its final retention needs a decision.
  • Export: no complete export control was found in Account; Trust promises “Download everything”. Reports/PDF downloads are not a full portability export. This review proposes request-based wording, not a new export feature.
  • State information: Trust says summaries are not AI-generated, but internal state research uses AI extraction (src/lib/state-hub/state-research.server.ts) with separate admin review fields. Do not guarantee universal editorial authorship or reviewed status without record-specific evidence.
  • Community: current legal disclaimers do not explain automatic non-care publication or care review. group-screening-rules.ts and group-moderation.functions.ts confirm the split. Supporting duplicate/count reads ignore some database errors, and care-relevant fields are absent from SCREENED_FIELDS; do not claim unconditional fail-closed screening or universal edit review.
  • Cookies/logging: clearing browser storage does not turn off server operational logging; categorical anonymous-logging claims require inventory validation.
  • AI data: relevant learner/context data can be attached by the platform, not only typed into a prompt (src/lib/prepare/prepare.functions.ts). No verified provider retention/training schedule was supplied. Spending controls are disabled, so proposed future budgets are not current entitlements.

5. Most important remaining risks and approval decisions

  1. Qualified AU/US legal review: assess the new educational disclaimer alongside consumer guarantees, unfair contract terms, liability cap, resupply limitation and indemnity. The disclaimer must not defeat reasonable paid-service expectations or mandatory rights.
  2. Children's privacy and AI processing: resolve COPPA applicability/consent, Australian privacy obligations, support-note sensitivity, subprocessors, overseas processing, provider retention/training and actual access/logging inventory. No professional approval or compliance finding is claimed.
  3. Retention/deletion/portability: approve a specific retention and backup schedule, distinguish anonymised from still-identifiable records, confirm a working access/export-request process, and separately address the restore/file-cleanup race. Do not substitute copy for operational fixes.
  4. Moderation and care: separately review care-change screening omissions and supporting-read failure handling; verify organiser obligations and ensure listing presentation never implies safety, registration or endorsement.
  5. Billing and copyright: review renewal notices, refund handling and regional tax obligations; confirm statutory copyright processes where applicable. A policy promise alone does not establish an implemented process.
  6. Policy activation: reconcile presentation-only corrections with stored accepted versions; approve final wording, versions/effective dates, material-change classification and notice/reacceptance together. Do not silently activate this draft under existing version numbers.

Verification limits: no automated browser tests, paid AI/search/payment calls, customer-record changes or policy-store writes. This is an evidence-based content review, not legal advice or launch certification. The draft is visible separately in Preview; operative policy bodies and acceptance workflows are unchanged.

Loading…