Privacy policy

Browsing the cheatsheets and diagrams requires no account, no email and no sign-up. There is no analytics script and no other third-party embed that profiles you.

Pages do carry Google AdSense ads. Google and its advertising partners may set cookies or use device identifiers on this site to serve and measure ads, including personalized ones based on your browsing elsewhere. You can see or turn off ad personalization at Google's Ads Settings, and read how Google uses this data at How Google uses information from sites that use our services.

Your reading preferences — theme, text scale — are kept in your own browser's local storage. They never leave your device and we cannot read them.

Our hosting provider keeps ordinary web server logs (IP address, user agent, requested URL, timestamp) for a short period, as any web server does, to serve traffic and stop abuse.

When you create an account for the job-hunt workspace we store:

• your email address, used to identify the account and to send job alerts;
• a display name;
• a password hash (scrypt, with a per-account salt). We never store the password itself and cannot recover it;
• your search settings, saved searches, job triage decisions, and the notes you write on a posting.

Signing in sets one cookie, jobs.user, holding a signed session token — not your password. Removing it (or signing out) ends the session.

You may upload a résumé so the workspace can match postings against your background and write drafts from it. The uploaded file itself is parsed in the same request and then discarded — we do not keep the file, and we do not keep the raw text.

What we do keep is the structured résumé read out of it, which is the whole résumé: your professional summary, every role with its employer, dates, location and bullet points, your projects, education, certifications, skills, and — if your résumé carries them — your name, email address, phone number and links. This is stored against your account so that a tailored résumé or cover letter is written from your actual history rather than from a handful of keywords.

You are shown everything that was read before any of it is saved, and nothing is stored until you press Save. Every field stays editable and deletable from the account page afterwards, and deleting your account deletes all of it.

Connecting Google is optional. The workspace only asks for connection when you press “Connect Google Drive”, and it requests three scopes and no others:

• openid and email — to know which Google account is connected;
• drive.file — access limited to files this app itself creates in your Drive.

Pressentify cannot see, list, open, modify or delete any other file in your Google Drive. The drive.file scope grants access only to documents the app created — the tailored résumé and cover-letter drafts you ask it to save. Existing documents in your Drive are invisible to it.

We store the connected Google account's email address, an access token, and a refresh token. The refresh token is encrypted at rest (AES-256-GCM). Tokens are used only to create and update the drafts you generate.

Disconnecting Google from the account page revokes the token with Google and deletes the stored credentials. You can also revoke access at any time from your Google account permissions page. Documents already created stay in your Drive and are yours; revoking access simply stops this app from touching them again.

Pressentify's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never sold, never used for advertising, and never used to train machine-learning models.

• MongoDB Atlas — the database where accounts, job postings and profile summaries are stored.
• Vercel — application hosting and server logs.
• NVIDIA NIM — the AI models that read a résumé to extract its structured summary, rank postings, and draft a pitch for a specific job. Résumé text and profile facts are sent to this API at the moment you run one of those actions. Job postings themselves come from public sources.
• Google — OAuth and Drive, only if you connect an account (section 4).
• Gmail (SMTP) — used to deliver job-alert emails to the address on your account.

We do not sell personal data, share it with advertisers, or use it to build profiles for anyone other than you.

Account data is kept until you delete it. You can clear your job profile, disconnect Google, and delete saved searches from the account page. To delete your account and everything attached to it, email pressentify@gmail.com from the address on the account; we will remove it and confirm.

Public job postings collected from company career pages and job boards are not personal data about you and are pruned on their own schedule.

You can ask for a copy of the data held about you, ask for it to be corrected, or ask for it to be erased, by emailing pressentify@gmail.com. If you are in the EU/UK, these are your GDPR rights of access, rectification and erasure; the lawful basis for processing is the performance of the service you asked for, and consent for the optional Google connection.

Passwords are hashed with scrypt. Google refresh tokens are encrypted at rest. Session cookies are signed, HTTP-only and scoped to this site. All traffic is served over HTTPS. No system is perfectly secure, and we do not claim otherwise — please do not store anything in the workspace you could not afford to have exposed.

The job-hunt workspace is not directed at children and accounts are not intended for anyone under 16.

If this policy changes materially, the “last updated” date above changes with it and account holders are notified by email. Questions about this policy go to pressentify@gmail.com.