Effective date: August 17, 2026
Openings makes public technology job listings easier to find. This policy explains what information the site displays, what it saves in your browser, and when your browser connects 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 in your browser
Openings stores your language and theme preferences in your browser’s local storage. These preferences restore the interface you selected and are not used to identify you. They remain in that browser until you change them or clear the browser’s site data.
The site does not set analytics cookies or load analytics scripts.
3. 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.
4. 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.
5. 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 [email protected]. 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.
6. 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.
7. Security
Security vulnerabilities should be reported privately to [email protected] rather than in a public issue. Response times can vary because the project is maintained by contributors.
8. 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.