Privacy Policy

This distinction decides who you should contact about a given piece of information, so it comes first.

• For our own customers and site visitors, we decide why and how information is used. That covers your account, your billing details, and how you use the product.
• For the data our customers put into the product, such as their lead lists, the mail synced from their mailboxes, and their call recordings, we act on that customer's instructions. They decide who is contacted and why. If you received an email or a call from a business using Scheduler Zero and you want it to stop, the fastest route is to reply to that business or use the unsubscribe link in the message. You can also write to us at legal@fundlevel.co and we will pass your request to them.

Account and workspace information

Your name, email address, profile picture, workspace and parent organisation details, memberships, roles, invitations, and account security information. WorkOS handles our primary sign-in experience, including enabled social sign-in or single sign-on. We also process session identifiers, API key records, and authentication events.

Billing information

Your plan, subscription status, invoices, and usage counts. Card details are entered directly with Stripe and we never see or store the full card number.

Connected mailboxes

When you connect a mailbox we store the access tokens or the IMAP and SMTP credentials needed to send and read on your behalf. These are encrypted at rest. We sync message content, headers, threads, and folder labels so the unified inbox, reply detection, and bounce handling work. Attachments and message bodies may be fetched as needed, and historical loading can import older mail beyond the initial sync. Disconnecting a mailbox stops its connection; it does not by itself erase messages already stored in Scheduler Zero or at your provider.

Google API data

Scheduler Zero's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google mailbox data and the mailbox address only to provide the mailbox features you enable. We do not sell it, use it for advertising, or use it to train, develop, or improve generalised AI models. The same restrictions apply to transfers of Google API data to providers that help deliver these features. Human access is limited to the circumstances allowed by that policy, such as your affirmative agreement to view specific data for support, security investigations, or legal requirements. You can revoke access in your Google account permissions and contact us to request deletion of previously imported data.

Contacts, workspace content, and integrations

Names, email addresses, phone numbers, employers, job titles, and any custom fields you choose to add, along with lead notes, tasks, assignments, campaign notes, templates, suppression records, workflow instructions, and activity history. Information may come from you, workspace members, connected CRM systems, booking services, or verification providers. Email and phone checks send the address or number to the configured providers and return deliverability, carrier, line type, and other available validation results. A cascade may consult more than one provider for a single check.

Sending and engagement data

Which messages were sent from which inbox and when, plus opens recorded through a tracking pixel, clicks recorded through rewritten links, replies, bounces, and unsubscribes. Open and click tracking is controlled by campaign settings and, for clicks, individual link choices. Requests to tracking endpoints include technical information such as IP address and user agent; we use derived identifiers and bot signals to measure engagement. Tracking can be affected by mail proxies, scanners, and privacy features and does not prove a person read a message.

Dialer data

Caller and recipient numbers, forwarding destinations, call times, duration, outcomes, notes, voicemail assets, and recording-consent records. Enabled recording and post-call features process audio, transcripts, summaries, and suggested dispositions through Twilio, Deepgram, and our AI providers.

Authorised users can share recordings using a public link or a link restricted to workspace members. Anyone who obtains a public link can access its content until it is revoked. Hiding displayed names or changing the prospect voice does not remove identifying information spoken in the audio or present in a transcript. Voice masking is not guaranteed anonymisation. Live voice effects change the representative's browser playback; original recordings remain available to authorised users, and masked sharing creates a separate copy.

Purchases, bookings, and support

Domain names, registration and billing contact details, DNS settings, mailbox orders, sender profiles, and provisioning status. Automated mailbox setup may process temporary passwords and verification codes in hosted browser sessions. Booking integrations supply attendee details, event times, status, and cancellation or rescheduling data. We also receive demo requests, survey answers, support messages, and files or screenshots you send us.

Product, site, and video analytics

Pages viewed, features used, browser and device details, IP-derived approximate location, error and diagnostic logs, and video playback events such as progress and completion. PostHog session replay can capture on-screen content, interactions, and non-password form input; it is not a recording of your camera or microphone. Product analytics may be linked to your user identity and workspace. Website measurement choices are described in section 10.

Mobile applications

The mobile app processes account and workspace data for the features you use, along with app version, lifecycle events, screen activity, and crash diagnostics. It contacts Expo for application updates. Calling uses microphone and audio-device permissions; you can manage those permissions in your device settings, though disabling them can prevent calls. Call audio and recordings are handled as described above.

How we identify website visitors

When you allow advertising tracking on this site, we use a tracking script, cookies and similar technologies to collect information about your visit, including your IP address, the pages you view, the site you arrived from, and your approximate location. We pass that information to our visitor-identification provider, which compares it against its own database of business contact records.

