Privacy

FacultaStudio is a research project about what AI-related job postings ask for. It is not an advertising business, and it holds almost no personal data. This page says exactly what it does hold.

Last updated 26 September 2026.

Who is responsible

FacultaStudio is operated by Mark Keith. For any question about this policy, or to exercise any right described below, contact privacy@facultastudio.com.

What we collect

If you sign in

Signing in is only for faculty maintaining a program page. We collect your email address and an account identifier, handled by Supabase Auth. We use a one-time sign-in link, so there is no password to store. We do not collect your name, title, department, phone number or photograph.

What a program submits

Job titles, employer names, optional notes and questions submitted through My program, together with the account that submitted them and a timestamp. These are statements about a program and its graduates in aggregate. They are not, and must not be, statements about identifiable individuals.

Job postings collected from public sources

Job advertisements retrieved from public APIs and feeds, listed on the research page. This is third-party content written by employers. It occasionally contains personal data an employer chose to publish, such as a named hiring contact. We do not seek that data, do not index it, and never publish posting text: the site publishes only counts and percentages computed across many postings.

Placement figures

Employer-level placement counts transcribed from documents institutions have already published. These are counts of graduates per employer per year. They contain no names.

Server logs

Our hosting and database providers keep standard operational logs, which can include IP address, user agent and request time. We use these only to keep the service running and secure. We also keep our own request log, described under How we measure the site.

What we do not do

• No third-party analytics or tracking. There is no analytics package, tag manager, pixel, session recorder or third-party script anywhere on this site. What we do measure is described under How we measure the site, and all of it is our own code, writing to our own database.
• No advertising, and no profiling for advertising.
• No sale or sharing of personal information, as those terms are defined under California law. We have never done so and have no mechanism to.
• No automated decisions producing legal or similarly significant effects about any person.
• No special category data — no health, biometric, genetic, religious, political or sexual-orientation data.

How we measure the site

This changed on 26 September 2026. Until then the detailed measurement was off unless you turned it on, and a banner asked. It is now on for everyone, and there is no banner, because it no longer stores anything on your device: no cookie, no local storage, no identifier of any kind. Everything below is worked out on our server from the requests your browser already makes.

What is recorded

Every request our server answers: the time, the page asked for (without whatever follows a question mark in the address), the method, the site that sent you (its name only, not the full address), whether the request looked like a person’s browser, a crawler or an automated browser, and a keyed hash of your IP address. This is the security log. It is how we notice and block someone probing the site for weaknesses or flooding it, so it is kept for every visitor, including anyone who opts out below.

What you do on a page, reported by a small script of our own: which pages you read and how long for, how far you scroll, what you click (the visible text of the link or button, up to 100 characters, and where it goes), files you download, links you follow to other sites, the filters and views you choose on a page, the length (never the content) of text you copy, script errors you run into, and whether you begin a form, send it or leave it. What you type into a form is never recorded. Filter choices are recorded as the options you picked; anything in the address that could carry a sign-in code, token or email address is removed first.

About each visit: the page you arrived on, the referring site, your browser, operating system, device type, screen size and language, and an approximate location (country, region, city) that our host, Vercel, derives from your IP address and hands over with the request. Your IP address is not sent to any lookup service and is never stored as itself.

How a visit is grouped without a cookie

Requests are grouped into a visit by a hash of your IP address and browser string, mixed with a random value that is replaced at midnight (Mountain time) every day and then deleted. Once it is gone, that day’s visit hashes cannot be linked to anything, so this hash cannot follow you from one day to the next. A visit ends after 30 minutes without activity.

The security log’s keyed hash of your IP address does not change from day to day, because blocking an address has to outlast a day. For 30 days, then, two visits from the same IP address can be matched to each other. It cannot be turned back into the address. After 30 days it is deleted, along with the full browser string, and what remains of a visit cannot be matched to any other.

None of this is tied to your FacultaStudio account. If you sign in, your account is never attached to these records, and nothing about your coding work or your program travels with them.

Bots, threats and blocking

