Loopky Terms of Service
These terms cover the Loopky apps for Android and iOS, the loopky command line tool, the Loopky plugin for AI agents, and the website at loopky.app. Using any of them means you accept these terms. If you do not, please do not use them.
The short version: Loopky is free software with no warranty, the project runs no servers, and what you publish is public and yours to answer for.
1. Who provides Loopky
Loopky is an open-source project by João Victor Sena. The source is at github.com/jvsena42/loopky. There is no company behind it and nothing to pay for: no price, no subscription, no ads and no in-app purchases.
2. The software and its licence
The apps, the command line tool and the agent plugin are released under the MIT License. You may use, copy, change and redistribute the code under that licence.
The software is provided "as is", without warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose and non-infringement. Nothing in these terms takes away a right the MIT License gives you, and nothing here adds a warranty the licence does not.
3. The project runs no servers
There is no Loopky account and no Loopky backend. Your identity is a Pubky keypair, and your decks, cards, images, tags and study progress are written to a Pubky homeserver.
Unless you run one yourself, that homeserver is operated by a third party. If you signed up through Loopky, it is the homeserver Synonym operate for pubky.app. That operator's own terms and policies apply to your account and to everything stored there, alongside these terms.
Because the project holds none of your data, it cannot do the things a hosted service could:
- it cannot recover a lost key, recovery phrase or recovery file. If Loopky holds the only copy of your key and you lose it or sign out without a backup, the account is gone;
- it cannot restore deleted decks or review history;
- it cannot raise a homeserver's limits or reverse a decision its operator makes.
4. Limits your homeserver sets
Some limits you will meet in Loopky belong to the homeserver, not to Loopky, and its operator can change them:
- Storage. The default homeserver gives each account a quota, 1 GB on its free tier. Once it is full, writes are refused until you delete something. Images imported from an Anki deck count against it; a picture added by web address does not.
- Sessions. Signing in gives Loopky a time-limited session. It can expire after about an hour, and writing then needs you to sign in or approve again. Reading may keep working in the meantime.
- Availability. A homeserver, the Pubky indexer or the sign-in relay can be slow or unreachable. Loopky needs a connection to load decks and makes no promise that any of those services will be available.
5. What you publish
Published decks are public. Loopky has no private or local-only decks. Anything you publish can be read by anyone, is indexed for search and discovery, and can be followed or copied by other people. A copy someone else made lives under their key and cannot be recalled.
You keep whatever rights you have in what you publish. You are responsible for it. By publishing you confirm that:
- you have the right to publish the text and images in the deck. That includes pictures you add from the web and material from an Anki deck you import: many shared Anki decks are someone else's copyrighted work, and importing one publishes it under your key;
- the deck contains no one else's personal information, and nothing you would not put on a public web page;
- the content is lawful where you are, and is not meant to harass, defraud or harm anyone.
The project does not review decks before or after they are published.
6. Other people's content
Decks, profiles and tags from other people come from their homeservers and from the Pubky indexer. Loopky does not verify, moderate or endorse them, and is not responsible for what they say or link to. Treat them as you would any content from a stranger on the internet.
The project cannot remove content from a homeserver it does not run. To report something unlawful, contact the operator of the homeserver that hosts it. If the problem is in Loopky itself, open an issue at github.com/jvsena42/loopky/issues.
7. The command line tool and AI agents
The loopky command line tool and the agent plugin act with a session you approve, and that session is limited by design: it can write only Loopky's own data (/pub/loopky/). It cannot post, follow or edit your profile elsewhere on Pubky.
Within that limit, an agent you run acts for you. A deck an agent creates is published under your key and is public, and you are responsible for it as if you had made it by hand. The commands that import or add cards offer a dry run that reports what would be written; use it.
A sign-in link shown by the tool is a login secret until you approve it. Do not paste it anywhere other people can read.
8. Third-party services
Loopky contacts a small number of services run by other parties, each under its own terms: your homeserver, the Pubky sign-in relay and indexer, Homegate when you sign up, Unsplash when you search for a picture, your device's speech services for Listen and Speak, and Google Play, the App Store or TestFlight for the app itself. The privacy policy lists what reaches each one.
9. Children
Loopky is not directed at children under 13.
10. Liability
To the fullest extent the law allows, the Loopky project and its contributors are not liable for any claim, damages or other liability arising from the software or its use. That includes lost decks or study progress, a lost key or account, content published by you or by an agent acting for you, and anything a homeserver or another third-party service does or fails to do.
Some places do not allow some of these limits. Where that is so, they apply only as far as the law permits.
11. Changes to these terms
Material changes will be published here with an updated date above. The revision history of this document is public in the repository, so every change is inspectable.
12. Contact
Questions about these terms: open an issue at github.com/jvsena42/loopky/issues. For help using Loopky, see loopky.app/support.