Privacy Policy for Climb

This Policy applies to information processed through the Climb iOS app (bundle ID `io.climb.Climb`), backend services we operate for Climb (including Supabase-hosted APIs and Edge Functions), and the Climb website at climbapp.co. It does not apply to third-party websites, career platforms, or email providers you connect or visit outside Climb.

2.1 Information you provide

Depending on how you use Climb, this may include:

• Job-search content you enter: company names, job titles, application status, dates, locations, work type, salary notes, recruiter names, job descriptions, notes, timeline events, and reminders.
• Onboarding preferences: answers about your job-search stage, application volume, sources, frustrations, tracking habits, weekly goals, and reminder preferences (stored on device).
• Account information (optional): if you Sign in with Apple, we receive an Apple-provided user identifier and, when you choose to share it, your name and/or email (or Apple’s private relay email).
• Cloud sync (optional): core tracking features store job-search content on your device. If you Sign in with Apple, that on-device content—including applications, notes, salary information, recruiter names, timeline events, reminders, and related company logo/domain identifiers—is uploaded to our servers (hosted by Supabase) so it can sync across your devices. Signing out leaves that on-device content on this device. Signing in with a different Apple ID replaces this device’s applications and related records with that account’s cloud data. Cloud sync is not enabled until you sign in. Usage analytics are described separately in Section 2.4.
• Support communications: if you email us, we receive the content of that correspondence.

2.2 Email connection (Coming Soon — not currently offered)

Gmail connection and inbox scanning are not currently available in the live Climb app (shown as Coming Soon pending provider approval). When that feature is enabled and you choose to connect an email account, we would request access needed to identify recruiting-related messages and may store structured fields such as sender display/address, subject line, a short snippet, classification metadata, and hashed message identifiers for deduplication.

We do not store full email bodies as part of normal Climb processing. OAuth tokens would be stored encrypted on our servers and would not be exposed to the mobile client. Until the feature is enabled for you, Climb does not request Gmail OAuth access or scan your inbox.

2.3 Information created by AI processing

Climb does not currently send your content to a language-model provider for typical app use. If email scanning or related AI suggestion features are later enabled, limited message metadata (such as subject/snippet) and related context (such as your application list) may be sent to our server-side language-model provider to help classify recruiting-related mail or generate suggestions. Model outputs can be incorrect; you would control whether suggested updates are applied.

2.4 Device and usage information

• Local app preferences and notification settings
• Notification permission state (if you enable reminders or related alerts, including trial-ending reminders)
• Basic technical diagnostics you or Apple may surface when reporting crashes
• Apple may present an in-app App Store rating prompt. That prompt is provided by Apple; we do not receive your star rating or written review through Climb unless you choose to leave a public App Store review.

App analytics: We use PostHog to understand how people navigate and use Climb, including which onboarding screens they reach and where they stop. Analytics events may include:

• Screen or onboarding-step names, step order, navigation actions, and completion events
• Paywall views, button taps, and purchase, trial, or restore outcomes, including product identifiers and subscription/trial status
• Feature-use events, such as creating or updating an application, adding a reminder, or exporting applications, with limited properties such as application status or reminder type
• Event timestamps, app version/build, device model, operating system version, and identifiers used to distinguish users, sessions, and onboarding or purchase attempts

These analytics events are sent to PostHog even if you do not sign in. Before sign-in, events use an app-generated identifier. If you Sign in with Apple, we associate analytics with your Climb account identifier and may provide the name and email address available on your account, including an Apple private relay address. This can link earlier app activity to your account.

Our custom screen and feature-use event properties do not include the text of your questionnaire answers, application notes, job descriptions, salary entries, or payment card details. We use this analytics information to measure onboarding completion, understand feature usage, identify problems, and improve Climb, not for targeted advertising. See PostHog’s privacy policy for information about PostHog.

2.5 Website information

If you visit climbapp.co, standard server logs and hosting providers (such as Vercel) may process technical data such as IP address, browser type, and request metadata needed to deliver and secure the site. We also use Vercel Web Analytics, a cookieless first-party analytics tool, to measure aggregate site usage such as page views, referrers, and approximate geography. We do not use this information for advertising, and we do not run third-party advertising or cross-site behavioral tracking pixels on this website.

Do Not Track: Some browsers send a “Do Not Track” (DNT) signal. We do not currently respond to DNT signals. Vercel Web Analytics is used for first-party site measurement, not targeted advertising. Our website host may still process standard server logs as described above, which are used to deliver and secure the site—not for targeted advertising.

2.6 Purchases and subscriptions

After onboarding, using Climb on iOS requires an active Climb Pro subscription or free trial (a hard paywall). Climb Pro is an auto-renewing subscription (currently marketed as a weekly plan). Purchases and free trials are processed by Apple. We use RevenueCat to check whether your subscription or free trial is active and to restore purchases. We use Superwall to decide which paywall to show and to measure paywall experiments.

