Privacy

If you sign in with Google, we receive and store your name, email address, whether Google considers that address verified, and your profile picture URL. We do not receive your Google password and have no access to your Gmail, Drive, or any other Google service — the sign-in requests only the email, profile and openid scopes.

To keep you signed in, we store a session record containing a session token, its expiry, and the IP address and browser user-agent it was created from. Those last two exist so a suspicious session can be identified and revoked. We also store the access and refresh tokens Google issues, which is how sign-in works at all.

What you enter is stored as you write it: project titles, summaries, start dates, course codes, affiliations, sponsors, acknowledgements, tags, resource links, uploaded photos, the names and roles of team members, and any contact email a team chooses to publish.

Team members can be credited by name without ever having an account. If you add a teammate’s email so they can sign in and edit, that address is stored to make the link.

Published projects are public to anyone on the internet, including search engines. That is the point of the archive — it exists to be read by employers, sponsors and future students. Assume anything you publish is permanent and world-readable.

Projects still in draft are visible only to their team and to studio admins. Individual resource links can be marked members-only, in which case signed-in members see them and the public sees a locked row.

A contact email is shown only after a visitor clicks a button; it is not written into the page’s HTML. This stops routine address harvesters, which scrape page source. It does not stop someone determined to collect it by hand. Only publish an address you are willing to have reached.

Your own email address is never shown on a public project page. Studio admins can see the accounts list, including email addresses, because that is what administering the archive requires.

Everything is stored on Cloudflare’s infrastructure — a D1 database for records and an R2 bucket for uploaded photos — under an account controlled by the studio. Fonts are served from this site rather than fetched from Google, so simply reading a page sends no request to a third party.

Cloudflare processes data on our behalf and keeps its own operational logs as any hosting provider does. See Cloudflare’s privacy policy.

One cookie, holding your session token, set when you sign in. It is how the site knows you are you. There are no advertising, analytics or cross-site tracking cookies. Signing out clears it.

Project records are meant to last — a studio archive that forgets defeats its own purpose. Sessions expire on their own. Accounts and their linked Google tokens are kept while the account exists.

If your account is deleted, your name stays on the projects you worked on and your sign-in access ends. That is deliberate: removing a contributor’s credit would falsify the record of who built what. If you want your name removed as well, ask — see below.

You can ask us to show you what we hold about you, correct it, remove your account, or remove your name from a project. You can also revoke this site’s access to your Google account at any time from your Google account permissions, which ends future sign-ins.

Email archive@dit-design-studio.org and say what you would like done.

If this policy changes materially, the date at the top changes with it.