Privacy
Privacy Policy
How Sylph handles account information, workspace content, and product usage data.
Last updated July 22, 2026
What this policy covers
Sylph is built as a private personal workspace. Your projects, tasks, notes, reminders, habits, reviews, and community account information are used to provide the product experience you request.
Private workspace content is not intentionally made public unless you use a public sharing feature, such as a shared note link, or post content in Community.
Information Sylph stores
We may collect account details such as your email address, display profile information, authentication records, and product settings.
We store workspace content you create in Sylph, including project data, task records, Canvas positions, notes, reminders, calendar entries, habits, reviews, toolbox preferences, and related activity needed to make the app work.
How information is used
Sylph uses this information to authenticate your account, save your workspace, sync changes across views, provide requested features, improve reliability, prevent abuse, and respond to support requests.
When AI features are used, Sylph may send the relevant context needed to answer your request to the configured AI provider. The app should avoid sending unrelated workspace data.
Service providers
Sylph uses Supabase for authentication and database storage. Additional providers may be used for hosting, email delivery, AI responses, analytics, or operational monitoring.
We do not sell personal workspace content. If future billing or payment features are enabled, payment handling should be managed by a dedicated payment provider rather than storing full card details in Sylph.
Your choices
You are responsible for the content you choose to publish in Community or share through public links.
You can request help with account access, data questions, or deletion requests by contacting support.
Contact
For privacy questions, contact support@sylph.live.
This policy is maintained by Sylph. The governing law and required regional disclosures should be confirmed before final launch in the user's local jurisdiction.