Privacy Policy
How Open Role View uses information to provide account access, organize your job search and manage paid passes.
Last updated:
At a glance
Google, Microsoft and LinkedIn provide sign-in, Stripe handles hosted payments, and Postgres stores account and job-search state. Recommendations use saved roles and job information. You can contact us with access, correction or deletion requests.
Browsing and operational logs
Serving the site and API involves request information such as IP addresses, request paths and browser/network details. Application logs record request method, path, status, duration and request identifiers for operation and troubleshooting. Hosting, log and backup retention depend on the deployed services.
Sign-in and account data
We store the sign-in provider, issuer and account identifier, email address, email-verification status, name and profile-image URL when provided, plus account creation/update information. Microsoft email addresses are not treated as verified. We request openid, email and profile for authentication. Different providers create separate accounts; account linking is not currently available.
Your job-search state
We store language and display preferences, followed employers, industry choices, onboarding state, custom searches, saved and hidden roles, viewing and application activity, manually saved roles, and application status, dates, notes and history that you enter.
Recommendations
Saved roles and job information are used to suggest related roles. Automatic hiding and recommendations use job-matching data and your saved choices. Job-source text is sent to OpenAI for enrichment, and job title, industry and summary information is used for embeddings.
Payments and access
Stripe processes payment information on its hosted checkout. Our database records checkout-session, price, customer and payment references, purchased pass terms, payment/refund/dispute dates, access grants and related administrative history. These records support paid access and billing inquiries.
Cookies and browser storage
An HttpOnly sign-in cookie supports account access. Session storage holds temporary authentication/visit and checkout-return state. Theme and language choices can be stored locally and in first-party preference cookies, whose configured lifetime is one year. Durable job-search preferences and account state are stored in Postgres. The default account-session expiry is 30 days.
Activity and tracking
Open Role View records sign-in and visit activity and job interactions to operate the product. We use Cloudflare dashboard traffic analytics based on requests handled by its infrastructure. We do not add third-party browser analytics scripts or advertising SDKs to the application. Operational request logging remains part of running the service.
Sharing your personal data
We do not sell or rent your personal data. The service providers described below process information to provide authentication, payments, hosting, job enrichment and support-email routing.
External websites
Employer/application links and provider sign-in or payment pages have their own privacy practices. Loading a Google or LinkedIn profile image can also contact an external image host.
Access, correction and deletion
Contact us to ask about your personal data, request access or correction, or request account/data deletion. Deletion is handled through a request rather than an immediate self-service action. Billing, operational and backup records may require separate handling; no blanket deletion deadline is promised.
Protection and policy changes
Account access uses authenticated sessions and request protections. See Security for details and reporting. We update this policy when processing changes; the displayed revision date identifies the current content.
Campaign attribution
When you arrive through a tagged link, we temporarily keep its campaign tags (source, medium, campaign, campaign ID, content and term) in session storage for the current tab. We carry these tags through sign-in and save them with a newly created account to understand which campaigns bring signups. Existing accounts are not updated. Saved tags follow account-data retention; temporary tags are cleared after authentication or logout. Attribution may be lost when the tab closes or storage is unavailable. We do not send these tags to identity providers or upload conversions to advertising platforms.
Data controller
Benjamin Ryder
Avenue de Crousaz 11 1010 Lausanne Switzerland
Service providers
LinkedIn provides optional sign-in. We receive an account identifier, issuer, email address, email-verification status, name and profile-image URL when provided. LinkedIn handles its own sign-in page. We do not request access to connections, messages or posting.
Processing location: International processing; see LinkedIn’s privacy policy for locations and practices.
Microsoft
Microsoft provides optional sign-in for personal accounts. We receive an account identifier, issuer, email address and name when provided. Microsoft handles its own sign-in page. We do not request access to Outlook mail, calendars or files.
Processing location: International processing; see Microsoft’s privacy statement for locations and practices.
Google / Gmail
Google provides sign-in. We receive your account identifier, email address, email-verification status, name and profile-image URL. Google handles its own sign-in page. Our support mailbox is hosted by Gmail. Google processes sender and recipient details, message content, attachments and email metadata to receive, store and send support correspondence.
Processing location: Worldwide.
Stripe
Stripe handles hosted checkout and payment details. We store checkout, price, customer and payment identifiers, payment dates and refund/dispute status to manage access.
Processing location: Ireland, United States, and other countries used by applicable subprocessors and support providers.
OpenAI
OpenAI processes job-source text for summaries, classification and translations, and job titles/industry/summaries for embeddings. Recommendations match job information against saved roles. This is not an upload of your sign-in profile or application notes.
Processing location: International processing in the United States and other locations listed for API services in OpenAI’s published subprocessor list. EU-only processing is not established for this service.
Neon
Neon hosts the production Postgres database. It stores account identity, sessions, preferences, job-search and application state, activity, recommendation data and billing references so we can operate the service.
Processing location: Germany — production database project.
Netcup
Netcup hosts the backend and job-processing services. These services handle authenticated requests, account and job-search data, billing references and operational logs. Serving API requests also involves network information such as IP addresses.
Processing location: Germany — backend server.
Cloudflare
Cloudflare delivers the public website and app frontend and provides dashboard traffic analytics from infrastructure requests. Serving pages and static assets involves request and network information such as IP addresses, requested URLs and browser details. Cloudflare Email Routing forwards messages sent to our support address to Gmail.
Processing location: Worldwide infrastructure, generally near end users. Support and subprocessors may process information internationally.
Data retention
Account and job-search data is retained for account operation and handled through verified manual deletion requests. Necessary billing records are preserved separately where required for accounting or legal purposes. Neon keeps database restore history within the project’s configured history window; deleted data may remain in that history until it expires. We do not promise immediate removal from every backup or an automatic cleanup deadline.
The production Neon database is configured with 24 hours of restore history. This is the database recovery window; it does not set a deletion deadline for account data, support emails or billing records.
International transfers
Our primary Netcup server and Neon database project are in Germany. Other providers process information internationally as described above, including outside Switzerland. Hosting the server and database in Germany does not mean all processing takes place there. See the provider locations and linked policies for their processing practices.
Request account/data deletion
Email us to request deletion of your account and personal data. Sending a request does not immediately delete your data or refund paid access. Signing out only ends your current session.
Request account/data deletionContact
For privacy questions or requests about your account data, email us.