Privacy Policy

This policy explains what information Ulric collects, how it is used, and the choices you have. Ulric is the independent software studio of Eric Richers, based in Eugene, Oregon. In this policy, "I", "me", and "Ulric" mean the studio; "you" means the person visiting a site I run or booking a call with me.

Effective July 22, 2026.

The short version

I build custom websites and the scheduling, content, and assistant tools behind them. When you book a time through one of those tools, I read only when your calendar is busy so the times I offer are honest, and I create the single event for your booking. I do not sell your information, I do not use it for advertising, and I do not share it beyond what it takes to deliver the service you asked for.

Information I collect

  • Things you send me. When you fill in a contact form, book a consultation, or write to the site assistant, I receive what you provide: usually your name, email address, and your message. A booking also records the time you chose.
  • Basic technical data. Like most websites, my servers keep short-lived logs (IP address, browser type, timestamps) to keep the site running and to guard against abuse.
  • Calendar data, only if you connect a calendar. The scheduling tool is used by the business owner, not by visitors. If a business owner connects a Google or Microsoft calendar, I access the data described in the next section.

Google user data

When a business owner connects a Google account to the scheduler, Ulric requests a narrow set of permissions and uses them only to make booking work:

  • Free/busy times (calendar.freebusy): I read when you are busy so I never offer a time that is already taken. I do not read the titles, guests, or details of your events.
  • Events (calendar.events): I create the one event for a confirmed booking, add a video meeting link, invite the guest, and delete that event if the booking is cancelled.
  • Calendar list (calendar.calendarlist.readonly): I read the names of your calendars so you can choose which one receives bookings and which ones block your availability.
  • Email address (openid, email): I show which account is connected.

Ulric's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google calendar data is used only to provide and improve the scheduling feature you turned on. It is never sold, never used for advertising, and never transferred to others except as needed to run the service (for example, sending your booking to Google to place the event on your calendar), to comply with the law, or with your consent.

Microsoft Outlook data

If you connect a Microsoft account instead, the same principles apply through the Microsoft Graph API: I read your free/busy schedule to keep offered times honest and create or cancel the single event for a booking, using the Calendars.ReadWrite permission and nothing more.

How connection data is stored and secured

Calendar connections use OAuth, the standard that lets you grant access without ever giving me your password. The access and refresh tokens are stored on the server that runs your site, are used only to perform the actions above, and are transmitted over encrypted connections. Access to the server is limited to me.

Keeping and deleting data

You stay in control. Disconnecting a calendar in the dashboard revokes Ulric's access at the provider and deletes the stored tokens. Booking records and contact messages are kept only as long as needed to run the business they belong to, and you can ask me to delete them at any time. To request deletion of any information I hold about you, email [email protected] and I will handle it promptly.

Who else is involved

I keep the list of outside services short and name them plainly: Google and Microsoft (only when you connect their calendars), a web host that runs the servers, and an email provider that delivers booking confirmations. Each handles data only to provide its part of the service. I do not sell data to anyone, and I do not use it to build advertising profiles.

Cookies

The sites I run use a small number of cookies to keep you signed in to a dashboard and to remember basic preferences. They are not used to track you across other websites.

Children

My services are meant for businesses and adults. They are not directed to children under 13, and I do not knowingly collect information from them.

Changes to this policy

If this policy changes in a meaningful way, I will update the date at the top and, where appropriate, note the change. Continued use of the service after an update means you accept the revised policy.

Contact

Questions about privacy, or a request to see or delete your data, go to Eric Richers at [email protected], Ulric, Eugene, Oregon, United States.

From the lab

The product lines behind the studio.

Frida

The lightning-fast CMS + CRM builder. Ferocious, independent, zero dependencies. Like her namesake, she hunts alone.

Meet Frida →

Pippin

The agentic harness builder. Sweet, nurturing, and quietly everywhere. Custom agent flows your team can actually trust.

Meet Pippin →

Composer

Branded reels and posts, made fast. The studio's own social composer.

Meet Composer →

Composer for iOS

The native app. On-device reels and posts, built for one thumb.

Meet Composer for iOS →

The chat lab

Talk to the open models I build on. Switch between them mid-conversation.

Meet The chat lab →