Legal

Privacy Policy

1.Who we are

Skarrow is an online workspace for job discovery, operated by the Skarrow team ("Skarrow", "we", "us"). This policy covers the public website and the authenticated workspace at /app. It applies to customers who create an account and to visitors browsing the public pages.

2.Definitions

Service

The Skarrow website and workspace, including the search console, saved jobs, applications, alerts and account settings.

Boards

The third-party employment platforms Skarrow queries — Indeed, LinkedIn, ZipRecruiter, Glassdoor, Bayt, Naukri, BDJobs, HelloWork, StepStone, Arbeitnow, EnglishJobs.de, Built In, Reed, Dice, Workopolis, SponsorApply, GetGlobalJob, Jora (AU), Visa Sponsor Jobs, VisaJobsDaily and Xing — the only sources of job listings in the Service.

Workspace data

The content you create or that is generated by your actions: searches and their results, saved jobs and notes, applications and their status history, saved searches and alert records, and your preferences.

Operator

The person or organization running this Skarrow deployment, who administers accounts and infrastructure.

3.Account and profile information

Creating an account requires a full name, an email address and a password. We store:

• your name and email address, which identify the account and are used to sign in, to deliver security messages you request, and to reply when you contact us;
• your password as a one-way hash (industry-standard password hashing, never plaintext or reversible);
• the optional profile fields you choose to save in the workspace: current profession, target role, location and time zone, together with the date they were last updated;
• account metadata: creation date, last sign-in date, your plan and its source, and your email-verification status.

Profile fields are visible only inside your own account. You can edit them at any time in Settings → Profile. Your name and email cannot be edited directly in that form (the email is a credential changed through a verification flow — §7; name corrections go through the contact form).

4.Search queries and search history

When you run a search, the search term, location, country code, selected boards and filter options you chose are sent to the boards you selected. These queries originate from the Service's server, so the boards see the server's connection, not your device. Boards process queries under their own policies (§12).

Each execution is recorded as a search run in your history: the query and filters, the boards used, the returned listings (stored so you can reopen the run without re-querying), the result count, status and timestamps. Re-opening a stored run does not query the boards again and does not consume quota. History is private to your account and you can delete individual runs or clear your history.

5.Saved jobs and application information

Saving a listing stores a reference to it in your collection, with any private notes you write. Tracking an application stores the listing reference, the pipeline status you set (planned, applied, interview, offer, closed), applied dates, follow-up dates and your notes, plus a history of every status change. Saved-search alerts store the search configuration, its schedule, and which listings have already been announced to you (so the same listing is never announced twice). All of it belongs to your account and is invisible to other customers.

6.Sessions, session identifiers and IP information

Skarrow sets at most two first-party cookies: a signed session cookie (HttpOnly, same-site, 8-hour lifetime) and — only if you tick "Keep me signed in" — a signed remember-me cookie (up to 365 days). There are no third-party cookies.

For security, each active sign-in is recorded in a session registry visible to you on the Security page:

• a hashed session identifier (the raw value lives only inside your signed cookie; the database cannot use it to sign in as you);
• a short device label derived from your browser's user-agent string (for example "Chrome · Windows");
• the connection IP address of the sign-in, shown as approximate connection information — it is not used to derive or display a location;
• creation, last-activity and expiry timestamps, and whether the session has been revoked.

You can revoke any session (or all of them) from the Security page; a revoked session stops working on its next request. Signing out revokes your session.

7.Email verification and security messages

Email delivery is optional per deployment and is used only for account-security messages — never marketing:

• Password reset: a single-use link that expires in one hour, sent only when you request it. The database stores only a SHA-256 hash of the token.
• Email address changes: a change takes effect only after a single-use, 24-hour verification link sent to the new address is opened there. Until then the change is pending and your current email remains your sign-in credential. The old address is notified after the change where delivery is configured.
• Security notices: records of password changes, email changes and session revocations are kept in your visible security activity (Security page) and, where email is configured, a notice is sent to your account email.

Security events store the event type, a short description, the time and the connection IP — never passwords, tokens or cookie values. Where email delivery is not configured, nothing claims to have been emailed; the in-app record is the source of truth.

8.Payments (Stripe)

When billing is enabled on a deployment, paid subscriptions are processed by Stripe, an independent payment processor. Checkout and the billing portal happen on Stripe's own infrastructure; Skarrow receives signed webhook events and stores only the subscription state it needs to grant your plan: subscription and price identifiers, status, period dates and cancellation state.

