Sysslor uses end-to-end encryption so your community's saved chore and recipe details stay private. This page explains exactly what is protected, what the service can see, and what tradeoffs that creates.
These data are encrypted on your device before reaching the server. The server stores only encrypted blobs it cannot decrypt:
AI features are off by default for each community; community managers can enable or disable them at any time. Admin and Parent roles receive the feature-specific recipe AI permission (`recipes.ai`) by default; Kid does not. You also need recipe-writing permission (`recipes.write`), Premium entitlement, and per-import confirmation. When you confirm, Sysslor receives the URL you submitted, fetches the page, and sends bounded extracted page text—not the URL itself by default—to the active external AI provider. The URL and fetched page are temporarily visible to Sysslor's importer; the provider receives the extracted text and fixed instructions. Sysslor does not add your account/member IDs, profile data, or community identity to the provider request. Extracted source text may itself contain identifying details. The provider's location and retention depend on its terms, shown in the per-import notice. Turning off AI stops new requests but cannot recall content already sent. Turning off the community AI setting prevents imports whose server-side setting check happens after the setting takes effect, but it cannot cancel an import already in progress or recall content already sent.
To make scheduling, assignment, sync, and rewards work, the server stores some operational metadata in readable form:
Outside the separately disclosed AI recipe import described above, the server cannot read saved E2EE content such as:
Encryption keys are generated on your device during first-time setup. They are stored exclusively in your device's secure storage — the server never receives them.
To share access with community members, keys are exchanged directly between devices using QR codes. No keys ever pass through the server.
If all devices in a community lose their keys, encrypted content becomes permanently unreadable. There is no backdoor and no recovery mechanism — that is the tradeoff for true privacy.
Because Sysslor cannot decrypt your community's saved content, we cannot recover lost chore descriptions, template details, occurrence content, or saved recipes. If you lose access to all devices that hold the community key, that encrypted data is gone.
Operational data (schedules, assignments, balances, memberships) remains intact and can be managed by community admins even if encryption keys are lost.