Version 2026-10-05.draft14 · Effective {Effective date} · {Company Name} LLC

DRAFT: not yet reviewed by an attorney. Placeholders in {braces} must be completed before launch. This policy describes how the Site's software actually works as of version 2026-10-05.draft14. Re-check it whenever features change.

Privacy Policy

{Company Name} LLC ("we", "us") operates SecondWatch Careers (https://secondwatchcareers.com). This policy explains what personal information we collect, why, how long we keep it, who we share it with, and your choices.

Version 2026-10-05.draft14 · Effective {Effective date}

Summary

• Law enforcement officers create an account and verify their status to see full listings and apply. Your officer profile is never public, employers and agencies can't search or browse officers, and an employer sees your details only when you apply to its job. Verification documents are encrypted, seen only by our reviewers, and deleted right after the decision. You can instead verify instantly with GovX ID, in which case we receive only your GovX verification result (details). See Officer accounts and data.
• We have no analytics, advertising or tracking cookies and no third-party scripts. We use only essential cookies (see Cookies).
• Payment cards are handled by Stripe. We never see or store card numbers.
• Employer and agency accounts give us account details. Agencies may also give us verification information, which we use only to verify them and delete on a schedule.
• Job alerts are optional. We email them only for searches you save; without an account, only after you confirm your address (double opt-in). Every email has a one-click unsubscribe. See Job alerts.
• Agency reviews, pay reports and hiring-time reports from verified officers are published anonymously, only after moderation, and pay and hiring times only as aggregates from at least 5 different officers. Agencies and employers never learn who wrote them. See Reviews and pay reports.
• Employers don't get your email address unless you choose to share it on an application; they contact you through site messages. Your career profile, application tracker and match labels are private to you. See Career profile, tracker and match labels. So are your mock interviews: we never store audio, and employers never see them (details).
• Messages with employers are tied to one application, stored encrypted, and deleted with it. See Messages and hiring stages.
• We don't sell or rent personal information, and we don't share it for cross-context behavioral advertising.

Information we collect

Visitors (no account). Browsing is anonymous to us: no profiles, and no record of which jobs or agencies you view or compare (for signed-in officers too: we don't keep a viewing history). For employers' job analytics we keep only daily totals per job (views, apply-form opens, and where the visit came from, such as search or an alert). Unique visitors are counted in memory with a random key that changes every day and is never stored, so no visitor identifier or IP address is saved for analytics. We use no third-party trackers or advertising cookies. If you search by distance from a ZIP code, we work out distances on our own server from public U.S. Census data. Your ZIP code isn't sent to any mapping or geocoding service and isn't stored unless you save the search as an alert. If you ask for job alerts without an account, we store your email address and the searches you save (see Job alerts). Like any website, our server necessarily receives your IP address and browser details to deliver pages. We use IP addresses briefly in memory for security rate limits, and store them only where described below (for example, with security events or a listing report). If you use Report this listing, we store your reason, any details you type, your optional email address, the time, and your IP address in our audit log.

Support tickets and error reports. If you contact support, we store what you send and a small amount of technical context. See Support tickets.

Officer account holders. See Officer accounts and data for the full details: account and profile information, verification documents (deleted after the decision), and applications you choose to send.

Employer and agency account holders.

How we use it

To provide and secure accounts; publish and display your listings and profiles; verify that agency accounts represent real agencies and that officer accounts belong to law enforcement officers; limit full listings and applying to verified officers; deliver officers' applications to the employer they chose; process payments and prevent fraud; screen posts for discriminatory wording and review reports; respond to requests; comply with law and enforce our Terms; and keep records of agreements. We don't use personal information for advertising and we don't make automated decisions with legal effects about you. Automated wording checks only route a post to a human. Match labels ("Strong / Good / Possible match") are a sorting aid computed from job-related fields only; they never use protected characteristics and never decide anything (see Career profile, tracker and match labels).

Legal bases (if applicable)

{Attorney: include only if serving EU/UK users. Contract, legitimate interests (security, fraud prevention, moderation), legal obligation, consent (recruiter contact publication).}

Sharing

We share personal information only with:

• GovX (officers who choose Verify with GovX ID): we send you to GovX's site to sign in. GovX learns that you're verifying with us; we send GovX no other information about you. See Verifying with GovX ID.
• Employers you apply to (officers): only the employer that owns the job post you apply to receives your application, and only the details you choose on that application: your full name, a display name or your initials; your current agency and home city/state only if you tick them; your email, phone, qualifications (certifications, specialties, education, languages) and military service only if you tick them; your resume, cover note and verified-officer status (status, years of service, date last verified), and any messages you send about that application. If you shared qualifications, the employer may also see a match label computed only from what you shared. No other employer, agency or visitor can see it. Employers can't search for officers, except for the anonymous card of officers who opt in to officer search (see Officer search). The employer can export its applicants to a spreadsheet (CSV) containing only those same shared details, and you can see each export in your activity log. See Identity protection.
• Agency reviews and pay reports (officers) are shown publicly without your name, initials, account or exact dates, and pay only as aggregates; we don't tell the agency, employers or other users who wrote them. See Reviews and pay reports.
• Stripe (payments). Stripe processes your card and billing details under its own privacy policy: https://stripe.com/privacy.
• Teammates of an employer account (employers): the owner and the teammates they invite share the organization's posts, applicants, notes and analytics, according to their role. An officer's application to that employer is visible to its team.
• Our email provider ({email provider name}), to deliver account emails.
• Our hosting provider ({hosting provider name}), which stores the Site's servers, database and backups.
• The public: the job posts, agency profile content and (with consent) recruiter contact details you choose to publish. Public pages are listed in our sitemap, and live job posts carry search-engine markup (title, a public summary, dates, employer, location and pay), so search engines may index and show them. Officer information is never part of it.
• Legal and safety: when required by law, subpoena or court order, or to protect rights, safety and security.
• Business transfers: a successor in a merger, acquisition or sale of assets, subject to this policy.

We don't send mock-interview answers to anyone: they're scored on our server (see Mock interviews). If you choose to answer by voice, the speech-to-text is done by your browser, not by us; some browsers (for example Chrome and Edge) send the audio to their maker's speech service (Google or Microsoft) under that company's privacy terms.

We don't send any personal information to the third-party job sources that provide aggregated listings. We only receive listings from them.

How long we keep it

These periods are enforced automatically by the Site (config values in brackets):

Support tickets

You can contact support with or without an account at /support. We store:

• What you send: your email address, the category, subject, description and your later messages, and an optional screenshot. Screenshots must be PNG or JPEG images; we re-encode them to remove hidden metadata (such as location) and store them encrypted. Only our support admins can view them, and each view is recorded in our audit log.
• Technical context we attach automatically, limited to: your account type and account number (if you're logged in), whether your email is confirmed and two-factor login is on, your officer verification status (officers), the page you came from (its path only, without query strings or link codes), your browser's user-agent string, and the reference numbers of recent server errors linked to your account or browser session. We never attach your verification documents, resume, password, sign-in codes or security tokens.
• Our replies and internal notes. Staff may add internal notes you don't see, and may prepare draft replies. Support is handled by the site owner and an AI assistant that works on our own server under the owner's direction; the assistant can read tickets (with email addresses masked), add internal notes and draft replies, but only a human admin can send a reply. The assistant can't access verification documents, resumes or payment details through the ticket tools.
• If you're not logged in, we email you a private link to confirm your address and view the ticket. Anyone with that link can read and reply to the ticket, so keep it private. We don't email replies until you confirm.

Please don't put passwords, sign-in codes, ID documents, badge photos or other sensitive information in a ticket; officer verification has its own protected page. We use ticket data only to answer you, fix problems and prevent abuse (the form has rate limits and anti-spam checks; security events such as blocked submissions are recorded with your IP address in the audit log). Retention periods are in How long we keep it. Deleting your account deletes your tickets (including those sent from the same email address while logged out), their screenshots and your error records.

Security

We use HTTPS (in production), salted password hashing, two-factor authentication (required for admins and officers, available to everyone), CSRF protection, strict content-security headers, rate limits, encryption at rest for agency verification documents and backups (when keys are configured), always-on encryption at rest for officer verification documents and resumes, least-privilege file permissions, and an audit log that records every view of an officer document and every access to an application. Messages between employers and applicants and employers' private notes are also encrypted at rest. No system is perfectly secure. If we learn of a breach affecting your personal information, we'll notify you as the law requires.

Your rights and choices

• Access and correction: you can view and edit your account, posts and profile at any time. Officers can view, and delete one by one or all at once, their mock interviews at /interview.
• Deletion: signed-in users can delete their account under Account → Delete account. You can also email {privacy contact email}. For officers this withdraws and deletes your applications (with their messages) and deletes your verification documents and records, your career profile and default resume, your application tracker, your mock interviews, your agency reviews, pay reports, hiring-time reports and job alerts. It also deletes your support tickets, their screenshots and your server error records.
• Withdrawing an application: officers can withdraw any application from My officer account.
• Recruiter contact: agencies can untick the consent box at any time to hide recruiter details immediately.
• Emails: we send only transactional emails (no marketing lists), plus the job alerts you set up. Every alert email has an unsubscribe link (and supports one-click unsubscribe in mail apps), and you can manage alerts at /alerts or through the link in each email.
• State privacy rights {PLACEHOLDER: California (CCPA/CPRA) and other state laws may give residents rights to know, access, correct, delete, and opt out of "sale"/"sharing" and of certain profiling, plus non-discrimination for exercising rights and the right to appeal. Attorney to confirm which laws apply given our size and revenue, and add a "Notice at Collection", request-verification method, authorized-agent process and response timelines.} We don't sell or share personal information as those laws define it.

To make a request, email {privacy contact email}. We may need to verify your identity.

Cookies

Cookie notice. We use only strictly necessary cookies, so no consent banner is required for them. We have no analytics, advertising, social-media or tracking cookies, and no third-party scripts on our pages.

All are HttpOnly, SameSite and (on HTTPS) Secure. When you pay, you leave our Site for Stripe's checkout page, which sets its own cookies under Stripe's cookie policy. {Attorney: confirm no consent is needed in target jurisdictions for strictly necessary cookies.}

Officer accounts and data

We know officers value discretion. This is how officer accounts work:

• What we collect. Your name, email (confirmed by a link), password (salted hash), optional two-factor settings, your status (active, retired, former, corrections, federal, military police or reserve), current or last agency, its state, years of service, and optional phone number. Optionally: a display name, your home city/state, your default share choices, and a career profile (see below). We don't ask for your street address.
• Verification documents. At least one document showing your status (badge photo, agency ID card, POST / certification card or letter, retirement ID, DD-214, agency letter or SF-50) and, if you choose, a selfie holding a photo ID. We check each file is a real image or PDF, strip hidden metadata (such as GPS location and camera details), and store it encrypted. Only our reviewers can open it, and every view is logged. We delete the files right after the decision and keep only the decision, reviewer, date, the types of documents, the checklist and notes. We compare a selfie with your ID by eye only: we don't use face recognition and don't create biometric identifiers or templates {Attorney: confirm no biometric-privacy notice (e.g. Illinois BIPA, Texas, Washington) is needed for manual review}. Please cover ID numbers and details we don't need.
• Visibility. Your profile and verified-officer status are never public and aren't shown to employers or agencies, except to an employer you apply to. Employers and agencies can't search, browse or list officers, unless you opt in to officer search, and then they see only an anonymous card (see Officer search).
• Applications. When you apply to a direct post you send the details you choose (see below), optional phone, resume (PDF or Word, checked and stored encrypted), cover note and verified-officer status to that employer only. Your email address goes to the employer only if you tick Share my email on that application; otherwise the employer contacts you through site messages. The employer receives an email that a verified officer applied, without your details, and must log in to see them; every view and resume download is logged, and you can see that log under Who opened my applications. Withdrawing an application ends the employer's access to it at once. The employer's use of your application after that (for example a copy it downloaded before you withdrew) is governed by its own privacy practices.
• Aggregated listings. When you open an aggregated listing's original link, you leave our Site; we don't send your information to that source.
• What we don't do. No selling or sharing for advertising, no public profiles, no resume database, no marketing emails (job alerts only if you set them up, and sponsored job emails only if you turn them on).
• Your choices. Edit your profile and privacy settings, choose what each employer sees, withdraw applications, see who opened them, manage two-step login, or delete your account and data at any time. Retention periods are in How long we keep it.

Messages and hiring stages

Employers move applications through hiring stages (for example interview or background check). You see a simplified status for each application and get an email when it reaches a later stage. The employer's star ratings and private notes are never shown to you or anyone else outside that employer's account. You and the employer can exchange messages about one application at a time. Our site doesn't show your email address in messages, and notification emails don't include the message text. Messages are stored encrypted and deleted with the application (see How long we keep it). We don't read messages except when needed to investigate a report, a security problem or a legal request. {Attorney: confirm this access statement and whether messages need a longer hold when an employer is subject to record-keeping duties.}

Agency reviews and pay reports

Verified officers can review agencies, report their pay and report how long hiring took them (weeks from application to offer, the year, and whether they were a lateral). They can do this for any agency in our agency directory, including agencies that haven't joined the site ("Unclaimed profile"). Directory records come only from agency profiles and sign-ups on the site and from agency names in real job listings we import. We store the ratings, text, current/former status and the years range you chose (for reviews), or the agency, rank group, pay, benefits answers and years-of-service range (for pay reports), linked to your account so you can edit or delete them and so each officer can post only one review per agency.

• Public display. Reviews appear as "Verified officer" with no name, initials, account or exact dates. The month and year appear only once an agency has 5 published reviews, and average ratings only from 3 reviews. Pay is shown only as medians and ranges from at least 5 different officers' approved reports (middle-50% ranges from 8), rounded, never one report on its own; yes/no answers are shown in words, never as 0% or 100%. Hiring times are shown only as a median from at least 5 different officers.
• When an agency deletes its account. Reviews and reports are the officers' contributions, so they stay on the agency's record, which shows as an "Unclaimed profile". The agency's own responses are deleted. An agency that claims the record later sees the same reviews and can respond again.
• Moderation. Our moderators read each review and pay report before it's published. Automatic checks flag possible names, personal information, threats and unusual pay, but a person decides. Moderators see the content without your name.
• Who can see authorship. Agencies and employers can't see who wrote a review or pay report, and neither is part of any export. Our staff can link a review to an account only when needed for moderation, abuse or legal requests. {Attorney: describe how we'd respond to a subpoena seeking a reviewer's identity (notice to the reviewer where lawful, time to object).}
• Small numbers. Even without names, a detailed review or a pay group with few reports could let someone who knows you guess it's you. Leave out details only you would know.

Career profile, application tracker and match labels

• Career profile. Optionally you can save state certifications, specialties (for example K9, SWAT, FTO), education, military service, languages, the states and job categories you're interested in, a minimum pay, and a default resume (checked and stored encrypted like other resumes). It's used to prefill applications (including one-click apply, which always shows a confirm step with your share choices; phone, email, agency, qualifications and military service are never pre-ticked) and for match labels. No employer can search or see your profile, unless you opt in to officer search (and then only the anonymous card fields you choose); otherwise an employer only sees what you share on an application to its job.
• Match labels. When you're signed in as a verified officer, we compare your profile with each job's state, certification, years-of-service, specialty, category and pay fields on our server, when you view the page, and show you a label with the reasons. Labels aren't stored or shared. We never use military service, languages, education or any protected characteristic (such as age, sex, race, religion or disability) for them. If you share your qualifications on an application, the employer sees a label computed only from what you shared (certifications, specialties and your verified years), never from your preferences or minimum pay. A label is a sorting aid and doesn't decide anything.
• Application tracker. Your site applications (with their live status), jobs you track from elsewhere, follow-up dates and private notes. Notes are encrypted and visible only to you. If you set a follow-up date, we email you a reminder that day (without your notes).

Mock interviews

Verified officers can practise interviews at /interview, for a role type or for a specific job.

• What we store. The role type, the job you practised for (if any), the questions and follow-ups, the text of your answers, whether you typed or spoke each one, and the scores, feedback and tips. All of it is stored encrypted, like resumes and tracker notes.
• Voice answers. Only if you press Answer by voice. Your browser then asks for the microphone, and your browser turns your speech into text in the answer box. You can edit the text before sending it. We never receive, record or store audio, and we don't create voiceprints or any other biometric identifier. Only the text you send reaches us. Speech-to-text is a browser feature: in some browsers (for example Chrome and Edge) the audio goes to the browser maker's speech service (Google or Microsoft) under its privacy terms. If you'd rather not, type your answers. The Read question aloud option uses your device's built-in voice and sends us nothing.
• Scoring. Currently demo scoring: simple rules on our server (answer length, STAR structure, words from the job, filler words, specific details and numbers), explained on every results page. No AI service and no outside company receives your answers. Scores are practice guidance only, not a hiring assessment, and they're never used for match labels, officer search or anything else.
• Who can see them. Only you. Employers, agencies and other users can never see your mock interviews, scores or the fact that you practised for their job. There's no staff or admin screen that shows them; our team could reach them only through the server, when legally required or to fix a problem you report. The audit log records only that an interview was started, finished or deleted, never its content.
• Deleting. Delete any interview, or all of them, at any time. They're deleted with your account and automatically after the times in How long we keep it.

Officer search, invites to apply and sponsored job emails

Officer search is off unless you turn it on on a consent screen. Only verified officers can turn it on.

• What employers see. An anonymous card with only the fields you tick: your initials (or your display name), the state you choose, a years-of-service band, certifications and specialties by default, and optionally the states and categories you're interested in, languages and education. Never your name, agency, email, phone, city, resume, military service or minimum pay.
• Who can search. Verified law enforcement agencies, and employers with a confirmed email and at least one live job our team approved (with a paid search pass where required). Your current agency is blocked automatically if it has an account here, and you can block any employer. Searches are limited (few pages per search, hourly and daily limits, no export) and logged, and unusual activity is flagged for our team. A search shows cards only when at least 5 opted-in officers match. Repeated narrow searches whose results differ by fewer than 5 officers (which could single someone out) are refused and flagged for review. To detect that, we keep which officer accounts each employer's searches returned for 24 hours, then delete it.
• Invites to apply. An employer can invite you to apply to one of its live jobs. We email you and list it under Invites. If you ignore it, the employer isn't told; it learns who you are only if you apply, and then only what you share on that application.
• What we record. Your settings and consent (version and time); which employers saw your card in results or opened it, by day (shown to you so you can block them; kept 365 days); invites and your response; your blocks.
• Pause or opt out any time: your card leaves search immediately. If we change how officer search works, every card is hidden until the officer opts in again.
• Sponsored job emails (separate choice, off by default): when an employer pays for an email blast, we email officers who turned this on and whose job alerts or officer-search profile match the job, at most one a week, marked Sponsored, with one-click unsubscribe. The employer never learns who received it.

{Attorney: confirm the consent wording, whether officer search makes us an "employment agency" or a consumer reporting agency, and whether sponsored job emails are commercial messages needing a postal address (see attorney notes 79–81).}

Job alerts

You can save a job search and get new matching jobs by email, instantly (at most hourly), daily or weekly.

• With an officer account, alerts go to your confirmed account email and are managed at /alerts.
• Without an account, you give us your email address and tick a consent box. We email a confirmation link and send nothing else until you click it (double opt-in). Each alert email has a private link to manage your alerts.
• What we store. Your email address (logged-out alerts), the saved search (keywords, category, state, remote and pay filters, and any extra filters you set: pay range, shift, job type, degree, lateral friendly, and for distance searches the ZIP code and radius you typed), the delivery choice, when we last emailed it, and which listings we already sent for it so we never send one twice. We also keep a short-lived count of alert emails per address, stored under a one-way key, to limit how many we send.
• What's in an alert. Listings follow the same visibility rules as the site: unless you're a verified officer, an alert shows only the public teaser (title, employer, location, pay).
• Stopping. Each email has an unsubscribe link, and mail apps' one-click unsubscribe works too. Unsubscribing turns an officer's alert off, or deletes a logged-out alert (and your email address with your last alert). Deleting your officer account deletes your alerts and any logged-out alerts saved with the same address.

We use alert emails only to send the alerts you asked for.

"Highly active" badge, job-search status and Promoted jobs

• What we count. While you're signed in to an officer account, we keep one number per day for each kind of action: visits, searches, job views, saves, applications, and quiz or Path Matcher use (for example "3 job views on Oct 14"). We don't store which jobs you viewed, your search words, the pages you opened or the time of day. These daily counts are deleted after 30 days.
• The badge. If you've used the site regularly in the last 14 days, your profile can show the words "Highly active". The badge goes away on its own when you're less active. Employers who can already see your profile (officer search, talent pools, or an application you sent) see only those words. They never see your counts, the days you visited or what you looked at. The badge is on by default, and you can turn it off at any time at /officer/visibility.
• Job-search status. You can choose "Actively looking", "Open to opportunities", "Just exploring" or "Off". It is Off by default, and Off shows nothing. If you choose a status, employers who can see your profile see that tag, and they can filter officer search by it. You can change it whenever you like. Unless you turn auto-revert off, "Actively looking" and "Open to opportunities" switch back to "Just exploring" after 60 days without an update.
• Who never sees them. Employers you've blocked never see the badge or your status. Neither does your current agency (the agency on your verified profile).
• Promoted jobs (Active Reach). Employers on some paid plans can have their jobs shown first to highly active officers. This only reorders jobs that already fit your own search filters, saved-alert criteria or match profile (Strong or Good match). It never adds jobs you wouldn't otherwise see. These jobs are labeled "Promoted", and the number shown to you each day is limited. Officers marked "Actively looking" may see one more per list. To count how often promotions were shown, we keep a daily count, and to give employers a weekly total of distinct officers per job, we keep a one-way tag under a random key that changes each week. Both are deleted after 30 days. Employers see only those totals ("shown to 12 highly active officers this week"), never who saw a job. Turning the badge off also turns off Promoted placement based on your activity.

{Attorney: confirm whether the activity-based badge and promotion count as "profiling" under state privacy laws (CPRA/CPA/VCDPA, etc.), whether badge-on by default needs opt-in consent in any target state, and whether showing "Actively looking" to employers needs extra notice (see attorney notes, section 28).}

Feedback from employers

When an employer decides not to move forward with your application, they can choose to add a reason (for example "Position filled" or "Certification or license required") and a short note.

• Who sees it. Only you, on your private Feedback received page. Other officers never see it, and neither do other employers (including your current agency). It isn't part of officer search, talent pools or any export. The employer who wrote it can see only what they sent.
• What you see. The job title, the company name, the date, the reason and the note. We don't show which person on the employer's team wrote it. We keep that inside the employer's account for their own records only.
• Notification. You see a notice on your dashboard. We don't email you about feedback.
• Moderation. Notes are limited to 400 characters. We block notes that contain slurs, profanity, contact details or other personal information, or that mention protected traits (such as age, race, sex, religion, disability or family status). We also remind employers to keep feedback constructive and lawful. You can archive any feedback, or report it as inappropriate. Reported feedback goes to our moderators, who can remove it.
• How long we keep it. For as long as your account is open. Deleting your account deletes it, and deleting an employer account deletes the feedback that employer wrote.

{Attorney: confirm that sharing rejection reasons doesn't create adverse-action or FCRA-style notice duties, that an employer's stated reason can't be used against us as the platform, and whether officers in some states have a right to request the employer's reasons (see attorney notes, section 29).}

Identity protection and two-step login

Your current agency and home location are hidden from employers until you apply, and on each application you choose what that employer sees: your full name, a display name (alias) or your initials; your current agency (off unless you tick it); and your city and state. The name defaults to your initials. We don't collect or share your street address. The choices are recorded with the application, and we don't show employers the fields you didn't share. Our reviewers still see your legal name and agency to verify you. Your email address isn't shared unless you tick it on that application; employers reply through the application's message thread. Your qualifications and military service are also shared only if you tick them. {Attorney: the site owner can switch officers.employer_email to "always" (the earlier behaviour); this paragraph must then be changed back.}

Two-step login. Officer accounts must turn on an authenticator app with one-time recovery codes before verifying their status, seeing full listings or applying. We record when it's turned on or off and when a recovery code is used, and email you when a recovery code is used. If you lose both your phone and your codes, an admin can reset it only after re-verifying your identity (for example a live video call with your photo ID, or a call to your agency at an independently found number); each reset is logged and you're emailed.

Verifying with GovX ID

GovX ID (govx.com) is a third-party service that verifies military, first responder and other affiliations. Using it is optional: you can always upload a document instead.

• How it works. When you click Verify with GovX ID, you go to GovX's site, sign in or register there, and choose whether to share your verification with us. GovX then sends you back to us, and our server fetches the result directly from GovX. Your GovX password never reaches us.
• What we ask GovX for. Your profile (GovX user id, name, and the email/username GovX includes in it) and your verification (status and verified occupations). We don't request GovX's demographics (date of birth, gender, phone, ZIP code).
• What we keep. The GovX status (Approved / Pending / Failed), the law enforcement occupation categories GovX verified (for example "law-enforcement/sheriff/current"), the date we received the result, the method ("GovX ID"), and a one-way hash of your GovX user id (used only to spot one GovX identity being used on several accounts). We don't keep your GovX email or username, and we keep your GovX name only while a reviewer compares it with your account name, then delete it at the decision. Access tokens are used once, during a single request, and are never stored or logged.
• Why. To confirm you're law enforcement so you can see full listings and apply (the same purpose as document verification). We approve automatically only when GovX's status is Approved, the occupation is law enforcement, and the name matches your account. Otherwise a person reviews it, or you can upload a document.
• GovX's own handling. GovX processes your data under its own privacy policy and terms. GovX says it keeps a verification record in your GovX account, uses sub-processors (Google Cloud Vision and Resistant AI) to check documents you give it, stores data in U.S. data centers, and deletes your GovX data on request. {Attorney: confirm the GovX partner agreement's data-use terms and describe any limits here.}
• Retention and deletion. The GovX result stays with your verification record while your account is open and is deleted when you delete your account. To delete your data at GovX, use your GovX account or contact GovX.

Children

The Site isn't intended for anyone under 16, and we don't knowingly collect personal information from children under 16. If you believe a child has given us information, contact {privacy contact email} and we'll delete it.

International users

The Site is operated in the United States and intended for U.S. jobs. Information is stored in the United States.

Changes

If we change this policy materially, we'll update the version and effective date and ask account holders to review it at their next login.

Contact

{Company Name} LLC · {Mailing address} · Privacy: {privacy contact email} · General: {contact email}