Privacy Policy
Effective October 23, 2026.
About this policy
This Privacy Policy describes CheckyTask at https://checkytask.com. It does not certify compliance with any particular privacy law.
CheckyTask is currently operated by Anderson Loyalty LLC. Business mailing address: 9340 N 56th St #221, Tampa, FL 33617.
What CheckyTask does
CheckyTask lets creators make checklists, keep personal lists, and assign tasks to other people. Assigned-task recipients use a task code and a required separate passcode without creating an account. Personal lists have no recipient access. Creators can request photo proof, notes, and completion reports.
Information we collect
Creator accounts. Email address, optional display name, default timezone, and notification preferences. Passwords are handled by our authentication provider and are never stored in plain text.
Content you create. Checklists and personal lists, steps, templates, recurring schedules, groups and tags, private creator notes, task guidance, task addresses you choose to add, and reference photos.
Task activity. Task codes are stored as task identifiers. Passcodes are protected by cryptographic hashes; schedule-generated passcodes are also retained in service-restricted storage so the creator can reveal them later. We store step check-offs, before/after proof photos, issue reports, optional clock-in/clock-out records and completion reports (including PDFs).
Recipient information. Creators may supply recipient names, email addresses and notification contact details. Accountless recipients may submit photo evidence, response notes, issue descriptions and notification consent/contact information. Providing a phone number alone does not grant SMS consent. SMS sending is switched off.
AI requests. Drafts and rewrites send creator-supplied text. Completion summaries can send recipient names, checklist/step titles, submitted notes, issue descriptions and resolutions, timestamps, time-tracking details and photo-presence indicators. The application does not automatically attach photo bytes, dedicated guidance-address fields or private creator-note fields. Free text is not address-redacted and may contain personal information, including an address. Review what you submit.
Billing. Subscription plan, status and history, customer/payment identifiers, billing-period dates and payment-event metadata. Card and checkout billing-address details are processed by Stripe; CheckyTask does not collect or store full card numbers through its payment form. Paid subscriptions are available through live Stripe checkout.
Technical and notification data. Sign-in/security records, hashed recipient session tokens, failed-passcode counters, email addresses, phone/consent and opt-out records, delivery identifiers, attempts, statuses, errors and timestamps. Pending recipient notes/check-offs may be held in session-only, token-scoped browser storage while awaiting synchronization; synchronized responses become app records. Hosting, email and error-reporting services may process network/device request information and diagnostics, including request paths, messages or stacks. Provider access, redaction and retention have not been independently verified.
How we use information
To provide the service: creating and sharing tasks, verifying task codes and passcodes, storing photo evidence, generating PDF completion reports, sending email receipts and reminders you turn on, and managing subscriptions.
Notifications. Completion and issue emails follow task settings; personal-list reminders are optional. Recurring assignments with a recipient email can send a new-task email containing the task link, code and passcode. Operational schedule-limit or time-tracking-change alerts may be sent to the creator when applicable; they are distinct from recipient completion-email choices. SMS sending is switched off.
Service providers
The reviewed application has no advertising or data-sale integration. This is a description of the application, not a verified business-wide legal determination about sale or sharing. These services process information through the paths described below:
- Lovable Cloud and managed authentication email — accounts, authentication and verification/recovery messages, app records, private photos/PDFs, billing/notification metadata and operational diagnostics.
- Lovable AI Gateway and downstream AI service — the text and summary facts described above. The application requests an OpenAI-namespaced model; actual routing, subprocessors, retention, training use and processing locations have not been independently verified. A request setting disabling stored results is not a guarantee of zero provider retention.
- Resend — recipient/creator email addresses, task/reminder/issue information and completion PDF attachments, which can include guidance, addresses, reference and proof photos, notes, issues and time records. Authentication email uses a separate managed path.
- Stripe through Lovable's payment connection — customer email, user/billing identifiers and metadata, and checkout/payment/tax details for the selected environment. Test mode can involve real contact information. Live credentials and prices do not by themselves activate public paid checkout; the merchant's verified legal identity must match the operating business before activation.
- Twilio infrastructure — inactive SMS transport; no current outbound SMS sending. Phone/consent records can exist in Lovable Cloud. If later approved, phone numbers, message content and delivery identifiers would be processed for SMS.
- IONOS — customer support messages, sender/contact details, attachments and replies sent through support@checkytask.com.
- Google Maps and linked websites — clicking Get Directions sends the destination address in a Maps link; external sites also receive ordinary browser/request information when opened.
We have not independently verified each provider's internal data uses, training practices, subprocessors, processing countries or retention schedules. We therefore do not promise zero retention, no training, domestic-only processing or limitations on their independent uses. Information can be processed outside your state or country. These uncertainties require provider/contract review where applicable privacy law requires it.
Children's privacy and family checklists
Account holders must be at least 13 and confirm this when they first use their account; children under 13 must not create accounts. The confirmation and family commitment are recorded for all sign-in methods and returning accounts before the dashboard opens. Declarations are self-attestation, not verified age. Authentication itself does not establish age.
Parent-managed family checklists. An adult may create family profiles identified only by an optional nickname the parent chooses, with settings for task history and turning a profile off. We do not request a child's full name, email, phone number, birth date or photo. Family checklists, steps, check-offs and completion records are stored in the parent's account, are visible only to that parent, and are completed by the parent. A nickname may be shown on the parent's dashboard and in that parent's printouts or reports. Removing a profile removes the nickname record; the parent's checklists and completion records remain in the parent's account and can be included in a deletion request.
Assigned recipients. Assigned tasks may be used by recipients aged 13 or older. When opening a task or resuming an existing session, the recipient confirms they are 13 or older and the declaration is recorded with the recipient session. We do not verify age; the declaration is self-attested. Children under 13 must not open assigned tasks. Existing sessions are prompted without losing pending drafts.
Children under 13. Children must not access or submit assigned tasks. Family lists have no recipient access, including after profile removal. Family child-side notes, proof photos, issue/time records, SMS and automatic AI completion summaries are blocked; parent-entered nicknames, routine text and completion records can still concern children. Free-text AI tools are not a child-data detector: do not enter children's personal information. These workflow restrictions do not verify who holds ordinary assigned-task credentials. Direct child use requires a separately reviewed parental-consent framework; no COPPA compliance is claimed.
If you believe a child has submitted information through an assigned task, contact support@checkytask.com without sending additional sensitive evidence. We will review access and removal needs through the manual process below, subject to applicable law; no automated child-data removal system currently exists.
Task codes, passcodes, and photo privacy
Each assigned task requires a task code and separate passcode. Possession authorizes access; it does not verify a recipient's identity. Share credentials only with intended recipients. Photos are private, not publicly listed, and served through temporary signed links. Already-issued photo links can be forwarded and remain usable for up to one hour, including after cancellation.
Task addresses, contact details, shared guidance and reference photos are intentionally visible to authorized recipients and may appear in PDF/email reports; they are not private creator notes. Uploaded proof and issue photos also appear in authorized reports. Downloads, screenshots and emailed copies cannot be recalled.
Private creator notes are owner-protected and excluded from recipient views, checklist printouts, PDF reports, emails and the reviewed AI processing paths. Privileged service processing can access private records where required to operate the service.
The 30-day recipient access rule
Recipient application access ends at cancellation, any earlier task expiry, or 30 days after completion, whichever comes first. After expiry, the code and passcode no longer open the task. Recipient sessions last up to 12 hours before credentials must be entered again; session expiry is not a record purge.
This limits recipient access, not storage retention. Creator records and private files are not automatically deleted at that deadline. Independently emailed or downloaded PDF copies may remain readable after access ends and cannot be recalled by CheckyTask. Optional pre-completion checklist printouts are labeled “Printable Checklist — Not Proof of Completion”; printing does not submit or verify a task.
Data retention and deletion — actual behavior
This section describes what the system does today, so the final policy promises nothing it cannot implement.
Active and completed records. No inactivity-based or completed-task purge is implemented. Tasks, personal lists, templates, schedules, recipient submissions, notes, private photos/PDFs and saved AI text remain unless changed through a supported action or separately approved administrative process. Cancellation blocks task access but keeps records/files; deleting database rows alone does not remove stored files.
Account deletion requests. Settings accepts an identity-checked request with an optional reason and displays its status. A private owner review queue inventories dependencies and records review actions. Submission, review and preview do not erase or suspend accounts, pause schedules, cancel billing or revoke recipients. No permanent deletion executor or automated deadline is available. Any permanent erasure requires a separately authorized, coordinated manual administrative process covering tasks, personal lists, recipient records, templates, schedules, private notes, saved AI content, photos and reports. Deleting a sign-in account alone would not reliably erase those records or files. Cancel subscriptions and pause schedules separately; contact support to amend or withdraw a request.
Backups. Platform documentation describes daily database-only snapshots retained up to roughly 14 days, not a guaranteed CheckyTask retention policy. Storage photos/PDFs are excluded; point-in-time recovery is unavailable. This project's snapshot inventory and latest successful backup are not independently verified. Selective erasure from backups and a deletion deadline have not been established; restoring a snapshot can restore previously removed database data.
Logs, AI and billing. Email delivery histories, SMS contacts/consent/opt-outs, AI usage/reservations and app-side billing records have no routine retention purge. Unsaved AI results are not kept in a dedicated conversation table; saved text follows task/template retention. Stripe, Resend, managed authentication email, AI services and IONOS retain their own records under applicable terms; periods are unverified. Removing an app account does not remove provider invoices, payment records, delivered messages or attachments. Accounting, security, dispute, legal-hold, other-party and opt-out records require separate review of applicable retention duties; no fixed universal retention period has been established.
Your choices
You can edit or cancel tasks, manage templates/schedules, choose task email receipts and personal-list reminders, and set defaults for new-task completion/issue emails in Settings. You can request an email change, change your password, or submit and track an account-deletion review request in Settings.
Depending on applicable law, you may have rights to access, correct, obtain a copy of or request deletion of information, object to or restrict processing, withdraw consent where processing relies on it, or complain to a competent privacy authority. Contact support@checkytask.com to make a request, including if you are an accountless recipient. We may need to verify identity and authority without disclosing another person's records. The available Settings actions are not a complete automated privacy-rights system; requests require manual review and applicable legal exceptions. Nothing in this policy limits mandatory rights or establishes a verified GDPR, CCPA or other compliance certification.
Contact
Privacy questions: support@checkytask.com (active and monitored; sending and receiving verified by the owner). Business mailing address: 9340 N 56th St #221, Tampa, FL 33617.
Operator
CheckyTask is owned and operated by Anderson Loyalty LLC.