Legal

Privacy policy

What rikerweb.com collects, what this browser stores, who else touches it, and what we don't do with it. The terms of service cover using the site. This page covers the information.

22 October 2026 · RikerWeb, LLC

No tracker. The cookie section is the whole list.

Who we are

RikerWeb, LLC is a Colorado limited liability company. Nicola Riker Urdaneta and Brian Williams run it. This policy covers the public site, the contact form, the scoping checklist, the blog subscription, sign-in, and the client workspace. Questions go to hello@rikerweb.com.

What we collect

  • An inquiry. Name, company, email, what you need, a budget range, and the note you write. If you arrived from a link that named a source, we keep that too. The form has a hidden field named "website". If that field is filled in, we treat the submission as automated and drop it. We don't email it, and we don't keep it.
  • A checklist. Your email, and a first name if you type one. We send the checklist once. The same hidden "website" field applies: if it is filled in, we drop the request and do not store it. A real address is kept on a Resend list named checklist so we know who asked. That list is not a newsletter, and asking does not start a sequence.
  • A blog subscription. Your email, and the post you subscribed from. It is kept so Nicola can send a note when a new post goes up. That mail is not running yet. The same hidden "website" field applies: if it is filled in, we drop the request and do not store it. Subscribing twice looks the same as subscribing once, and nothing is sent to confirm it.
  • A sign-in. The email address on the account, and a password if you use email. A new email account also needs a six-digit code. The code expires in one hour. If you sign in with Google or Discord, we receive the email on that account and, when the provider sends it, your name. We use those to check who can open the workspace and to keep that session. We never receive your Google or Discord password. The email password is stored by the auth service. We can't read it back.
  • A workspace record. When the studio opens an engagement, we store the client's name, email, and company; the engagement title, phase, summary, and staging link; deliverables and due dates; invoices (number, amount, dates, status, and a short memo); and project notes, with the email of whoever wrote the note. The sample page at /workspace/example is not one of these records. It is built into the page.
  • A card payment, if an invoice offers one. Stripe processes the card on Stripe's page. We keep the amount, the status, and Stripe's reference. We do not keep the card number.

Cookies and this browser

This site does not set an analytics cookie, an advertising cookie, or anything that follows you onto other sites. There is nothing optional to accept or refuse, so there is no consent banner. What this browser stores is all required for something you asked the site to do. Fonts are files on this site. Opening a page does not send your IP address to a font host, an analytics service, or an ad network.

  • Theme. If you pick light or dark, that choice stays in local storage on this device. We don't send it to a server. Leave it unset and the site follows your system setting, which is not stored.
  • The cookie note. Dismissing the note at the top of a public page stores that you dismissed it, on this device, so it does not keep coming back.
  • Sign-in. A session stays in local storage until you sign out or it expires. When the auth service isn't configured, a demo sign-in keeps the invited email in session storage until the tab closes.

Clearing this site's data in the browser removes the theme, the dismissed note, and any local session.

What we don't do

We don't run analytics, advertising, a newsletter, or a chat widget. The checklist is one email. We don't follow it with a drip sequence. A blog subscription is a note when a post goes up, nothing more, and that note is not being sent yet. We don't sell personal information, we don't share it for advertising, and we don't buy it. Google or Discord account data is used to recognize an invited sign-in. We don't use it to advertise, and we don't pass it to a data broker.

Who else handles it

  • Resend delivers an inquiry as email to hello@rikerweb.com, from noreply@rikerweb.com, with your address as the reply-to. It also sends the checklist to the address you gave, stores that address on the checklist list, sends the studio a one-line notice, and sends the six-digit sign-in code. Resend keeps a record of those sent messages as part of the service. If inquiry email isn't configured, the contact form opens a draft in your own mail app instead, and nothing is sent until you send it.
  • Supabase stores the sign-in account and session, blog subscription addresses, and workspace records. Google or Discord shows its own sign-in screen when you choose it, then hands Supabase the account email and name.
  • Stripe collects the card when an invoice is paid that way. The card number stays with Stripe.
  • Cal.com is where a scoping call is booked. That link leaves this site. What you type there is handled by Cal.com.
  • Vercel hosts the site. Like any host, it keeps request logs (IP address, path, and time) to run and protect it, including limiting repeated form submissions.

An address that isn't on the invite list is signed out. We don't open the workspace for it. Supabase may still have a record of the sign-in attempt. The site is operated from the United States. The companies above process this information there.

How long it stays

Inquiry mail stays in the studio inbox until we delete it, the same as any other project email. A checklist address stays in Resend until you ask us to delete it, or we delete it. A blog subscription stays until you ask us to remove it, or we do. A sign-in session lasts until you sign out, it expires, or we take the address off the invite list. Taking it off the list ends the session the next time the site checks. Workspace records stay for the engagement. Invoice amounts and payment status stay with the studio's books. The theme choice and the dismissed cookie note stay in this browser until you clear the site's data.

Why we keep it

We keep an inquiry, a checklist request, and a subscription because you asked for the reply, the checklist, or the note. We keep a sign-in and the workspace records to run the engagement you were invited to. We keep host logs to run and protect the site. A signed brief may require us to keep project email and invoice records after the work is done.

Asking us about it

Email hello@rikerweb.com to ask what we have, to correct it, or to ask us to delete an inquiry, a checklist address, a subscription, a workspace record, or a sign-in. Signing out of the workspace ends the session in that browser. Clearing this site's data removes the theme choice, the cookie note, and any local session.

Children

This site is for people hiring a studio. We don't knowingly collect personal information from anyone under 16. If you think we have, email us and we will delete it.

Changes

When this policy changes, the date at the top changes with it. A signed project brief is a separate document. It does not move because this page did.