Dokumen resmi
Istilah Layanan
Bacalah istilah ini dengan hati-hati sebelum menggunakan Layergram.
1. Penerimaan Syarat
Dengan mengunduh, menginstal, atau menggunakan Layergram, Anda setuju untuk terikat oleh Ketentuan Layanan ini. Jika Anda tidak setuju, Anda tidak akan menggunakan aplikasi.
2. Tanggung Jawab Pengguna dan Penggunaan yang Aksa
Anda bertanggung jawab atas konten yang Anda enkripsi dan kirimkan. Anda setuju untuk tidak menggunakan aplikasi untuk kegiatan ilegal, berbahaya atau teroris sesuai dengan hukum di wilayah Anda. Layergram adalah alat privasi, bukan pelindung kejahatan. Kami secara eksplisit menyatakan setiap tanggung jawab atas penggunaan perangkat lunak Anda.
3. Tidak ada Server Pusat
Layergram beroperasi secara lokal, kami tidak menyimpan, mengusung, atau menyimpan pesan Anda, kami tidak memiliki informasi identitas Anda atau kunci Anda.
4. Tidak Ada Rekuplikasi Data (Kealahgunaan Kunci)
Kunci dan kata sandi Anda hanya disimpan di perangkat Anda. Jika Anda kehilangan perangkat atau lupa kata sandi, data Anda akan hilang selamanya. Kita tidak bisa mendapatkan kunci Anda dalam apa pun keadaan.
5. Pengecualian Jaminan
Layergram disediakan 'COSÌ COM'È'. Meskipun kami menggunakan enkripsi standar industri, kami tidak menjamin bahwa perangkat lunak tidak terancam oleh serangan apapun, terutama jika sistem operasi perangkat Anda terganggu.
6. Pembatasan Tanggung Jawab
Sejauh yang diizinkan oleh hukum, pengembang Layergram tidak akan bertanggung jawab atas kerusakan tidak langsung, kebetulan atau konsekuensial, termasuk kerugian keuntungan, data, atau aset digital, yang timbul dari penggunaan atau ketidakmampuan untuk menggunakan aplikasi.
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.