Every few minutes each recent visit is scored for how likely it is to be a bot and how likely it is to be an attack, from the request pattern and whether a script ran. An address that probes for known weaknesses, or sends far more requests than a person could, may be refused for a period; so may one an administrator blocks by hand. Sign-in stays reachable while an address is blocked. Because many people can share one address (a campus network, a phone carrier), a block can affect people behind it who did nothing; if that happens to you, write to the address below.

Anonymous page counts

Separately, since 22 September 2026 our server adds one to a daily tally each time a page is requested: which page, which filters were showing (the geography and quadrant on the overview), which panel, and whether the request looked like a person’s browser, a crawler or an automated browser. That tally holds no IP address or hash of one, no browser details and no location, and cannot be tied to you or to any visit. It is kept for good.

Turning it off

Use Analytics opt-out in the footer. It stops the page script from reporting anything from this browser, and it is the one thing we ever keep on your device: a note, in this browser’s own storage, that you asked, which the script reads and never sends anywhere. If your browser sends a Global Privacy Control signal we treat it the same way, with nothing stored. Either way the security log above still records requests, for the reason given there.

Cookies. The only cookie this site sets is the session cookie when you sign in. Signing out clears it. Nothing here is sold, shared with advertisers, or handed to a data broker or aggregator, and there is no advertising technology on this site at all.

Why we are allowed to hold it

For readers in the UK, EU and other jurisdictions applying similar rules, our lawful bases are: contract, to give you the account you asked for; legitimate interests, to run and secure the service and to conduct academic research in the public interest, balanced against your rights; and public-interest research for the aggregate analyses themselves, which are published only in suppressed, aggregated form.

Who else processes it

Vercel (hosting and delivery) and Supabase (database and authentication). Both act as processors on our instructions. We do not pass your data to anyone else, and there are no other recipients.

Where it goes

Our infrastructure is hosted in the United States. If you access the service from outside the United States, your data is transferred there. Where transfer safeguards are required, they are provided through our providers’ standard contractual clauses.

How long we keep it

• Account data: until you ask us to delete it, or until the account has been unused for two years.
• Program submissions: until the program withdraws them. A program can edit or remove its own entries at any time from My program.
• Job postings and placement figures: retained indefinitely as a research corpus. This is the point of the project — a panel that cannot be looked at over time cannot answer questions about change over time.
• Server logs: per our providers’ retention, typically weeks rather than months.
• Our request log: 30 days.
• Visits and what was done on a page: 400 days. The full browser string and the keyed hash of the IP address are cleared from a visit after 30 days.
• The daily grouping value: deleted when its day ends.
• Blocks: 90 days after the block ends.
• Anonymous page counts: indefinitely.
• Never kept at all: your IP address itself, your account identifier alongside any of the above, cookies other than the sign-in session, what you type into forms, and the part of a page address after the question mark (apart from the filter choices described above, with anything private removed).

Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict or object to our processing of your personal data, to receive it in a portable form, and to withdraw consent where we rely on it. California residents may request the categories and specific pieces of information collected, request deletion or correction, and are entitled not to be discriminated against for exercising those rights. We do not sell or share personal information, so there is no opt-out to exercise.

Write to privacy@facultastudio.com. We will not ask you to create an account to make a request. If you are in the UK or EU and are unhappy with our response, you may complain to your national supervisory authority.

If a posting mentions you

If a job advertisement we collected contains your personal data and you want it removed, write to privacy@facultastudio.com with the posting URL. We will remove it from the corpus. We do not need to keep any individual posting for the analysis to hold.

Education records

We are not a school official and we do not receive education records. Nothing in this project constitutes an education record under FERPA, because no student-level data enters it. Where we report placement figures, they come from documents the institution itself has published.

Children

This service is for faculty and adult researchers. It is not directed to children, and we do not knowingly collect data from anyone under 16. If you believe a child has given us data, write to us and we will delete it.

Security

Access to program data is enforced in the database by row-level security, not by the interface: a mistake in a page cannot widen access beyond the policy. The site holds only a publishable, read-only key and can reach only the aggregate schema. Administrative credentials never reach the browser.

Changes

If this policy changes we will update the date above. If a change is significant, and you have an account, we will tell you by email before it takes effect.