Privacy Policy
Last updated: November 16, 2026
1. Who We Are
This Privacy Policy describes how Kure-Cal ("Kure-Cal", "we", "us", or "our") collects, uses, and shares information when you use our website, products, and services (collectively, the "Services"). If you have questions, use our contact form.
2. Information We Collect
- Account data: name, email address, authentication provider, profile preferences, time zone, and account identifiers. Password credentials are handled by our authentication provider.
- Usage data: device/browser type, IP address, pages viewed, features used, timestamps, referral URLs.
- Calendar and content: events you add or import, calendar connection credentials, community posts, comments, reports, images, categories/tags, and related metadata you choose to store in the app.
- Cookies and similar technologies: essential cookies to operate the Service, and analytics cookies and similar storage, as described in section 6.
- Recommendation activity (optional): only if you opt in during onboarding or in Settings, we log which recommended events were shown to you, which you saved, and which links you opened, linked to your account. We use it to improve your recommendations, keep it for 180 days, and delete it when you turn the setting off.
- Call-for-proposals alerts: the calls you ask us to remind you about, your alert settings, and which alerts we sent you. These are deleted with your account.
- Talk submissions: the status, talk title, abstract, link and notes you enter for a call. We keep rows you have marked as submitted or later, because they are your history and we use them to work out acceptance rates per person and per conference. These are deleted with your account. If you add an accepted talk to your claimed speaker page, it appears publicly on that page, labelled as self-reported.
- Alert opens and clicks (optional): only if you opted in to recommendation activity when an alert was sent, that alert's email contains a small tracking image and tracked links, and tapping its push notification is counted. We record the first time you opened and clicked it, linked to your account, to measure whether alerts are useful, and we also send these events to our analytics provider. Alerts sent while the setting is off contain no tracking.
- Career goals and season plans: the goals you set, such as giving talks or changing role, with any detail you add, how far you'll travel, a target date and a budget. When you ask for a season plan, we keep the events it picked, the reason for each, what you accepted, dropped or swapped, and any rating you give. A plan that fails to build is kept with the reason it failed, because it counts towards your plan limits.
- Voice debriefs (iOS): if you record a debrief after an event, the recording (up to 60 seconds) is sent to us once, turned into a transcript and draft contacts, and never stored by us. Your phone deletes its copy after the upload, or keeps it until you send or discard it if the upload fails. We keep the transcript and any drafts you haven't saved or dismissed. A draft becomes a contact only when you confirm it.
- Contacts and follow-ups: the people you add as contacts, whether they are Kure-Cal members, listed speakers or people outside Kure-Cal (a name, company and optional link), with the event where you met, your notes, and follow-up dates. Contacts are visible only to you. We send follow-up reminders by email or push as your notification settings allow.
- Morning briefings: which briefings we sent you and which of their sections they showed. Only if you opted in to recommendation activity, we also record when you opened or clicked one.
- Agent waitlist: if you join the waitlist for our Agent plan, when you joined and from where in the app.
- Mobile device data: push-notification token, app version, a locally generated device identifier, and approximate location when you ask for nearby results. Device calendar access is used only when you choose to save or remove an event. The microphone is used only while you record a voice debrief, after you tap record.
- Payment data: subscription product, purchase status, renewal and expiration information processed by Paddle on the web, and by Apple and RevenueCat on iOS. We do not receive or store full payment-card numbers.
3. How We Use Information
- Provide, maintain, and improve the Services.
- Personalize features (e.g., time zone, view preferences).
- Build season plans for your goals, morning briefings for your events, and contact drafts from your voice debriefs.
- Understand feature adoption and improve performance and reliability.
- Communicate with you (account updates, security notices, support).
- Detect, prevent, and investigate fraud, abuse, or security incidents.
- Comply with legal obligations.
4. Legal Bases (EEA/UK Users)
We process personal data under the following legal bases, where applicable:
- Contract: to provide the Services you requested.
- Legitimate interests: to secure, improve, and market our Services, balanced against your rights.
- Consent: where required for non‑essential cookies, marketing communications, and optional recommendation activity logging.
- Legal obligation: to meet regulatory and compliance requirements.
5. Sharing and Disclosure
- Service providers: hosting, analytics, error monitoring, email delivery, and payments—only as needed to perform services for us.
- Legal and safety: to comply with laws, enforce our terms, or protect rights, property, or safety.
- Business transfers: in connection with a merger, acquisition, or asset sale, with appropriate safeguards.
Our service providers are Supabase for authentication, database, and file storage; Vercel for hosting; Upstash for rate limiting; Apple and Google for sign-in and optional calendar connections; Paddle for web payments; RevenueCat and Apple for in-app subscriptions; Expo for push-notification delivery; Resend for email; PostHog for product analytics and session recordings; Sentry for error monitoring; and Google Gemini, which processes public event pages, including the speaker details on them, to build our listings and search. To build a season plan, Google Gemini receives your goal, your home city and travel radius, your budget, the skills and interests in your career profile, and details of candidate events, including the names of people you follow who publicly show they're going. To turn a voice debrief into a transcript and draft contacts, it receives the recording, the event's title and its listed speakers. We don't send your name, email address or account details with either. Their processing is limited to providing these functions and is governed by their applicable terms and privacy commitments.
6. Cookies and Tracking
We use essential cookies to operate the Service. We also use PostHog to understand usage. It runs for all visitors, whether or not they are signed in, and stores an identifier in your browser. It records pages viewed, clicks, your IP address and performance and error details. It also makes session recordings, which replay what you do on a page, such as page views, clicks and scrolling, and which we keep for 30 days. This is not currently controlled by a cookie banner or setting. You can control cookies and similar storage in your browser settings; disabling them may affect functionality.
Call-for-proposals alert emails may contain a tracking image and tracked links as described in section 2, only if you opted in to recommendation activity. You can stop these alerts in Settings or from the link in any alert email.
7. Data Retention
We retain personal data for as long as needed to provide the Services and for legitimate business purposes (e.g., security, backups, legal compliance). When data is no longer required, we securely delete or anonymize it.
Goals and their season plans are kept until you delete the goal or your account. Voice recordings are never stored by us. Transcripts and unsaved drafts are kept until you delete them, which you can do from the event in the app; contacts already saved from a transcript stay. Contacts, notes and follow-ups are kept until you delete them. If someone you added as a contact deletes their Kure-Cal account, that contact and your notes on it are removed too. Changes you make to event listings are recorded and kept for 180 days.
If your plan changes, for example from Agent to Pro or Free, everything you made is kept. Some features stop until you upgrade again, such as building new season plans, recording debriefs, or adding contacts beyond the Free plan's limit of 10.
Google Calendar connections are a Pro feature. If your account no longer has Pro, the connection is paused and nothing syncs. If you don't upgrade again within 60 days, we revoke Kure-Cal's access with Google and delete the stored connection credentials. Events already added to your Google Calendar stay there. Pro members can disconnect at any time from Settings → Integrations, and anyone can ask us to remove a connection sooner.
8. Security
We implement administrative, technical, and physical safeguards appropriate to the sensitivity of the data, including encryption in transit, access controls, and monitoring. No method of transmission or storage is 100% secure.
9. Your Rights
Your rights may include:
- Access, correction, deletion, and portability of your personal data.
- Objection or restriction to certain processing.
- Withdrawal of consent where processing is based on consent.
To exercise rights, submit a request through our contact form. We may verify your identity to process requests.
Mobile users can initiate permanent account deletion from Settings → Delete account. Deletion removes the Kure-Cal account and associated personal data unless retention is legally required, including your goals and season plans, voice debrief transcripts, contacts, notes and follow-ups. Deleting Kure-Cal does not cancel an Apple subscription; subscriptions can be cancelled in Apple Account subscription settings.
10. Other People in Your Contacts and Debriefs
Your contacts, notes and debriefs can include details about other people, such as a name, company or what you talked about. We use them only to provide these features to you, and we never show them to anyone else, including the people concerned. Voice debriefs are meant for your own notes after an event: please don't use them to record a conversation without the other person's agreement. A draft only suggests linking a name to a Kure-Cal member or listed speaker when it matches exactly, and nothing is linked unless you confirm it.
11. Public Speaker and Organizer Pages
We publish pages about people who speak at, and organizations that run, tech events, whether or not they have an account. These pages can show a name, title, company, biography, photo, website and social links, and past and upcoming talks and events. We take this from conference and event pages, public event feeds, a person's or organization's own sites, and what they give us. We do not take photos or profile data from LinkedIn, though we may keep a link to a LinkedIn profile when one of those sources gives it. We rely on our legitimate interest in providing a useful public record of events.
- Claims: if you claim a page, we keep the claim, how it was verified, and any evidence you give, such as a note, a link or your work email address. Our team can review these.
- Your edits: if you own a page, you can change its details and photo or hide it. Organizers who correct an event are recorded with the old and new values.
- Removal requests: anyone can ask us to remove a page from the link on it. We keep the name and email address you give, your reason and the outcome, and we use your email only to handle the request.
- After removal: we clear the page's details but keep the speaker's name on a suppression list, so the page isn't recreated when events are imported again. This can also affect someone else with the same name; contact us if it does.
- API and AI assistants: if we offer a public API or tools for AI assistants, they will expose only what these public pages show, and will respect hidden and removed pages.
You can object to this processing or ask us to correct or remove your page at any time, using the link on the page or our contact form. See also our trust principles.
12. International Transfers
If we transfer data internationally, we use appropriate safeguards such as Standard Contractual Clauses and additional measures as needed.
13. Children’s Privacy
The Services are not directed to children under 13 (or older as required by local law). If we learn we have collected data from a child, we will delete it and take appropriate steps to disable the account.
14. Changes to This Policy
We may update this Policy from time to time. We will update the “Last updated” date and, for material changes, provide additional notice (e.g., banner or email). Your continued use of the Services after changes indicates acceptance.
15. Contact Us
Use our contact form.