Scope

These terms cover three surfaces: the public site at maleta.dev (catalog, documentation, and institutional pages), the workspace at app.maleta.dev where a Maleta is assembled and saved, and the maleta CLI that applies a Maleta on a computer. This page describes how those surfaces behave; it does not add obligations the product does not implement.

[TODO: confirm legal operator and address]

[TODO: confirm governing law and venue]

[TODO: legal review and effective date]

The account is optional

The GitHub sign-in is optional and exists only in the workspace. Everything works without it. Signing in does not send a Maleta, a selection, or a recent search to the server.

A Maleta reaches your account only when you choose Save to account. Until then it is a local file in this browser. You can delete a saved Maleta from the account, and you can sign out at any time.

Skills, sources, and local execution

A Maleta is a declarative selection: the maleta.json manifest records each skill's source, and the CLI resolves external sources from the public GitHub content they declare. You download and run the CLI and any applied content on your own computer. Third-party skills keep the licenses and attribution of their upstream sources; a Maleta does not transfer any right to that content.

The catalog lists public sources as references. Reviewing a source before applying it is your decision, and the CLI's --dry-run shows the plan without writing destinations or fetching content.

Authorized computers

maleta login authorizes one computer to follow the Maletas in your account with a short code confirmed at app.maleta.dev/device. You can revoke any authorized computer under /account. maleta logout removes the credential from that computer and asks the server to revoke it.

Support and changes

Report a problem, a broken source, or a security issue by email at contato@maleta.dev. This page may change as the product changes; the date at the top is the last update.

← Back to the catalog