Where it finds a match we receive personal information about you that you did not give us directly: usually your name, work email address, employer, job title and professional profile links. We use it to contact you about our products and services, and we store it in our sales and marketing systems.

Under some privacy laws this counts as a "sale" or "sharing" of your personal information, or as targeted advertising. You can change these choices at any time:

• Reject marketing tracking in the consent banner or reopen the site's privacy settings and turn off marketing cookies. This stops future consent-based visitor identification in that browser.
• Ask us to access, correct or delete what we hold about you: legal@fundlevel.co

PIPEDA is built on consent. We rely on your express consent where you give it, such as connecting a mailbox or enabling call recording, and on implied consent for the ordinary operation of a service you have signed up for. We use personal information to:

• provide and operate the features you have switched on;
• protect deliverability and the platform, which includes monitoring bounce rates, spam complaints, and abuse signals;
• bill you and keep the financial records the law requires;
• provide support and respond to what you ask us;
• improve the product, using aggregated or de-identified information wherever that is enough;
• send you service messages, and marketing messages where CASL permits it, which you can stop at any time;
• meet legal obligations and enforce our terms.

We do not sell customer workspace content, including uploaded lead lists and connected mailbox content, or use it for advertising. The separate website advertising and visitor-identification disclosures in sections 2 and 10 describe exchanges that may count as a sale or sharing under some privacy laws.

Where the EU or UK GDPR applies to information we control, our bases are performance of our contract with you for account and service delivery; legal obligations for required records and disclosures; consent for optional website measurement and advertising; and legitimate interests in administering business relationships, supporting customers, and protecting and improving the service, subject to your rights. Our customers determine the lawful basis for their own outreach and the personal information they ask us to process.

AI features may send message text, conversation history, lead or CRM context, workflow instructions, and call transcripts to model providers for classification, summaries, and follow-up drafts. Transcription sends recorded audio to Deepgram. Results and workflow activity may be stored with the relevant conversation or call. We do not train our own AI models on your content. Provider processing is governed by the applicable service terms and account settings; contact us for details about the providers used for your feature.

A workspace can configure AI follow-ups for approval or automatic sending and permit tools to retrieve web content, access CRM data, or contact external MCP servers. Tool requests and results may disclose relevant context to those destinations. Review the connected services and permissions before enabling them. AI results can be inaccurate and should not be treated as verified facts.

The following providers and recipients support the features described here. Which ones receive your information depends on your use, workspace configuration, and consent choices. Some process information on our behalf; others, including your connected services, registrars, payment services, and advertising partners, also have their own terms and privacy responsibilities. This is a feature-based provider list, not a promise that each provider receives every category of data.

Sharing you or your workspace authorise

Workspace members and administrators can access information according to their permissions. Authorised parent-organisation members may view information across linked workspaces. API keys, the public API, MCP clients, webhooks, Zapier, Make, and other connected tools can read data or perform actions within their permissions. Customer-configured workflow destinations, including Conductor and other external agents, receive the data sent to them. Revoking access stops future authorised requests but does not recall copies already exported.

Warmup participants

Enabling warmup joins a shared pool of warmup-enabled mailboxes, including mailboxes operated by other customers. Participants and their email providers receive real warmup messages and can see the sender address, display name, domain, headers, and warmup content. The service may send replies and organise or mark warmup mail as read or not spam. Turning warmup off stops new participation but does not recall messages already delivered.

Customer domains and mirrored sites

If a customer enables website proxying, visitor requests and responses pass through our edge service to the configured origin. This can include URLs, headers, cookies, and submitted form content. The site operator is responsible for its own privacy notice and tracking choices. Domain registration also involves disclosures to registrars, registries, and other recipients required by registration rules; public registration records depend on the domain and available privacy protections.

We may also disclose information where the law requires it, to establish or defend a legal claim, or as part of a merger or sale of our business, in which case we will tell you before your information becomes subject to a different policy.

Our infrastructure and most of our providers operate in the United States and other countries, so your information is stored and processed outside Canada. We are required to tell you what that means: while information is in another country it is subject to that country's laws, and the courts, law enforcement agencies, and national security authorities of that country may be able to obtain access to it. We use contractual protections with our providers, but they cannot override those laws. If you would like more detail about our practices for handling information across borders, write to legal@fundlevel.co.

We retain information according to its purpose: operating your workspace, completing purchases, providing support, preventing abuse, honouring opt-outs, resolving disputes, and meeting legal recordkeeping duties. Cancelling a subscription or disconnecting an integration is not a request to delete the workspace or all previously imported data. Workspace deletion can remove application records immediately, so arrange any export first. Purchased domains and mailbox services must be transferred or offboarded before workspace deletion can proceed.

