Privacy Policy

Modyl is built by Carcinize Corp. We take your privacy seriously and want to be upfront about what we collect, why, and how you can control it.

What we collect

We collect the minimum data needed to operate the site and communicate with you:

• Optional usage analytics: fixed, allowlisted interaction events collected through PostHog after you accept analytics. We do not send page URLs, query strings, referrers, hostnames, form values, or session recordings to PostHog, and those events carry no per-visitor identifier. This helps us understand aggregate use without collecting submitted content.
• Communication data: if you email us, use the chat messenger, or request access, we retain your communication. An access request includes the email address and decision context you choose to submit, together with the time and version of your consent. Access requests are stored in Cloudflare D1 and the contact is synchronized to our self-hosted Twenty CRM for review.
• How you found us: when you submit an access request, we store alongside it which of our own pages you first arrived on, which page you submitted from, the name of the website that linked you to us if there was one, and any campaign labels (such as utm_source) that were on the link you followed. We keep this so we can tell which of our pages are actually useful to people. It is stored whether or not you accepted optional analytics, because a count that included only the people who accept analytics would be a misleading one.
  What this deliberately is not: we store the name of the referring website, never the full address of the page you came from, so a search you typed stays out of our records. We keep the name of one of our own pages only when it matches the shape of an ordinary page address on this site; anything else is recorded as/other instead. This record lives in your browser tab for the length of your visit and is sent only with the access request you deliberately submit. It is not a cookie, we do not share it, it sets no identifier that would recognise you on a later visit or on any other website, and it is deleted with the rest of your access request.
• Chat messages: whatever you type into the chat messenger, plus the technical metadata any web service sees when your browser connects to it, such as IP address, browser and device type, and the page you opened chat from. If you give us your email address or name inside a chat so we can reply, we keep that too. We do not pass your identity to the chat provider ourselves. The only thing we send it about you is whether you opened chat from the support page or from elsewhere on the site, so the conversation starts in the right place. Everything else it holds about you is what you chose to type.

How we use it

• Improving the site based on aggregate usage patterns.
• Understanding which of our pages and links bring people who request access, so we can write fewer and better pages.
• Responding to your questions, support requests, or access requests.

Third-party services

We use a small number of trusted third-party services to operate:

• PostHog: consented, fixed-event analytics.
• Intercom: the chat messenger and the support conversations held in it. A chat control is available on every page of this site. Intercom loads its own script from its servers and sets its own cookies, but only once you open the chat. If you never open it, no Intercom script runs and no Intercom cookie is set. Intercom processes chat data on our behalf as our processor and service provider, under its own privacy policy.
• Cloudflare: hosting and CDN.
• Twenty: our self-hosted access-request CRM.

We do not sell your data to anyone. These services process data only as needed to provide their specific function.

Cookies

We use a small number of cookies:

• Analytics choice: we store whether you accepted or declined optional analytics so your choice persists. Analytics events use no persistent visitor identifier.
• Chat cookies: Intercom uses cookies and similar storage to keep a chat conversation attached to you across pages and visits, so a reply reaches you rather than a stranger. These are set only after you open the chat, never on page load.
• Hosting platform cookies: this site is served by our hosting platform, Ploy, which sets its own cookies on every page load, before and independently of any choice you make about our analytics. ploy_anon_id is a persistent pseudonymous visitor identifier that lasts up to a year;ploy_session identifies a single visit. The platform records the page you are on and the address you arrived from, and uses the visitor identifier to keep any content experiment showing you a consistent version of a page. We do not control these cookies, we do not use them to identify you, and declining our optional analytics does not prevent them. Our content delivery provider also sets a security cookie (__cf_bm) to distinguish people from automated traffic.

We do not use advertising cookies, and we do not sell or share anything about your visit with advertisers. The hosting platform cookies described above are set by the platform that runs this site, not by us, and they are the reason we describe them here rather than claiming this site sets none.

Data retention and deletion

We keep analytics and communication data for as long as needed to operate the site and respond to you. Chat conversations are held in Intercom, and we keep them there for the same reason we keep mail: so a later question can be answered against what was already said. We have not set a fixed automatic expiry on them, so assume a chat conversation persists until it is deleted on request. If you want your data deleted, including a chat conversation, email us at hello@modyl.to or ask in the chat itself, and we will remove it, from Intercom as well as from our own records, within 30 days.

Your rights

You can request access to, correction of, or deletion of your personal data at any time. For any privacy request, reach out to hello@modyl.to.

Changes to this policy

If we make significant changes, we will post a notice on the site. Minor wording updates will be reflected in the “Updated” date above.