RevenueCat, Superwall, and Apple may process: an app user identifier (an anonymous identifier before you sign in, and your account identifier after you Sign in with Apple); product and entitlement identifiers; trial and subscription status; and device identifiers commonly used to restore purchases (such as an Identifier for Vendor). If you are signed in, Superwall may also receive your name and email so a paywall can be targeted or personalized. We do not receive your full payment card number; Apple processes payment.

2.7 Company logos and search

When you search for or display company information, Climb may request logo/brand metadata from Brandfetch (or a similar provider) using a public client identifier. Queries may include company names or domains you enter.

We use information to:

• Provide, maintain, and improve Climb (pipeline tracking, reminders, optional cloud sync, and—when available—optional email-assisted suggestions)
• Authenticate you and secure accounts
• Process and display subscription / trial status (including Climb Pro)
• Analyze screen navigation, onboarding drop-off, feature usage, and paywall outcomes to improve the app
• Schedule local notifications you enable on this device (for example, follow-up or interview reminders, and reminders before a free trial ends). Climb does not currently send remote push notifications via Apple Push Notification service (APNs).
• Troubleshoot, prevent abuse, and enforce our Terms
• Comply with law and respond to lawful requests

We do not sell your personal information. We do not use email content to build advertising profiles or to contact your employers on your behalf.

Where GDPR/UK GDPR applies, we process personal data on these bases as applicable:

• Contract — to provide the Service you request
• Consent — for optional features such as email connection (when available) and certain notifications (you may withdraw consent by disconnecting email or changing iOS/Settings permissions)
• Legitimate interests — securing the Service, preventing fraud/abuse, and improving reliability, balanced against your rights
• Legal obligation — when we must retain or disclose information to comply with law

We share information only as needed with service providers who help us operate Climb. Your use of those services may also be governed by their own terms and privacy policies.

We do not share your job-application notes or email snippets with other Climb users.

Processors act under instructions and appropriate contractual protections where required.

• On-device data remains until you delete it, uninstall the app, or clear app data. Signing out of cloud sync does not delete that on-device data.
• Account switch: if you Sign in with a different Apple ID, this device’s local applications and related records are replaced with that account’s cloud data.
• Cloud account data is retained while your account is active. If you delete your account in-app, we delete associated cloud user data subject to short backup/technical residual periods and any legal retention requirements, and we remove synced data from this device.
• Email connection (when available): disconnecting email revokes/stops use of tokens; you may choose to purge related email-event records where that option is available.
• Subscriptions: Apple, RevenueCat, and Superwall retain purchase, trial, and paywall records as needed for billing, tax, fraud prevention, and paywall measurement.
• App analytics: Analytics sent to PostHog are stored separately from your on-device content and cloud-sync data. Signing out, uninstalling Climb, or deleting your Climb cloud account does not automatically delete previously collected analytics. Contact support@climbapp.co to request access to or deletion of analytics associated with you, subject to applicable rights and retention requirements.

• On-device data: Applications and related content can live in local storage on your device (SwiftData) even without an account.
• Cloud data (optional): If you sign in, synced content may be stored with access controls (including row-level security patterns) intended to isolate users.
• Tokens: When email features are enabled, email OAuth tokens are encrypted at rest on the server.
• Transmission: We use HTTPS/TLS for network calls to our backends and major providers.

No method of transmission or storage is 100% secure. You are responsible for controlling physical access to your device and your Apple ID.

Depending on your location, you may have rights to access, correct, delete, export, or restrict certain personal data, and to object to or withdraw consent for certain processing.

In Climb you can typically:

• Edit or delete applications and related records on device
• Export applications (JSON) from Settings where available
• When email connection is available: disconnect email and optionally delete email-derived events
• Sign out (keeps on-device data) or delete your cloud account (Settings). Signing in with a different Apple ID replaces this device’s local applications with that account’s cloud data
• Disable notifications in iOS Settings or in-app reminder toggles
• Manage or cancel subscriptions and trials in Apple’s subscription settings

To exercise privacy rights or ask questions, contact support@climbapp.co. We may need to verify your request. You may also lodge a complaint with your local data protection authority.

California residents: We do not “sell” or “share” personal information as those terms are commonly defined for targeted advertising. You may request know/delete rights via the contact above. As described in Section 2.5, we do not currently respond to browser Do Not Track signals.

Children’s privacy: Climb is not directed to children under 13 (or under 16 where that is the applicable digital consent age). We do not knowingly collect personal information from children. If you believe a child has provided personal information, contact us and we will take appropriate steps to delete it.

We and our processors may process data in the United States and other countries. Where required, we use appropriate safeguards (such as standard contractual clauses) for transfers from the EEA/UK/Switzerland.

We may update this Policy from time to time. We will revise the “Last updated” date and, when changes are material, provide additional notice in the app or by other reasonable means. Continued use after the effective date constitutes acceptance of the updated Policy where permitted by law.

Questions about privacy:

Contact: support@climbapp.co
Operator: Rohan Wilmot
Postal address: 12555 Foothill Avenue, San Martin, California