To request deletion of account information, synced mail, recordings, transcripts, or other stored assets, contact legal@fundlevel.co. Deletion from the application does not itself erase copies held in recipient mailboxes, customer exports, or independent connected services. Backup, security, and legally required records may remain subject to their retention requirements. We will explain any applicable exceptions when handling your request.

Our scheduled cleanup removes expired advertising attribution data, removes detailed video viewing records after 90 days without a new viewing event, and strips encrypted advertising match data from conversion records after 90 days or earlier attribution expiry. We retain conversion records, which can still include business-event identifiers, and consent records for audit, security, and reporting purposes. The 90-day rule is for our marketing attribution and viewing records, not a deletion schedule for every provider's systems.

We protect information with encryption in transit and at rest, separately encrypted mailbox credentials, role based access controls within a workspace, workspace-scoped permissions, and access controls for administrative operations. No system is perfectly secure, so we do not promise absolute security.

If a breach creates a real risk of significant harm, we will report it to the Office of the Privacy Commissioner of Canada and notify the people affected as soon as feasible, and we keep records of security breaches as PIPEDA requires. You can report a suspected vulnerability to legal@fundlevel.co.

Under PIPEDA you may:

• ask what personal information we hold about you and how it has been used and disclosed;
• ask us to correct information that is wrong or incomplete;
• withdraw your consent, subject to legal and contractual limits, understanding that this may mean we can no longer provide the service;
• ask us to delete information we no longer need;
• complain about how we have handled your information.

Write to legal@fundlevel.co. We respond to PIPEDA access requests within thirty days unless a lawful extension applies, in which case we will explain the extension. Other requests are handled within the period required by applicable law. We may need to verify your identity first. If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada at priv.gc.ca.

If you are in the European Economic Area or the United Kingdom, you also have the rights given by the General Data Protection Regulation, including access, rectification, erasure, restriction, portability, and objection, subject to the conditions in that law. You can withdraw consent without affecting processing already lawfully carried out and complain to your local data protection authority. The same address reaches us.

Where applicable US state privacy laws give you rights, you may ask for access, correction, deletion, or a portable copy, and opt out of sale, sharing, or targeted advertising. Use the website privacy settings to reject marketing tracking, or email legal@fundlevel.co for requests about information already collected or requests submitted by an authorised agent. You may appeal a denied request by replying to our decision. We do not discriminate against you for exercising applicable privacy rights.

Necessary cookies and browser storage support sign-in, security, preferences, and consent records. The signed-in application also uses PostHog for product analytics, support, and diagnostics as described above; the website consent banner is not a product-wide analytics control. You can contact us about product privacy choices.

On our marketing site and sales funnels, optional analytics and advertising require an affirmative choice in the consent controls. Measurement includes analytics, session replay, video engagement, and affiliate measurement. Marketing includes advertising attribution and visitor identification. Google Tag Manager may load with denied consent defaults before a choice under Google's advanced Consent Mode; this can involve limited cookieless measurement signals. A denied choice prevents our consent-gated analytics and advertising delivery.

Reopen the site's privacy settings control, or the funnel's cookie preferences, to change your choice. Choices are browser-specific; clearing cookies or using another browser may require a new choice. Withdrawal affects future optional tracking and does not automatically delete previously collected information. Our preference cookie lasts up to one year, and we store a pseudonymous server-side record of the choice, notice version, and time. Blocking necessary cookies may prevent sign-in. Booking embeds and video delivery also connect to their providers to deliver content you request.

When you allow advertising tracking, we use Google Ads measurement and the Meta Pixel and Meta Conversions API to measure page visits and conversions. Meta may receive browser identifiers, IP address, browser information, and hashed contact identifiers for matching and attribution. Browser and server copies of the same conversion use an event identifier so Meta can deduplicate them.

Separately, emails sent through the platform by our customers may contain an open tracking pixel and rewritten links, which is a feature those customers control.

When an affiliate link is used, Dub and Scheduler Zero record link and referral identifiers to measure the visit and prevent fraud. Referral context may remain in the browser for 90 days, but is eligible for commission attribution only for 30 days. New affiliate analytics capture requires an explicit analytics grant. Rejecting or withdrawing it prevents new capture.

The service is a business tool and is not intended for anyone under 18. We do not knowingly collect information from children. If you believe a child has given us information, contact legal@fundlevel.co and we will delete it.

We may update this policy. If a change is significant we will tell you by email or in the product before it takes effect. The date at the top of this page shows when it was last changed.

Fundlevel Digital Limited
86 Ringwood Drive, Unit 212, Whitchurch-Stouffville, Ontario, Canada, L4A 1C3
legal@fundlevel.co