Who we are
ephm studio is a software studio run by Michel Camarillo. In this policy, “we” and “us” mean ephm studio. We decide how the personal data described here is used. For any privacy question or request, write to michel@ephm.dev.
This website
- No cookies. The website sets no cookies.
- Analytics. When analytics is switched on, we use Umami, a cookieless analytics service. It counts page views and a few clicks, such as which example you opened or that you sent the contact form, and shows them to us as totals. We do not use it to build profiles of individual visitors. The client portal and the operator app do not load it.
- Contact form. The form has no server behind it. When you press send, it opens your own email app with a pre-filled message; the page itself stores and sends nothing. If you send that email, we receive it like any other email and use it only to reply to you about your project.
- Demos. The examples under
/work/are concept demos for fictional businesses. Some remember your choices in your own browser (for example, a demo shopping cart); that stays in your browser and is never sent to us. - Hosting. The website is hosted by Netlify. Like any web server, it receives technical data with each request, such as your IP address, your browser and the page you asked for, and keeps it in its logs to deliver the site and protect it from abuse.
Client portal
Our clients get a private portal link (an address under ephm.dev/c/) to send us requests and bug reports and to follow their progress. The operator app at /admin is where we, and only we, work on them.
What we store
- The title and description of each request, and any screenshots (PNG, JPEG, WebP) or screen recordings (MP4, WebM, MOV) attached to it.
- The client’s name and a contact email address, which we enter ourselves.
- The status of each request and links to the code changes made for it.
- For the portal link itself, only a one-way fingerprint (a hash), not the link.
- To stop floods of requests, a one-way hash of the sender’s IP address. These records are deleted automatically after two days.
This is stored with Supabase, in a database and a private file store that only our signed-in operators can read.
How requests are processed
The text of each new request (not its attachments) goes through two AI services before we plan the work:
- Jev, by Typesafe, checks the text for unsafe content, works out which of the client’s projects it belongs to, and checks it against the agreed scope of that project.
- Claude, by Anthropic, summarises it into a short work brief.
We read every request ourselves. On projects where we have switched automation on, a small request that passes these checks may be handed to AI coding agents (Claude Code, by Anthropic) that we run on our own computer. They receive the request’s text, its brief and links to its attachments that expire after at most seven days, and they propose changes to the client’s code as pull requests. Nothing ships until we have reviewed and merged it.
Reports and sign-in
- When a request is done, we may email the client a short report through Resend, an email delivery service. We may ask Claude to improve the wording of that email before we send it.
- Operators sign in to
/adminwith a one-time link sent by email through Supabase Auth. The sign-in session is kept in that browser’s local storage.
How long we keep it
We keep requests and their attachments for as long as we work with the client and need them for the project’s records. A client can ask us at any time to delete them by writing to michel@ephm.dev. Please do not put passwords, payment card numbers or other people’s personal data in a request.
Odin and Google user data
Odin is a personal assistant for Windows, built by ephm studio. It runs on the user’s own computer, where it reads and organises things on the user’s behalf when asked, by voice or in writing. Today its only user is ephm studio’s owner, who connects his own personal and work Google accounts; it is not offered to the public. This section describes how Odin accesses, uses, stores and shares Google user data.
What Odin asks Google for
When a Google account is connected, Google’s consent page asks the user to allow the access below. Odin’s tools do less than some of these permissions allow, as noted.
- Gmail
gmail.modify - Read, search and organise email. Odin uses it to search and read messages, list labels, and add or remove labels, which includes archiving. Odin does not send, draft or delete email.
- Gmail settings
gmail.settings.basic - View and manage basic mail settings such as filters. Odin does not change mail settings today.
- Google Calendar
calendar - See and manage calendars and events. Odin only reads: it lists calendars and lists and searches events. It does not create, change, delete or answer events.
- Google Drive
drive,drive.readonly,drive.file - Find, read and create files in Drive. Odin needs to search the whole Drive to find a document it did not create. It does not delete, trash, share, move, rename, upload or download files, or change who can see them.
- Google Docs, Sheets and Slides
documents,spreadsheets,presentations - Read documents, spreadsheets and presentations; create new ones; add text to a document; and write cells in a spreadsheet.
How Odin uses it
- Google user data is used only to provide the features the signed-in user asks for: for example, to say what is on the calendar tomorrow, find an email, sort the inbox, or read a document and draft a summary.
- It is not sold, not used for advertising, and not used to train or improve AI or machine-learning models, ours or anyone else’s.
- No person reads it other than the user, except where we must for security reasons or to comply with the law, or with the user’s explicit permission.
Where it is stored
- The sign-in tokens Google issues are stored in files on the user’s own device. Odin has no server of its own, so they are never sent to ephm studio, and Odin’s AI agent is blocked from reading them.
- Odin fetches Google data from Google when a feature needs it, through connector programs that run on the device and talk to Google directly. What Odin says or shows in reply is kept in its conversation history on the device, and in the user’s notes on the device only when the user asks for that.
When it leaves the device
Google user data leaves the user’s device only to answer the user’s own request, and only the part that request needs:
- Anthropic (Claude). When the user asks something that needs Google data, the relevant content, such as an email’s text or a list of events, is sent to Anthropic’s Claude model to produce the answer. Odin uses Anthropic’s commercial API, under whose terms Anthropic does not train its models on this content.
- Typesafe (Jev). When the user asks Odin to sort the inbox, the sender, subject and preview line of the messages being sorted are sent to Jev, Typesafe’s decision model, to judge which are important, which label fits and which can be archived.
- Fish Audio. If spoken replies through Fish Audio are switched on, the sentence Odin is about to say, which can include details from email or the calendar, is sent to Fish Audio to turn it into speech. Listening and transcription stay on the device.
- WhatsApp (Meta). If the user has connected their own WhatsApp number, answers to questions sent from that number travel back through Meta’s WhatsApp service and can include details from email or the calendar.
ephm studio’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Removing access
The user can remove Odin’s access to a Google account at any time at myaccount.google.com/permissions. Odin then cannot read that account’s data. To delete what Odin keeps on the device, delete Odin’s data on that device, or write to michel@ephm.dev and we will explain how.
Service providers
We do not sell personal data. We share it only with the services that do the work described above, and only what each one needs:
- Netlify: website hosting.
- Umami: cookieless website analytics, when switched on.
- Supabase: database, file storage and operator sign-in for the client portal.
- Typesafe (Jev): screening and classifying portal requests; sorting email in Odin.
- Anthropic (Claude): briefs, report wording and coding agents for the portal; answers in Odin.
- Resend: delivering report emails to clients.
- Fish Audio and Meta (WhatsApp): only in Odin, only when those features are switched on.
Some of these services process data outside your country, including in the United States.
Your rights
You can ask us to tell you what personal data we hold about you, to correct it, to delete it, or to stop using it. Write to michel@ephm.dev; we may need to confirm who you are before we act. You can also complain to the data protection authority where you live.
Changes
If we change how we handle personal data, we will update this page and the date at the top. Significant changes will be described here.
Contact
ephm studio (Michel Camarillo), michel@ephm.dev.