The Flowo Assistant: User-Invoked Cloud Processing
· Maksym Bardakh Ivko
What context an assistant request can use, where it is processed, and which privacy limits still apply.
A request with selected planning context
The assistant can receive context selected from tasks, notes, or a schedule when a user invokes it. Generated text may be incomplete or inaccurate and must be reviewed before use.
What the Assistant Can Do Today
The assistant currently supports contextual queries about your workflow:
- Priority analysis: Ask about your most urgent tasks, and it surfaces what needs attention based on deadlines and importance levels.
- Note retrieval: Search through your Braindump notes by topic or keyword.
- Schedule overview: Get a summary of your day, upcoming deadlines, or free time slots.
- Thinking partner: Discuss priorities, break down complex decisions, or get help structuring a project.
Privacy as a Design Principle
Core planning records are stored in encrypted local storage. An assistant request sends the content needed for that request through the authenticated Flowo API to AWS services named in the Privacy Policy. Flowo does not store a centralized task database, sell planning content, use it for advertising, or use it to train models.
Local-first does not mean every feature is on-device. The policy identifies consent controls, processors, transfer mechanisms, and retention criteria. Voice upload asks for a separate just-in-time choice.
To see how the assistant fits into the broader system alongside auto-scheduling and Braindump, visit our Methodology page or read about how adaptive scheduling works.