Effective date: September 4, 2026
Openings makes public technology job listings easier to find. This policy applies to the Openings website and mobile application and explains what information they display, what they save on your device, and when they connect to external services.
1. Public data displayed by Openings
Openings reads public data published by the openings-dev/data-pipeline repository. A listing can include its title, description, excerpt, tags, job location, salary information, dates, source URL, repository, and community identity.
Openings also displays public GitHub account information attached to a listing, including the author’s name, handle, and avatar URL. Openings derives the GitHub profile link from the public handle. Author profile pages are generated from these public listing records. They do not indicate that Openings has verified, represents, or is affiliated with the person, organization, or employer shown.
2. Preferences stored on your device
Openings stores language, theme, saved and viewed jobs, discovery preferences, and your analytics and notification choices in local storage on your browser or mobile device. These settings restore the experience you selected and are not used to create an account. They remain there until you change them, clear the site or app data, or uninstall the app.
3. Technical monitoring and optional analytics
When configured, Sentry receives sanitized technical errors so maintainers can diagnose failures. The Android app also uses Firebase Crashlytics for automatic native crash reports. Openings disables default personal-data collection and session replay and does not intentionally send searches, job content, request bodies, cookies, user identities, or URL query strings. Diagnostic services can receive technical app, device, operating-system, release, and crash information needed to identify a failure.
Mixpanel is not loaded until you explicitly choose “Allow analytics.” If allowed, it receives a small allowlist of anonymous product events such as a filter dimension, result-count range, job ID, or original-listing click. It does not receive search text, job content, email addresses, full URLs, IP-derived location, automatic page views, autocapture, or session replay. You can decline or revoke consent at any time on this page; revocation clears the retained anonymous analytics identity and does not affect saved jobs or other product preferences.
In the mobile app, OneSignal is initialized with consent required. Openings does not enable notification processing until you choose to allow notifications and grant the operating-system permission. OneSignal can then process a device or installation identifier and notification delivery or interaction information needed to send and operate notifications. You can disable notifications in your device settings.
Questions about monitoring or analytics can be sent to support@openings.dev.
4. External requests and links
The site reads its public job index from GitHub-hosted raw files. When an avatar is available, your browser requests the remote image URL included in the public data; that image can be hosted by GitHub or another domain. Opening a listing, repository, profile, discussion, or other external link takes you to the destination service, which handles the request under its own terms and privacy policy.
5. How the data is used
Openings uses the public records above to provide search, filters, community pages, author pages, job details, and links back to each original source. Openings does not accept job applications, create candidate accounts, or verify employers and listings.
6. Questions, corrections, and removal requests
If public information is inaccurate or should be removed from the index, use the content correction or removal form or email support@openings.dev. Include the affected Openings URL and original source URL so contributors can investigate.
Information you choose to send through email or GitHub is handled by that channel so contributors can respond to your request. Do not include sensitive personal information that is not necessary for the request.
7. Data changes and retention
Job and author information changes when its public source and the published Openings data change. Theme and language preferences remain in your browser until you change them or clear local storage.
8. Security
Security vulnerabilities should be reported privately to security@openings.dev rather than in a public issue. Response times can vary because the project is maintained by contributors.
9. Policy updates
This policy can change as the product or its data handling changes. The effective date at the top identifies the current published version.