syllabe

Privacy Policy

Last updated 25 October 2026

1. Scope

1.1This Privacy Policy describes how the syllabe application for Android (the "App") and the website at syllabeapp.com (the "Website") handle information.
1.2Use of the App or the Website constitutes acceptance of this Privacy Policy.

2. Summary

2.1The App operates without user accounts, advertising, analytics or tracking.
2.2The developer of syllabe (the "Developer") has no access to content created in the App. Where an optional online feature transmits content, it does so only as set out in Section 9.
2.3The Developer does not sell, rent or share any information relating to users.

3. Information Stored on the Device

3.1Poems, drafts, Vault scraps and settings are stored locally within the App on the user's device.
3.2Photos and voice notes added in the App are stored as files within the App on the device and are not uploaded to any server.
3.3Uninstalling the App causes Android to delete all such information from the device.

4. Android Device Backup

4.1Where Google backup is enabled in the device's Android settings, Android may include the App's text content (poems, scraps and settings) in the device backup to the user's Google account. Photos and voice notes are excluded.
4.2Such backups are operated by Google under Google's own privacy policy and are controlled by the user through the device settings.

5. Google Drive Backup

5.1The App offers an optional backup of text content to the user's own Google Drive. This feature is disabled by default and is enabled only by the user in Settings.
5.2On enabling the feature, the user signs in with Google and grants a single permission, which gives the App access to a hidden application folder in the user's Google Drive. The App cannot view or open any other file in the user's Google Drive.
5.3The App stores one backup file in that folder containing poems, scraps and settings. Passcodes, photos and voice notes are never included.
5.4The App reads the email address of the selected Google account solely to display which account is connected.
5.5The backup is transferred directly from the user's device to the user's Google Drive and does not pass through any server operated by the Developer.
5.6The user may disable the feature at any time and may delete the backup from Google Drive, as set out on the Your Data page.
5.7The App's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

6. Device Permissions

6.1The App requests access to the camera, microphone or photo library only when the user adds a photo or records a voice note. Captured content remains within the App on the device.

7. App Lock and Biometrics

7.1Where a passcode is set, the App stores only a salted hash of the passcode on the device, and never the passcode itself.
7.2Fingerprint and face unlock are handled entirely by Android. The App does not access or store biometric data.

8. Sharing

8.1No content leaves the App unless the user shares or exports it, or uses an online feature set out in Section 9.
8.2Shared cards and exported files are delivered through the Android share sheet to the application selected by the user, whose own privacy policy applies from that point.

9. Online Features

9.1The App offers optional online features that rely on third-party services, including dictionaryapi.dev. Each feature transmits only the information described in this Section, and only when the feature is used. Such services operate under their own privacy policies.
9.2Where a word is not found in the dictionary stored in the App and the device is online, the App sends that single word to dictionaryapi.dev to retrieve its meaning. No other content is sent, and the result is not stored.
9.3When a poem is sealed, the App sends a fingerprint of the poem to public timestamp services. The fingerprint is a code derived from the poem, from which the poem cannot be recovered. The poem itself is not sent.
9.4The QR code on a certificate contains the seal, which is read on the device that scans it. Verifying a seal in the App or on the Website consults public timestamp records using the fingerprint only. The seal is not sent to the Website's server.
9.5Where the user writes a poem with other poets through Co-Write, the poem and its shared scraps are transmitted between the participating devices through a third-party relay service. The content is encrypted on the sending device and can be decrypted only by the participating devices. The relay holds the content in encrypted form only until it is delivered, together with the pen names and icons of the participating poets so that the host can see who asks to join. A shared poem is deleted from the relay when sharing ends, or when it has not been opened for one year.
9.6Where the user links a browser to the App through Link to Web App, content is transmitted between the device and that browser through the same relay service and encrypted in the same manner. The browser keeps the content in memory only. Changes made in the browser while the device is unavailable are kept in that browser in encrypted form until they are delivered. A link ends when it expires or when the user removes it in the App.

10. Children

10.1The App is not directed at children under the age of 13. No personal information is knowingly collected from any user.

11. Changes to This Policy

11.1This Privacy Policy may be updated from time to time. Updates are published on this page with a revised date.
11.2Any change affecting the handling of user data will be notified within the App before it takes effect.

12. Contact

12.1Questions regarding this Privacy Policy may be sent to [email protected].