Runfolk

Privacy

Last updated 24 September 2026

This policy covers the hosted Runfolk service and the Runfolk Chrome extension, both made by Alphbase. Operators who self-host Runfolk are responsible for their own installations.

What the recorder collects

The recorder collects nothing until you open it, check the tabs for a task and press Start recording. While recording, it captures:

Before evidence is kept, the recorder removes known secret fields such as passwords and tokens from captured addresses, headers and structured data. This filtering cannot remove secrets that appear in the video, in your narration or in free text, so pause before entering credentials. Chrome shows a notice that the recorder is debugging the browser while network evidence is captured.

When you stop, the recording is uploaded only to the Runfolk workspace you paired the recorder with. Until the upload succeeds it stays in your browser so it can be retried; you can discard it at any time.

What the Runfolk service stores

How we use it

We use your data only to provide Runfolk: to build review-only workflow drafts from your recordings, run the workflow versions your workspace approves, and deliver messages your workspace owner approves. Recordings, narration and evidence are sent to Google's Gemini API to interpret the task. We do not sell your data, use it for advertising, or use it to determine creditworthiness.

The use of information received through the Runfolk Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Service providers

Retention and security

Uploaded recordings are encrypted at rest and scheduled for deletion seven days after upload. You can delete a recording sooner from its page. Other workspace data is kept while your workspace is active.

Your choices

Changes

We will update this page when our practices change and revise the date above.