What we collect, and what we will never do with it.

1. Who runs this

Get You Employed is operated by Danish Nawab, a sole proprietor doing business as FrontPage Labs in the State of Illinois. When this page says "we" it means that one person. When it says "you" it means the person whose name is on the account.

This policy covers the marketing page at getyouemployed.netlify.app and the application behind sign-in at /app/. You can reach a human at build@frontpagelabs.com.

2. What we collect and why

Everything below exists because some part of the product stops working without it. Nothing is collected because it might be interesting later.

• Your email address. It identifies the account and it is how we reach you about billing or an outage.
• Your name, if you sign in with Google. Google tells us your name and your email address when you approve the sign-in. The name is used to greet you in the dashboard header and for nothing else.
• Your password, if you sign in with an email and password instead. It is handled by Supabase Auth and stored as a hash. We never see it and we cannot recover it, which is why a reset sends you a link rather than your old one.
• Your answers to the setup questions. Your industry, the kind of work you want, your years of experience, the cities you would work in, the job titles you are after, the companies you want watched, the words that rule a posting out, the companies you would rather skip, and an example posting you would apply to today. Those answers become the configuration that decides what the crawler looks for and how each posting is scored.
• Your resume, if you upload one. It goes into a private storage bucket under a path that begins with your own user id. The resume editor reads it back to you and exports a PDF. It goes nowhere else.
• Everything on your board. The postings that were found for you, the notes you write on them, your to-do items, what you archived, and the status you set on each application.
• Support messages you send from the support page inside the app, so that somebody can answer them.
• Billing identifiers from Stripe. A customer id, a subscription id, whether that subscription is trialing or active or past due, and the date your trial ends. Your card number never reaches our servers and is never stored by us. It goes directly to Stripe, which is the only party that holds it.
• Ordinary web server logs kept by Netlify, which include an IP address, a browser user agent string, and the time of a request. We do not use them to build a profile of you and we do not join them to your account.

3. What we do not do

• No analytics, no advertising network, no tracking pixel, and no session recording. There is not a single third-party measurement script on this site.
• We do not sell personal information and we have never given it to a data broker.
• We never show your resume or your job list to an employer, a recruiter, or another customer. Your board is visible to you alone.
• We do not apply to jobs on your behalf, so no employer ever receives anything from us with your name on it.
• We do not use your resume or your answers to train a machine learning model, ours or anybody else's.

4. Who else handles your data

Running this on one person's own hardware would be worse for you, not better, so a few companies handle pieces of it. Here is the whole list.

• Supabase. The database, the sign-in system, and the private bucket holding your resume. Data is stored in the United States.
• Netlify. Hosts the site and runs the functions that crawl the job feeds and score what they find.
• Stripe. Takes the payment and holds the card. We see a subscription status and an id, never a card number.
• Google. Involved only if you choose to sign in with Google, in which case Google confirms who you are and passes us your name and email address.
• Google Fonts and jsDelivr. They serve a font file and one JavaScript library that the pages load. As with any resource loaded from another domain, those requests reveal your IP address to them. No account information travels with the request.

If that list ever grows, this page changes first and you get an email.

5. How your data is protected

• Every table has row level security turned on, and every policy is written against your own user id. The public key that appears in the page source is deliberate and it is inert on its own, because it cannot read a single row without a valid signed-in session behind it.
• The service key that can read across accounts exists only in server-side environment variables. It never reaches a browser.
• The resume bucket is private, and its policy only permits opening a file whose path begins with your own user id.
• Everything is served over HTTPS, and the application refuses to be loaded inside a frame on another site.

6. Where the crawler goes

Every morning the crawler reads the public career pages of the companies on your list. Some of those pages accept a search keyword, and the keyword comes from your setup, something like "analyst" or "Chicago". Nothing that identifies you travels with the request. An employer does not learn that you are watching them, and they receive no signal from us at all until you decide to apply on their own site.

Every feed we read is public and keyless. We do not pay for job data, and we do not use any service that would charge us per lookup, which is also why nobody needs to be told who is doing the looking.

7. Cookies and browser storage

There is no advertising cookie and no analytics cookie here, because there is no advertising and no analytics. Your browser does store two things:

• Your sign-in session, which is what keeps you signed in between visits. It is managed by Supabase Auth.
• A small preferences entry holding your board theme and accent color, so the page can paint in the right colors before anything finishes loading.

Clearing your site data signs you out and forgets your theme. Nothing else is lost, because your board lives in the database rather than in your browser.

8. How long we keep things

For as long as your account is open. If you cancel and never come back, your board data stays where it is until you ask us to delete it, or until we close accounts that have gone unused for a long time, which we would email you about before doing.

Stripe keeps its own record of payments for as long as tax and accounting law requires. That record is outside our control and deleting your account here does not erase it there.

9. Deleting your account

Email build@frontpagelabs.com from the address on the account and ask. Deletion removes your sign-in record, your settings, every job on your board, your support tickets, and your resume file. We aim to finish within 30 days and it is usually the same day.

Canceling your subscription and deleting your data are separate actions on purpose. Canceling on the account page stops the billing and leaves your board intact in case you come back. If you want both, say so and you get both.

10. Your rights

You can ask for a copy of what we hold about you, ask for something to be corrected, or ask for the whole account to be deleted. There is no charge and it will never affect your price or your service.

Most of it is already in front of you. Your board is the job data, the account page holds your subscription and your setup answers, and the resume page holds your resume.

If you are in California

We do not sell or share personal information in the sense the CCPA uses those words, and we have no financial incentive program, so there is nothing to opt out of. Your rights of access, correction, and deletion are handled by the same email address.

If you are in the EU or the UK

The legal basis for handling your data is that we need it to provide the service you signed up for. You can object, ask us to restrict what we do, or ask for your data in a portable form, and the same email address is the way to do it.

11. Age

The service is for adults. You need to be at least 18 to sign up, because it involves a paid subscription. We do not knowingly collect anything from anybody younger, and if we find out that we have, we delete it.

12. Changes to this policy

When this policy changes, the date at the top of the page changes with it. If a change actually matters to you, for example a new company handling your data, everyone with an account gets an email before it takes effect rather than after.

13. Contact

Write to build@frontpagelabs.com with anything at all about your data. It reaches a person, and that person built this.