Privacy Policy
Last updated: November 15, 2026
This Privacy Policy explains how Mark Davenport, d/b/a iCal Merge (“we”, “us”, “our”), the operator of iCal Merge (the “Service”, available at icalmerge.com), collects, uses, and protects your information. We are based in the United States and serve users worldwide.
Plain-language summary (not a substitute for the full text): We store the account info needed to log you in, the calendars you create, and the feed URLs you add. We fetch those feeds on your behalf and combine them into a single calendar feed. We do not sell your data. Merged calendar feeds are served at public URLs — anyone who has the URL can read that calendar. If you organize a carpool with Car Pool, we also store what you enter about the other families (names, emails, addresses, the kids' first names) and show the schedule, names and addresses to the households in that carpool; a household can remove its own details or leave at any time.
1. Who is responsible for your data
The data controller is Mark Davenport, d/b/a iCal Merge, located in Kansas, United States. Contact: [email protected].
2. Information we collect
Account information. Authentication is handled by our identity provider, Auth0 (Okta). When you sign in we receive and store a unique user identifier and your email address. We do not store your password.
Calendar configuration you provide. For each calendar you create we store: the calendar name/title, a generated calendar identifier, the source feed URLs you add, and the display name you give each source.
Carpool schedules (Car Pool). If you organize a carpool, we store what you enter to run it: the carpool's name, school times and timezone; optionally the school's address and a link to the school's public calendar; each driving household's name, up to two email addresses and, optionally, a home address; each rider's name and, optionally, a pickup address; the schedule itself (who drives which ride, who rides, days off, days a driver cannot drive); and a short log of recent changes. Much of this is about people other than you. Section 6 explains who sees it and the choices those people have.
Content fetched on your behalf. To produce a merged feed, we request the contents of the source URLs you configure and combine their events. We may cache the merged result for a limited period to improve reliability and performance. We do not use the contents of your calendar events for any purpose other than producing your merged feed. If you enable double-booking alerts for a calendar, we additionally compare the start/end times of events across that calendar's sources to detect overlaps, and email you a summary of any we find.
Usage and access data. We record limited access metadata for each merged feed (for example, an access count and last-access timestamp) and standard server logs (IP address, user agent, timestamps) for security and operations.
Product analytics. We collect first-party usage analytics to understand how the Service is used and to improve it: which pages are visited on our site, and product actions in your account (for example, creating a calendar, adding a source, or reaching a plan limit). This is done without cookies and, apart from the per-tab arrival note described in section 8, without browser storage — an anonymous visitor is not recognized across visits. If you sign in, analytics events are associated with your account identifier, along with the page that referred you to us when you signed up. On a carpool household's personal link page (section 6), which has no sign-in, usage events (for example, that the page was opened or a ride was taken) are recorded under an identifier derived from that link, so they are counted per household across visits; the identifier is not a cookie, is not the link itself, and carries no name, email or address. We process this data in PostHog (a US analytics provider) via our own domain; we do not track you across other websites, and this data is never sold or used for advertising.
Payment information. Payments are processed by our Merchant of Record, Paddle, who acts as the seller of record. We do not receive or store your full payment card details. We receive subscription status (e.g., active, cancelled, past due) and limited billing metadata needed to provision your plan.
3. How we use your information
- To operate the Service: authenticate you, store your calendars, fetch sources, and serve merged feeds.
- To provision and manage your subscription and plan limits.
- To maintain security, prevent abuse, and debug problems.
- To communicate with you about the Service (service notices; double-booking alert emails for calendars where you turn them on; and, only if you opt in, product updates).
- To run a carpool's schedule and tell its households about it: a note when an organizer adds a household's email, notices when one of its rides changes, and the coming week's schedule.
We rely on the following legal bases (for users in the EEA/UK under GDPR): performance of a contract (operating the Service you signed up for), legitimate interests (security, abuse prevention, service improvement, and running a carpool for the households an organizer has added to it), and consent (optional marketing communications).
4. Public nature of merged feeds
A merged calendar feed is served at a URL with the calendar's identifier so that calendar applications can subscribe to it without authenticating. Anyone who knows or obtains that URL can read the contents of that merged feed. Treat the feed URL as a secret. Do not include sensitive information in calendars you intend to keep private. We are not responsible for access by anyone who obtains a feed URL.
5. Third-party feeds
You are responsible for ensuring you have the right to access and redistribute the source feeds you add. We fetch those feeds as your agent. We are not the author of, and do not control, the content of third-party feeds.
6. Car Pool: information about other people
Car Pool lets one person (the “organizer”) schedule a carpool for several families. The organizer has an account. The other households do not need one: each gets a personal link.
Who provides the information. The organizer enters the households, their email addresses, any addresses, and the riders' names, and is responsible for having each family's agreement to do so. Information about a child is entered by a parent or the organizer, never collected from the child. A first name is enough, and addresses are optional.
Who can see it. The organizer, and anyone the organizer adds as a co-organizer, sees everything in the carpool. Each household's personal link shows that household the schedule, the names of the driving households and riders, the riders' pickup addresses, and the home address of the household driving a ride where one was entered. Email addresses are shown to organizers only. The carpool's shared calendar feed contains the schedule and names but no addresses; a household's personal calendar feed also contains the stops for its rides. Links and feed addresses work without a login, so anyone who has one can see what it shows, and a household's link also lets its holder take or give back rides as that household. Keep them private.
Email to households. When an organizer adds an email address for a household, we send that address one message saying who added it and to which carpool. After that the address receives notices when one of the household's rides changes and, if the organizer has it on, the coming week's schedule. If someone asks on a household's link page to be sent its link again, we email the link to that address, and only if it is already on a carpool. Every message has an unsubscribe link that stops all of them.
A household's choices. From its personal link a household can change or remove its email addresses, remove its home address, and leave the carpool, which deletes its addresses and emails and takes it off the schedule (its name can remain in the log of past changes until those entries age out). A household can also ask the organizer, or write to us at [email protected]; we may need to involve the organizer to act on a request.
Addresses and maps. On plans that include drive-time estimates, the addresses in a carpool are sent to Mapbox to locate them, estimate drive times and draw map previews, and we store the resulting map coordinates with the address. On other plans addresses are stored as typed and are not sent to Mapbox.
How we use it. To run that carpool: to build its schedule, calendars and emails. We also count how the feature is used, as described under “Product analytics” in section 2; names, emails and addresses are not part of that. We do not sell any of it or use it for advertising.
How long we keep it. Until the organizer or the household removes it, or the carpool or the organizer's account is deleted, which deletes everything in the carpool. The log of changes keeps only its most recent entries.
7. Sharing and disclosure
We do not sell your personal information. We share data only with service providers who help us run the Service, under contract:
- Auth0 (Okta) — authentication and login.
- Paddle — payment processing and tax (Merchant of Record).
- Cloudflare — DNS, network proxy/CDN, encrypted off-site backup storage (R2), and inbound email routing for our support address.
- Resend — outbound email delivery (e.g., alert and service emails).
- PostHog — first-party, cookieless product analytics (see “Product analytics” above).
- Mapbox — address lookup, drive-time estimates and map previews for carpools on plans that include them (see section 6).
The Service itself runs on infrastructure we operate directly (it is not hosted by a third-party application host). We may also disclose information if required by law, to protect our rights, or in connection with a merger or acquisition.
8. Cookies and local storage
We use only the storage strictly necessary to run the Service. Our login provider (Auth0) stores authentication tokens in your browser's local storage so you stay signed in, and we store your light/dark theme preference locally. Our product analytics is deliberately cookieless: it sets no cookies and writes nothing to your browser's storage, so an anonymous visitor cannot be recognized across visits (a carpool household's personal link is counted per link, as section 2 describes; that uses nothing stored in the browser). The one exception is a per-tab note of the page that referred you to us and the page you arrived on; it lives in session storage until the tab closes, is attached to your account only if you sign up in that tab, and is never used to recognize you on a later visit. We do not use advertising cookies, and we do not track you across other websites — so there is no behavioral-advertising activity to opt out of.
9. Data retention
We retain your account and calendar configuration for as long as your account is active. When you delete a calendar, its sources are deleted with it. When you delete your account, we delete your calendars and configuration and remove your personal data within 30 days, except where we must retain limited records for legal, tax, or security reasons. Cached feed content expires automatically. Deleting a carpool, or the account that owns it, deletes its households, riders and schedule (see section 6).
10. Your rights
Depending on your location (including under GDPR and the CCPA/CPRA), you may have the right to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise these rights, contact [email protected]. You can delete your calendars at any time from your account, and request full account deletion by emailing [email protected]. EEA/UK users may lodge a complaint with their local data protection authority.
California residents (CCPA/CPRA). We do not sell your personal information and do not share it for cross-context behavioral advertising. You have the right to know what personal information we collect, to request its deletion or correction, and not to be discriminated against for exercising these rights. To make a request, contact [email protected].
11. International transfers
We are based in the United States and our providers may process data in the U.S. and elsewhere. Where required, we rely on appropriate safeguards (such as Standard Contractual Clauses) for transfers out of the EEA/UK.
12. Security
We use reasonable technical and organizational measures (encrypted transport, access controls, managed authentication) to protect your data. No method of transmission or storage is completely secure.
13. Children
The Service is for adults. It is not directed to children under 16, children may not create accounts, and we do not knowingly collect personal data from children. Car Pool schedules rides for children, so an organizer or parent may enter a child's first name and a pickup address as described in section 6; that information comes from the adult, is used only to run the carpool, and can be removed by the organizer at any time. If you believe a child has given us personal data directly, contact us and we will delete it.
14. Changes
We may update this policy. Material changes will be posted here with a new “Last updated” date and, where appropriate, notified to you.
15. Contact
Mark Davenport, d/b/a iCal Merge — [email protected]
See also our Terms of Service.