Privacy Policy
Last updated: March 31, 2026
Overview
Lapo is a private, single-user personal automation application. It is not a public service. This policy describes how Lapo handles data accessed through Google APIs and other services.
Who uses this application
Lapo is authorized and used exclusively by one individual: Evan Ruff. No other users have access to this application or the data it processes.
What data is accessed
Lapo accesses the following data through the Google API on behalf of the authorized user:
- Gmail messages — to triage, summarize, and draft email responses
- Google Calendar events — to provide scheduling assistance and reminders
- Google Drive files — to read and organize personal documents
How data is used
All accessed data is used solely to automate personal tasks for the authorized user. Specifically:
- Email content is read to generate summaries and draft replies; it is not stored permanently beyond session context
- Calendar data is read to surface upcoming events and assist with scheduling
- No data is analyzed for advertising, profiling, or any commercial purpose
Data sharing
Lapo does not share, sell, rent, or transmit any personal data to third parties. Data accessed from Google APIs is not used to train AI models or shared with any external service beyond what is necessary to execute the user's explicit requests.
Data storage
Lapo stores minimal data locally on the user's private Mac Mini. No personal data is stored in third-party cloud databases. Authentication tokens are stored locally in an encrypted credential vault (1Password) accessible only to the authorized user.
Google API Limited Use disclosure
Lapo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data obtained via Google APIs is used only to provide the functionality described in this policy and is not transferred to others, used for advertising, or used for purposes unrelated to the user's personal task automation.
Security
Access tokens and credentials are stored in an encrypted local vault. The application runs on a private, access-controlled machine. No data is exposed publicly.
Contact
Questions about this privacy policy can be directed to: evan.ruff@gmail.com