Terms of Service

1. Acceptance of the Terms

By downloading, installing or using Layergram, you agree to be bound by these Terms of Service. If you do not agree, do not use the app.

2. User Responsibilities and Acceptable Use

You are solely responsible for the content you encrypt and transmit. You agree NOT to use the app for illegal, harmful or terrorist activities under the laws of your jurisdiction. Layergram is a privacy tool, not a crime shield. We expressly disclaim any liability for your use of the software.

3. No Central Server

Layergram operates entirely on-premises. We do not host, route or store your messages. We have no knowledge of your identity or your keys.

4. No Data Recovery (Loss of Keys)

Your keys and passphrases are saved exclusively on your device. If you lose your device or forget your passphrase, your data will be lost forever. We cannot recover your keys under any circumstances. We are not responsible for lost data.

5. Exclusion of Warranties

Layergram is provided 'AS IS'. Although we use industry standard encryption, we do not guarantee that the software is invulnerable to all forms of attack, especially if your device's operating system is compromised.

6. Limitation of Liability

To the maximum extent permitted by law, Layergram developers will not be liable for any indirect, incidental or consequential damages, including loss of profits, data or digital assets, arising out of the use of or inability to use the app.

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.