Términos de servicio

1. Aceptación de los Términos

Al descargar, instalar o utilizar Layergram, usted acepta estar sujeto a estos Términos de servicio. Si no está de acuerdo, no utilice la aplicación.

2. Responsabilidades del usuario y uso aceptable

Usted es el único responsable del contenido que cifra y transmite. Acepta NO utilizar la aplicación para actividades ilegales, dañinas o terroristas según las leyes de su jurisdicción. Layergram es una herramienta de privacidad, no un escudo contra el crimen. Renunciamos expresamente a cualquier responsabilidad por el uso que usted haga del software.

3. Sin servidor central

Layergram funciona íntegramente de forma local. No alojamos, encaminamos ni almacenamos sus mensajes. No tenemos conocimiento de su identidad ni de sus claves.

4. Sin recuperación de datos (pérdida de claves)

Sus claves y frases de contraseña se guardan exclusivamente en su dispositivo. Si pierde el dispositivo u olvida la frase de contraseña, sus datos se perderán para siempre. No podemos recuperar sus claves bajo ninguna circunstancia. No somos responsables de la pérdida de datos.

5. Exclusión de Garantías

Layergram se proporciona «TAL CUAL». Aunque utilizamos cifrado conforme a estándares del sector, no garantizamos que el software sea invulnerable a todas las formas de ataque, especialmente si el sistema operativo de su dispositivo está comprometido.

6. Limitación de responsabilidad

En la medida máxima permitida por la ley, los desarrolladores de Layergram no serán responsables de ningún daño indirecto, incidental o consecuente, incluida la pérdida de ganancias, datos o activos digitales, que surja del uso o la imposibilidad de usar la aplicación.

Social publishing privacy notice

Updated 13 October 2026. English notice for the publishing integration.

This notice covers Layergram's local social publishing tool, which uses Brand Social Hub to connect authorized social accounts and publish prepared content. It is separate from the Layergram encryption app and its privacy policy.

What the publishing tool processes

When an account owner connects Pinterest through OAuth, Pinterest returns an account identifier, username, account type and authorization tokens. The tool can read the connected account's public boards to select a publishing destination. It sends the chosen board identifier, Pin title, description, image, alternative text, destination link and applicable AI disclosure to Pinterest when the operator explicitly approves and requests publication.

The tool requests the permissions needed for account identification, board discovery and Pin creation: user_accounts:read, boards:read, boards:write, pins:read and pins:write. It does not request advertising or secret-board permissions. It does not scrape accounts, automate engagement or read Layergram encrypted conversations.

Local storage and credentials

The tool runs on the operator's computer. Account credentials, the dedicated app secret and OAuth access and refresh tokens are stored in the local encrypted credential vault. They are used for authorized API calls and token refresh. They are not placed in chat, ordinary draft records or audit logs. Draft content and account references are stored in the local project directory with restricted file permissions; draft content is not encrypted by the publishing tool.

Audit records describe workflow actions without storing draft bodies or credential values. Operation checkpoints used to avoid duplicate API publications are encrypted locally. Local files remain until the operator removes them. The tool does not operate a central service collecting these records.

Sharing and control

Authorized API requests send the required data to Pinterest. Pinterest processes that information under its own privacy policy and the account's settings and access level. Published content may be publicly visible when the account owner chooses public publication and the app has the required access. Trial API Pins are sandbox entities visible only to their creator.

Connecting an account does not publish content. Each draft is previewed and approved separately, and publishing is a separate operation. Editing a draft revokes its previous approval. The operator can revoke the app's access in Pinterest's connected-app settings and can remove the local credentials, drafts and operation records from their computer. Revoking access or deleting local files does not delete Pins already stored on Pinterest; those can be managed on Pinterest.

Contact

Questions about this publishing integration can be sent to legal@layergram.app.