privacy

who we are

maioka is the studio of Ken Dowling, a film director and editor based in San Francisco, California, USA. On this page, “maioka”, “we” and “us” mean Ken.

Questions or requests about anything here: hello@maioka.co.

this website

maioka.co is a portfolio. There are no accounts, no sign-ups, no forms and no comments. We do not use cookies, analytics, advertising or tracking of any kind.

Your browser keeps three small settings for this site, on your device only. We never receive them:

• maioka:theme (local storage): whether you chose light or dark mode.
• maioka:ring (local storage): where you left the sliders on the home page (corners, size, motion).
• maioka:titlecard (session storage): that the opening title card has already played on this visit. It is cleared when you close the tab.

You can clear them at any time in your browser’s settings. The site works the same without them.

The site is hosted by Vercel, and the films are streamed through Cloudflare (from maioka-media.reachmaioka.workers.dev). Like any web server, these providers process standard technical information, such as your IP address, browser type, the page or file requested and the time, in order to deliver and protect the site, and may keep it in their standard server logs. We do not use it to identify or profile visitors.

The fonts, the animation library and the video player are served from maioka.co itself. No third-party fonts, scripts or embeds are loaded.

Links to Instagram and to email take you off the site, where those services’ own policies apply. If you email us, we use your message only to reply to you.

maioka Outbound and Google user data

maioka Outbound is a private tool used only by Ken to manage his own business email, on his two accounts: hello@maioka.co and reachmaioka@gmail.com. It is not offered to the public, and no one else can sign in to it.

what it accesses

It asks Google for two permissions on Ken’s two accounts:

• gmail.readonly: to read the email threads in Ken’s mailboxes (senders, recipients, subject lines, dates, message text and attachments).
• gmail.compose: to create and update draft emails in Ken’s Gmail, and to send a single draft when Ken presses Send on it himself. The tool never sends anything on its own.

how it uses that data

• To see which of Ken’s outreach emails have had replies, and keep track of each conversation.
• To find contact details of people Ken already corresponds with.
• To learn Ken’s writing style from his own sent emails (stored in redacted form), so drafts sound like him.
• To read contracts and deal terms sent to Ken by email and flag points for him to review.
• To give Ken a summary of activity.
• To prepare draft replies and save them in Ken’s Gmail, where (or in the tool’s dashboard) he reviews, edits and sends each one himself.

It never sends email automatically. Every email is sent by Ken, by hand.

where it runs, where it is stored and who processes it

The tool runs on demand on Ken’s own computer, through Anthropic’s Claude Code. Google user data is handled only by these service providers:

• Google: Gmail itself, where the email lives.
• Supabase: the tool’s private database and file storage, in the United States, which only Ken can access.
• Anthropic: Claude, which processes message content to draft text.
• Our web host for Ken’s private dashboard (Vercel or Cloudflare), which shows Ken his drafts and threads after he signs in.

what we never do with it

• We do not sell it.
• We do not share it with anyone, except the service providers listed above, and only to run the tool.
• We do not use it for advertising.
• We do not use it to train generalized AI or machine-learning models.

keeping and deleting it

• Conversation data is deleted once a conversation has ended and no follow-up is due.
• Writing-style samples and contract reviews are kept until Ken deletes them.
• Opt-out addresses are kept for as long as needed to honour the opt-out.

Access can be revoked at any time at myaccount.google.com/permissions. Revoking access stops all new reading and drafting; data already stored is deleted on request to hello@maioka.co.

google api services user data policy

maioka Outbound'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.

people ken contacts about work

Ken sends business emails about creative work to people at brands, agencies and production companies, and to creators and artists or their teams. To do that he uses contact details (such as name, job title, company and work email address) found in:

• public company websites, press pages and credits pages;
• public Instagram and YouTube profiles, through their official APIs;
• the Meta Ad Library;
• Hunter.io;
• LinkedIn profiles that Ken looks up himself;
• Ken’s own past email correspondence.

He also keeps the emails exchanged.

• Every first-contact email includes a way to opt out.
• Opt-outs are honoured: your address and company are added to a suppression list so you are not contacted again.
• You can ask what we hold about you, or ask us to delete it, at hello@maioka.co.

california residents

If you live in California, you have the right to know what personal information we hold about you and how we use it, and the right to ask us to delete it. Email hello@maioka.co; we may ask you to confirm the request from the address concerned. We will not treat you differently for asking.

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

children

This site and our tools are not directed at children under 13, and we do not knowingly collect their information. If you believe we have, email us and we will delete it.

changes

If this policy changes, we will update this page and its effective date.

contact

maioka (Ken Dowling), San Francisco, California, USA
hello@maioka.co

effective 14 october 2026