Hosted account terms
These terms cover accounts hosted on Link Jar's Personal Data Server.
Effective date: 6 October 2026
Who provides the service
Link Jar’s hosted account service is provided by Codepolyglots, registered at Mise Vujica 1, Belgrade, Serbia. Contact: hello@linkjar.io.
These terms cover accounts hosted on Link Jar's Personal Data Server (PDS). If another provider hosts your account, that provider's hosting terms apply. Our privacy policy explains how Link Jar handles personal data.
The beta service
Hosting is currently a free, invite-only beta. An invitation allows you to create an account. It does not guarantee uninterrupted service or continued availability.
The PDS stores your AT Protocol repository and files and supports account identity, authentication and synchronization. The service applies rate limits and a maximum upload size of 50 MiB per file. Compatible apps may support different record types and features.
We may change the service or its limits. We will give reasonable notice of planned material changes or closure, through the service or account email. If we plan to close hosting, we will provide an opportunity to export before closure where safe and lawful. Urgent security or legal circumstances may require action without advance notice.
Account security and recovery
Keep your sign-in methods secure. Use the account's authenticated controls for password resets, handle changes and deletion. We may need to verify that you control the account before acting on a support request.
Keep your Private Jar Recovery Kit securely and separately from the hosted account. You need its recovery material to recover access to encrypted private content. Never send support your password, recovery seed, recovery secret or provider token.
The PDS holds online repository and identity signing material. Hosting an account does not mean that you personally hold all identity keys. Your Private Jar Recovery Kit protects access to encrypted content; it is separate from AT Protocol identity recovery.
Link Jar is not for children under 16.
Public and private content
Public repository records can be read and copied by other services and users on the open AT Protocol network. Choose each supported record's visibility carefully.
Private Jar clients encrypt private content before upload. The ordinary PDS storage path does not receive your Private Jar seed or the plaintext of that encrypted content. The host can still process account identity, request metadata, file sizes and timing. Encryption does not protect content on a compromised device or through malicious client software.
Optional previews, snapshots, AI and other app features have separate data flows, described in the privacy policy.
Acceptable use
Store or share only content you have the right to use. Do not use the service for unlawful content or activity, threats, targeted harassment, spam or deceptive impersonation. Do not attack the service, access another person's account without permission, or bypass security controls and rate limits.
Report abuse to hello@linkjar.io. Include the public record address or account DID and a brief explanation. Do not send account credentials or another person's private content.
Restrictions and review
We may limit requests, suspend access or remove hosted content when needed to protect the service, address unlawful activity or enforce these rules. We will explain a restriction through the service or account email where safe and lawful. Urgent action may precede notice.
Contact hello@linkjar.io to request a review or ask about exporting your data. We will consider the request and provide access to export where safe and lawful. We do not promise a fixed response time.
Export and moving your account
You can request help exporting or moving your account at hello@linkjar.io. Repository export uses a CAR file; referenced files must be exported separately. A CAR file alone does not contain those file bytes. Keep your Private Jar recovery material separately so you can decrypt private content after moving.
Moving to another compatible PDS can preserve your DID. Check the destination's requirements before retiring the source account. These terms do not promise a guided migration flow or uninterrupted migration.
Deletion and backups
Request account deletion through the authenticated account-delete flow and complete its confirmation step. Contact hello@linkjar.io if you need help. An unauthenticated email alone does not authorize account deletion.
Account deletion removes your repository from our server. It cannot remove copies already held by independent relays, other services or users. Repository deletion does not mean immediate erasure from backups or immediate cleanup of every unreferenced file. We do not promise automatic revocation of a connected identity provider's grants or tokens; manage those through the provider's account controls as well.
Our recovery system is configured to retain database snapshots for seven days. Server-key and configuration backups retain all captures within seven days and daily snapshots within 30 days. Outages or failed safety checks can delay pruning. These are configured retention windows, rather than an absolute deadline for erasure from every backup.
Server-key backups contain hosting material, not your Private Jar recovery seed. They do not replace your Recovery Kit.
Availability and contact
The beta may be interrupted by maintenance, faults or changes. We promise no uptime, recovery-time or support-response deadline. Keep your own exports and recovery material.
For hosting, sign-in, export, deletion or abuse requests, contact hello@linkjar.io.