Skip to main content

Legal

Privacy Policy

How we collect, use, and protect the information you share with us. Effective August 8, 2026.

Who we are

Notionalize builds operations infrastructure — Notion systems, workflow automations, and custom AI — for scaling teams. This policy explains what we collect through this website and what we do with it. It applies to notionalize.com and does not cover third-party sites we link to.

What we collect

We collect information you choose to send us and limited technical data needed to operate specific site features:

  • AI Systems Fit Assessment — when you complete the assessment, we collect your name, work email, and your answers (your biggest challenge, role, team size, current stack, time sink, timeline, budget, optional company website, and how you heard about us).
  • ROI calculator — we collect your estimate inputs, workflow bottleneck, Notion experience, company type, name and work email, plus any optional role, company website, and discovery source you provide.
  • Newsletter — if you subscribe, we collect your email address.
  • Ask Juls chat — anything you type into the on-site chat.
  • Booking — if you book a call, the scheduling form (provided by Fillout) collects the details you enter to set up the meeting.
  • Basic technical data — the page you came from (referrer) and your browser's user-agent string, stored alongside a submission, plus consent-based aggregate analytics from Vercel Analytics and Google Analytics 4.
  • Approximate location — for calculator submissions, Vercel may provide country, region, and city labels derived from the request. We label this as approximate and do not store the raw IP address, coordinates, or postal address.
  • Private-offer timer — when you open a timed existing-client offer, our server uses the request IP address to create a one-way, secret-keyed identifier. We store only that identifier, the offer name, and its start and expiry times so refreshing or returning does not reset the timer. We do not store the raw IP address.

How we use it

  • To send your preliminary assessment, reply to your message, or schedule and prepare for your call.
  • To send the newsletter you asked for (you can unsubscribe at any time).
  • To understand which content and pages are useful, in aggregate.
  • To run our own operations — i.e. to follow up with you about working together.
  • To keep a private offer's deadline accurate when the same network address returns.

Lead research (enrichment)

When you submit the audit or a verified ROI-calculator request with a business email or company website, we may look up publicly available company information — from the public website and public web search results — to understand your context before we talk. This uses automated tools (Firecrawl for retrieval and a third-party language model for summarization). For calculator leads, we store only the company name, a short company summary, industry, approximate company size, public buying signals, source domain, and confidence—not scraped page bodies, private journey data, lead scores, or newly discovered personal contact details. With no company website, we do not research personal email domains such as Gmail or Outlook. Self-reported answers remain separate and take precedence over inferred context.

Who we share it with

We do not sell your information. We share it only with the service providers that run this site and our intake process, and only so they can perform that function:

  • Supabase — stores form submissions in a private, access-controlled database.
  • Vercel — hosts the site and provides aggregate analytics.
  • Google Analytics 4 — loads the Google tag in default-denied consent mode, may send cookieless consent pings, and measures aggregate site traffic after you accept analytics.
  • Fillout — powers the call-booking form.
  • Firecrawl and our language-model provider — used for the company research described above.
  • Telegram — we receive a notification when a new lead comes in.

Cookies and local storage

We aim to keep this site as low-tracking as possible. We do not set advertising or cross-site tracking cookies.

  • Essential storage — we use your browser's local storage to remember your theme (light/dark) and the layout of the on-site app. This stays on your device, is never sent to us, and is required for the site to work as you left it.
  • Analytics — the Google tag loads in default-denied consent mode so Google can receive cookieless consent pings without analytics or advertising storage. With your consent, Vercel Analytics and Google Analytics 4 measure page views and site usage in aggregate. You can change your choice at any time via "Cookie preferences" in the footer.
  • Visitor journey (with your consent) — to understand how people find and use the site, we keep a small first-party record in your browser's local storage: an anonymous ID, the pages you view, time spent, and how you arrived (e.g. a search engine, an AI assistant, or a referring site). This stays on your device and never reaches us unless you submit a form — in which case a snapshot is attached to that submission so we can see the path that led you to reach out. It stays off until you accept analytics, and you can decline or clear it at any time.
  • Embedded booking — if you open the call-booking form, Fillout (the provider) may set its own cookies inside that form to operate it. That only happens when you open the booking modal.

How long we keep it

We keep submissions for as long as we may reasonably need them to follow up or for our records, and we delete them when they are no longer needed. Private-offer timer records are automatically removed on later timer requests once they have been expired for 30 days. You can ask us to delete your data at any time (see below).

Your choices and rights

  • Unsubscribe from the newsletter using the link in any email.
  • Ask us what we hold about you, ask us to correct it, or ask us to delete it.
  • Decline to provide information — the forms are optional; you can also simply book a call instead.

Security

Form submissions are stored in a database with row-level access controls and are written only by our server, never exposed to the public. We use reputable providers and reasonable safeguards, though no method of transmission or storage is ever completely secure.

Changes to this policy

We may update this policy as our practices evolve. The effective date above reflects the latest version.

Contact

Questions, or want your data corrected or deleted? Email hello@notionalize.com and we'll take care of it.