Card numbers and payment credentials never reach Skarrow. Skarrow does not decide payments from its own database — the webhook record is authoritative — and support staff cannot see your payment details, only the subscription state.

9.Data exports

From Settings → Data & Privacy you can download a copy of your data (skarrow-account-export.zip) at any time. The export requires your current password and contains JSON files with: your profile and account metadata, search preferences, your saved jobs with notes, your applications and their status history, metadata of your search runs (most recent 500 runs) — the runs' queries, filters, boards, status and counts, not the stored listing payloads — your saved searches and alert settings, the labels and timestamps of your active sessions, and your subscription records.

The export never contains passwords or their hashes, tokens, session secrets, other customers' data, internal administrative audit records, raw webhook payloads or payment credentials. The archive is generated for your request only; there is no shared or guessable download link. Exports are rate limited to five per hour per account and each export is recorded in your security activity.

10.Account closure and deletion

You can request account closure from Settings → Data & Privacy. Closure requires your current password, is refused while an active paid subscription exists (cancel that first through the billing flow), and is cancellable while pending.

A pending request marks the account for closure; sign-in keeps working until the closure is completed. Completion is a reviewed operation performed by the team against the service's records and backups — the product does not delete data irreversibly with a single click, and it does not claim to. When a closure is completed, the account and its workspace data are removed from the live service; residual copies may persist in operator backups until those backups are naturally replaced or purged under the operator's backup procedure. Records the operator must keep for security and legal accountability (for example the internal administrative audit trail) are retained in a form that no longer identifies you as an active customer, per §11.

11.Data retention and operational logs

Workspace data (§3–§5) is retained while your account is open. There is no automatic deletion of customer content; you can delete search runs and saved items yourself, and anything else can be removed on request through the contact form or by closing your account (§10).

Operational records kept by the service:

• the usage ledger (per-search quota accounting), retained with the account so plan enforcement stays accurate;
• the session registry rows, which expire with their sessions and are removed when revoked sessions are cleaned up or the account closes;
• security activity visible to you, retained with the account as your security history;
• an internal administrative audit trail of operator actions on accounts — append-only, visible to administrators, not to customers, and retained for accountability after closures in a form that no longer tracks an active customer;
• contact messages you send us, retained until the conversation is resolved;
• the deployment's web-server logs (standard access logs handled by the operator's infrastructure) — separate from the application and subject to the operator's log-retention procedure.

Exact retention periods for completed closures and operator logs depend on the deployment's backup and log procedures; ask the team through the contact form for the specifics of this deployment.

12.Data sources and third-party services

Skarrow works with a small, explicit set of third parties:

• Employment boards (data sources): the boards listed in §2 receive your search queries (§4) and are the source of every listing. They are independent controllers of the data they collect when you visit them; their own terms and privacy policies govern that relationship. Skarrow is independent of, and unaffiliated with, every board.
• Stripe (payments, only when billing is enabled): see §8. Stripe processes payment data as its own controller under its privacy policy.
• Email delivery provider (the operator's SMTP relay): delivers the security messages in §7 to you.
• Google Fonts: the interface loads two font families from Google Fonts, as part of any page visit. No Skarrow data is attached beyond standard web-serving headers.

Skarrow uses no advertising networks, no analytics providers, no social plugins and no data brokers. It does not sell or share your personal data.

13.Security

Skarrow applies layered protections: one-way password hashing; CSRF protection on every state-changing request; signed, HttpOnly session cookies; single-use, hashed, expiring tokens for password reset and email change; per-request authorization against the database (a revoked or suspended account loses access on its next request); signature-verified webhook processing; and rate limiting on credential and sensitive operations. No service can promise perfect security — if you believe you have found a vulnerability, please tell us through the contact form.

14.Your choices and rights

• Access and portability: download your data any time (§9).
• Correction: edit your profile in Settings; ask the team for anything else.
• Deletion: delete items yourself, or request account closure (§10).
• Objection to processing: essential security and billing processing cannot be switched off without breaking the service (§7, §8); there is no marketing processing to opt out of.
• Sign-out: revoke sessions any time (§6).

Rights requests are handled through the contact form. Depending on where you live, local law may grant you additional rights; this policy describes the Service's behavior, not a legal certification.

15.Children

The Service is not directed at children and is not intended for anyone under the age of digital consent in their jurisdiction. Accounts suspected of belonging to children may be suspended.

16.Changes and contact

Material changes to this policy update the effective date and version above; the current text is always the one published on this page.

Contact: privacy questions, data requests and reports go through the contact form — the team replies to the email you provide.