Privacy policy

Tullia is operated by Jacob Perks, trading as Thunkle, a sole proprietorship in Ottawa, Ontario, Canada. In this policy, “we” and “us” refer to that business. Contact jacob@thunkle.ai with questions or privacy requests.

This policy covers our website and application, account administration, and the information processed through Tullia. For our own account and service operations, we are responsible for deciding how information is used. When a business connects its CRM or runs a campaign, that business decides the purposes of its customer-data processing; Tullia processes that data to provide the requested service. Its own privacy notice also applies.

Account and workspace information: email addresses, authentication identifiers, workspace names, membership roles, invitations, and settings. Optional Google sign-in provides your Google account identifier, email, and basic profile information such as name and picture through our authentication provider.

Materials you provide: campaign briefs, chat messages, brand guidelines, logos and other uploaded files, product information, website addresses and retrieved website content, generated drafts, edits, approvals, and campaign configurations.

Connected customer data: when you authorize an integration, we may receive CRM contact details (including email and phone numbers), company and deal records, CRM properties, lists, lifecycle stages, form activity, consent and opt-out records, and related identifiers. The data available depends on the connected account and permissions.

Delivery and activity data: campaign enrollment, scheduled steps, send status, delivery failures, replies, unsubscribes, and engagement events such as opens, clicks, page views, or in-app impressions and dismissals, where the relevant channel or customer-installed integration supplies them.

Operational information: timestamps, request and error information, audit trails, job status, rate-limit identifiers, and ordinary hosting logs that may contain IP addresses, browser information, and requested URLs. We also receive information you include in support correspondence. If you purchase a paid service, we retain billing and subscription records; a payment processor handles payment credentials.

We use information to sign you in, administer workspaces, synchronize authorized integrations, prepare and edit campaign content, execute approved journeys, record consent, report results, provide support, and maintain the security and reliability of the service. We also use necessary records to investigate abuse, resolve disputes, comply with legal obligations, and administer any agreed paid service.

We do not sell personal information or use it for third-party behavioral advertising. Account creation is not permission to send you unrelated promotional email. Where marketing consent is required, it must be obtained separately; essential account, security, and service messages may still be sent.

Where applicable law requires a legal basis, processing depends on the activity: providing the service you request, consent, legal obligations, or legitimate interests in operating and protecting the service. Customers are responsible for establishing the appropriate authority for the contact data and campaigns they submit.

Google sign-in is optional. We request only OpenID, email, and basic profile permissions to authenticate and identify your Tullia account. This connection does not give Tullia access to your Gmail messages, Google Drive files, Calendar, or Google contacts, and does not authorize sending email from your Gmail account.

Supabase processes the sign-in exchange and session. We use Google sign-in information for authentication and account administration, not advertising. Tullia’s use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements.

You can remove the connection in your Google Account’s third-party connections settings. Revoking Google access does not itself erase existing Tullia records; contact us if you also want your account or data deleted.

AI features use Anthropic’s API to process prompts and generate or evaluate content. Requests can contain your brief, chat instructions, brand and product context, relevant website content, campaign details, and previous drafts. Personal information you include in those materials may therefore be sent to the AI provider. Do not submit secrets, payment-card details, or sensitive personal information that is unnecessary for the task.

AI processing is governed by the provider’s applicable commercial terms and data practices. We do not operate a general-purpose model-training service or offer customer content for sale as training data. We do not promise zero retention by an external provider. Review AI output before using it.

Connecting a channel authorizes the data transfers needed for that connection. For example, HubSpot synchronization imports CRM records, and an enabled messaging provider receives recipient and message information to deliver an approved campaign. Disconnecting a provider does not automatically delete data already synchronized into Tullia or held by that provider.

Our core infrastructure uses Supabase for authentication, database, and file storage; Render for the application and background workers; Google for optional sign-in; and Anthropic for AI features. Resend provides transactional account email when configured. Stripe processes payments when you choose an enabled paid offer.

Customer-authorized channels may include HubSpot, Twilio, and OneSignal. We share the information necessary for the enabled feature, not every workspace record with every provider. Authorized workspace members can access information according to their permissions. Support access may be necessary to resolve a request, operate the service, or investigate a security issue.

We may disclose information if legally required, to protect people and the service, or during a business transfer with appropriate safeguards. Providers may process or store information outside Canada, including in the United States, where other laws and lawful government-access requirements may apply.

The application uses essential authentication cookies and a workspace-selection cookie. Browser storage may support an active workflow. Blocking essential storage can prevent sign-in or disrupt the application.

If a customer installs Tullia’s in-app SDK, it stores a scoped identity token in session storage and sends message interactions. On identified campaign pages, it can report the page URL and campaign enrollment identifier. Connected delivery providers may also report message engagement. Customers must provide the notices, choices, and consent required for their deployment; this policy is not a consent mechanism for their website.

The Tullia marketing website does not currently install third-party advertising trackers. We will update this policy and obtain any required consent before introducing materially different optional tracking.

Account and workspace records are retained while needed to provide the service and for legitimate operational or legal purposes. Retention depends on the type of record, customer instructions, support needs, security investigations, and applicable obligations. Deleting a draft or disconnecting an integration does not by itself delete an entire account, all audit records, or provider backups.

Request deletion at jacob@thunkle.ai. After verifying your identity and authority, we will delete or de-identify information no longer needed, subject to applicable legal exceptions and backup-expiry processes. We may retain limited accounting, consent, suppression, security, or dispute records where justified or required. We will explain applicable retention limits when responding. There is no promise that every record or backup disappears immediately.

Contact jacob@thunkle.ai to request access, correction, export, or deletion of personal information, or to withdraw consent. Depending on your jurisdiction, you may also have rights to object, restrict processing, or complain to a privacy regulator. We may need to verify identity and authority before acting and will respond within the period required by applicable law.

If your information came from a business using Tullia, contact that business first so it can address the request across its systems. We can help route a request and assist the customer where appropriate. Workspace administrators control their organization’s access; removing a member does not necessarily remove that person’s past contributions.

You may contact the Office of the Privacy Commissioner of Canada or another regulator with jurisdiction. Withdrawing consent or deleting essential account information can make some features unavailable.

We use access controls, workspace scoping, encrypted network connections, and restricted credentials to help protect information. No system is completely secure. Report a suspected security issue to jacob@thunkle.ai; we will assess incidents and provide notifications when required by law.

Tullia is a business service intended for adults aged 18 and over. It is not directed to children. Customers must not use it to collect children’s information or submit unnecessary sensitive personal data.

We update this policy when our practices change. The date at the top identifies this version. We will provide additional notice of material changes and obtain fresh consent where required; a policy update does not itself authorize an incompatible new use of your information.