ToDoddle

Privacy Policy

Draft · last updated October 21, 2026

Who operates ToDoddle

ToDoddle is operated by Krffl LLC ("ToDoddle," "we," "our," "us"), located at 2389 Main St. STE 100, Glastonbury, CT 06033. This policy covers the marketing site and the ToDoddle application together (the "Services").

Information we collect

  • Account and profile — name, email address, password (stored hashed) or passkey/TOTP credentials, profile image, workspace and project role, and the date and versions of the Terms and Privacy Policy you accepted at sign-up.
  • Project content you provide — tickets, comments, Context artifacts, notes, documents, file and video uploads, checklist items, and other work content your organization creates in ToDoddle.
  • Time and billing — time entries, client records (name, billing profile, rates, currency, tax settings), invoices, and payment records. Stripe processes payment instruments directly; ToDoddle does not store full card numbers.
  • Communications — support case messages, direct messages, and mentions.
  • Agent and integration data — Agent Connection identities, capability scopes, project grants, and MCP tool-call metadata (tool name, duration, outcome). Tool arguments and returned content are excluded from our logs by design.
  • Access-request data — name, company, and email submitted through the "Get access" request form (currently hosted by Tally.so) on the marketing site.
  • Technical and usage data — login sessions, security events (MFA/passkey enrollment, password changes), authentication IP address, bot-detection signals (Vercel BotID) on sign-up, sign-in, and password reset requests, and opt-in product analytics that respects Do Not Track and excludes customer content.
  • Marketing site analytics — if you accept the cookie banner, Google Analytics (GA4) collects pages viewed, general location, device type, and referral source. Nothing is collected if you decline or don't decide.

How we use information

To provide and secure the Service; authenticate accounts and enforce workspace/project permissions; enable collaboration (comments, mentions, notifications, reviews); process subscription billing and client invoicing; respond to support requests; send transactional and digest emails; improve the product using aggregated, opt-in, content-excluding analytics; enforce our Terms of Service; and comply with legal obligations.

Legal bases

Where GDPR or similar law applies: contract (providing the Service you signed up for), legitimate interests (security, fraud prevention, and non-content product analytics), consent (marketing-site analytics cookies and any marketing communications), and legal obligation (billing records, responding to lawful requests, breach notification).

Service providers and subprocessors

ProviderPurpose
VercelApplication hosting and compute
SupabaseDatabase and Realtime messaging
Bunny.netFile/video storage, streaming, and CDN
StripeSubscription billing and payment processing
PostmarkTransactional email delivery
Tally.soAccess-request form embedded on the marketing site
AxiomOperational logging and telemetry
PostHogIn-app product analytics (only after opt-in consent)
Google AnalyticsMarketing site usage analytics (only after cookie consent)

We are still completing formal data processing agreements and reviewing assurance reports for each of these providers (tracked internally in the SOC 2 readiness backlog). We will keep this list current as infrastructure changes.

AI agents and third-party integrations

ToDoddle is built around Agent Connections — scoped, revocable credentials that let an AI agent act on a user's behalf, strictly within the capability scopes and project grants that user has authorized. Every agent action is rechecked against the authorizing human's current access on every call; nothing is granted permanently or beyond what the human already has.

Agents can connect to ToDoddle in two ways today:

  • Local MCP — an agent (such as Claude Code or Codex) running in a developer's own environment, using an Agent Connection's client credentials.
  • Hosted MCP (currently in private alpha, limited to a small number of accounts) — a hosted connector that lets AI platforms such as OpenAI, Anthropic, or Google act on ToDoddle through delegated OAuth.

When a user authorizes a hosted connection to one of these AI platforms, project data returned by a tool call passes through that platform's own systems, subject to that platform's own terms and privacy practices. ToDoddle does not send project content to any AI provider except as a direct result of an authorized Agent Connection's tool call. Tool arguments, returned content, emails, tokens, and signed URLs are excluded from ToDoddle's own logs by design.

Cookies, analytics, and similar technology

This marketing site uses Google Analytics (GA4, measurement ID G-T3GLKMGFXV) to understand how visitors use the site. It is implemented consent-first: the tag is not loaded and no analytics cookie is set until a visitor actively accepts the cookie banner. Declining, or not deciding, means nothing is ever fetched from Google. Visitors can change their choice at any time via the "Cookie preferences" link in the site footer. IP addresses are anonymized, and Google Signals and ad personalization signals are explicitly disabled — this is analytics only, not advertising or remarketing.

The embedded "Get access" form is provided by Tally.so and may set its own cookies under Tally's own privacy policy. The ToDoddle application uses strictly necessary session cookies to keep you signed in. Product analytics inside the application are opt-in, respect Do Not Track, and never include customer content.

Storage, retention, and deletion

Projects use soft deletion with a recovery window before permanent removal. Issued invoices are immutable snapshots by design and are retained for accounting and tax purposes. A full, published retention schedule for other data categories is still being finalized. We delete or anonymize account and project data on request, subject to legal retention obligations we're required to meet (for example, issued financial records).

Security

We use scoped, role-based access control across workspaces and projects; hashed passwords and API-client secrets; passkey and TOTP support; short-lived signed URLs for private file access; and revocable, least-privilege Agent Connections. No system is perfectly secure, and we do not currently hold SOC 2 or other third-party security certification — a readiness review is underway internally, but this policy will not claim compliance we haven't earned.

International data transfers

If you access the Service from outside the country where our infrastructure operates, your information may be transferred internationally. Where required, we rely on appropriate transfer mechanisms such as standard contractual clauses.

Privacy rights and requests

Depending on your location, you may have rights to access, correct, delete, or export your personal data, and to object to or restrict certain processing. For data your organization stores as work content (tickets, comments, documents), your workspace administrator is generally the controller and the first point of contact; ToDoddle acts as a processor for that content and as controller for account and billing data. To exercise a privacy right, contact us using the details below.

Children's privacy

The Service is intended for business use by adults. We do not knowingly collect personal data from children under 13 (or the relevant minimum age in your jurisdiction).

Policy changes

We may update this policy as the product and its data practices evolve. Material changes will be announced in the application or by email, and the "last updated" date at the top of the public page will change accordingly.

Contact

Krffl LLC
2389 Main St. STE 100
Glastonbury, CT 06033
Email: support@krffl.com