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:
- video of the one checked tab you choose for video;
- your microphone narration, if you allow microphone access;
- clicks and bounded network activity from the checked tabs only, used as evidence of the steps you took.
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
- Your account: name and email address, including your Google profile basics if you sign in with Google.
- Your workspace: members, recordings, workflow drafts and versions, runs, and report deliveries with their approvals.
- Connected accounts: which accounts are connected and their permissions. Access tokens are held by our authorization provider, not in the Runfolk database.
- Trial access, if the paid trial is enabled: payment status and usage counts. Card details are handled by our payment provider.
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
- Google: sign-in and the Gemini API for recording interpretation.
- Nango: authorizing and holding access to the accounts you connect.
- Stripe: payments, when the paid trial is enabled.
- A browser infrastructure provider: browser accounts you create for sign-in.
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
- Delete a recording from its page in Runfolk.
- Revoke a recorder pairing or a connected account at any time.
- Remove the extension from Chrome to stop all recording.
- Ask us to delete your account and workspace data through alphbase.com.
Changes
We will update this page when our practices change and revise the date above.