Folio privacy policy

Effective date: September 26, 2026.

Who operates Folio

Folio is operated by Donald Noah Ruffin. Contact foliostudyapp@gmail.com for support or privacy questions.

What Folio reads

Folio uses Chrome to read supported school and publisher pages you can access. Captured information can include course/account identifiers, assignments, deadlines, grades and completion evidence, documents, readings, captions, page titles and URLs, ordinary form entries, links, resource URLs and page/control markup. Course pages may contain personal information, including names, contact details and text you entered in forms.

You sign in on the school's or publisher's own website. Authenticated requests use the browser's existing session. Folio does not provide a separate school-password entry form. The corrected capture pipeline removes password fields and recognized authentication secrets from captured markup and structured content before saving them. It preserves academic identifiers needed for course discovery. Internal job authorization secrets are used transiently; saved routing records do not contain their bearer values. Tests cover supported formats and synthetic credentials; this is not a guarantee that arbitrary course text can never contain sensitive information. Earlier saved copies are not automatically rewritten by this correction.

Local storage

Folio keeps captured evidence and derived coursework in a workspace on your Mac, with separate settings, recovery/update records and service logs. Chrome stores extension setup/job state in its profile. Study progress and usage metadata may be stored locally. Recent teaching conversation is also held in helper memory; it is not a promise of durable chat history.

Folio does not add its own at-rest encryption to these files. Your device security and any backup/synchronization software you use affect access to local copies.

External requests and AI

Connecting courses sends requests to the school, publishers, and relevant content/media hosts. Folio may retrieve supported Kaltura and YouTube metadata/captions. Those services receive network request information and apply their own policies.

When you request optional AI teaching or learning feedback, Folio sends relevant course context, your question or practice response, and applicable recent conversation/learning inputs to OpenAI over HTTPS. Returned explanations or feedback are processed locally. Course excerpts can include personal information. Only use material you are permitted to process this way.

The inspected teaching and learning requests use store:false. That setting is not a promise that OpenAI retains nothing. Provider retention and account-specific controls are described in OpenAI's API data controls. Folio does not claim a zero-retention arrangement. This beta does not include an AI subscription or finished self-service AI setup.

Diagnostics and support

Export diagnostics creates a local download containing version/time/status/count information and limited connection/error codes. Its current builder does not include course titles/text, source URLs, account IDs or API keys. It does not automatically send the file to support. Review it before sending.

Raw evidence and service logs are different and can contain sensitive information. Do not send them, passwords, API keys or private screenshots by email. If you contact support, we receive your email address, message and attachments you choose to provide. Support emails and attachments are retained only as long as needed to provide support. After a support issue is resolved, related emails and attachments may be retained for up to 90 days and are then deleted. If a user requests deletion sooner, Folio will honor the request within 30 days. Folio may retain only the minimum information necessary for longer if required for security, fraud prevention, legal obligations, or an active dispute. Contact the email above for a support-record deletion request.

Retention and deletion

Saved coursework does not have a promised automatic expiry. Removing the app or extension does not erase the helper's saved coursework. Use the app's Remove Folio control to stop/remove the background service before moving the app to Trash.

Erase local coursework requires the displayed exact confirmation and removes the active Data directory. It does not delete school records, settings, logs, update/recovery copies, original imported folders, exports, separate backups, browser sessions or separately configured AI credentials. Those copies require separate handling. Third-party services control their own retained copies.

Purpose and limits

The operator has confirmed that Folio data will not be sold or used for advertising. Folio data will not be used to determine creditworthiness or for lending purposes. The reviewed extension does not request Chrome's cookies or browsing-history APIs, but it reads relevant tab URLs and uses existing sessions for authenticated requests. There is no separate payment, health or location collection feature identified in the reviewed application; such information can still appear incidentally in course pages or user-entered text. We therefore do not claim that Folio never handles those categories.

Complete graded work and submissions on your school's or publisher's original website. Folio's source navigation is not a guarantee about a publisher's page behavior. Changes to Folio's data practices must be reflected in this policy and the product disclosure before publication of those changes.