‹ Studio ES EN DE FR IT PT KO JA ZH
Studio (yoniliman.com/studio) is a writing platform for authors: a literary editor with tools for versions, characters, analysis, publishing for alpha/beta readers, export (EPUB, Word, PDF), an author’s planner, and optional AI assistants.
To use private features you need an account, created with your email or your Google account. You are responsible for keeping access to your email and for activity performed with your session.
The works, notes and materials you create in Studio are your property. Studio acquires no rights over your texts and only stores and processes them to provide the service (for example, version saving, export, or the analyses you request). You can export or delete your works at any time; works can also be encrypted with a key only you know.
AI features (AIGOR) are optional and run only when you invoke them. If you configure your own API key, it is stored encrypted and requests are sent to the provider you choose under their own terms.
If you connect your Google Calendar, Studio uses the access solely to sync your planner: creating your entries in a “Studio” calendar in your account and showing your calendar’s events inside Studio, for your benefit and under your control. You can disconnect the integration at any time from the planner or revoke access in your Google account. Use of data received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Do not use Studio for illegal activities, to infringe third-party rights, or to attempt to access other people’s accounts or works. We may suspend accounts that compromise the security or operation of the service.
Studio is provided “as is”, with no guarantee of uninterrupted availability. We keep backups and apply reasonable security measures, but we recommend exporting copies of your works. We may update these terms; if a change is significant we will announce it on the platform.
All traffic is encrypted over HTTPS (TLS). Passwords and access codes are never stored in plain text: they are hashed with bcrypt and a unique salt per credential. You can encrypt your works with AES-256 using a key only you know — not even the server can read them without it — with a recovery key in case you forget it. API keys are stored encrypted, shared links use random tokens with optional password and expiry, and sign-in is protected against brute force. No measure is absolute: keep your recovery key safe and export copies of your works.
For any questions about these terms, reach us via the contact page: yoniliman.com/contacto.