Get in touch
One person reads this, so replies aren't instant — but everything gets read.
What to include
Reporting a bug
The three things that make a bug fixable: what you were doing, what happened, and what you expected instead. Your browser and whether you're on a phone or a computer help too. If something looked visually wrong, a screenshot saves a lot of back-and-forth.
Please don't send your password. Nobody here will ever ask for it.
Correcting a guide
Corrections are genuinely welcome, especially with a source. The guides try to represent the research honestly, including where it's contested, and if one of them overstates a finding or cites something that hasn't held up, that's worth fixing. Say which guide and which paragraph.
Requesting a feature
Say what you're trying to do, not just what you'd like added — the underlying problem is usually more useful than the proposed solution, and there's often already a way to do it.
Your data
For a copy of what's stored about your account, or deletion when you can't get into the app yourself, email from the same context if you can and include your username. Note that most deletion can be done directly from the account menu in the app, which is immediate. What's stored and why →
Rights holders
If material you hold rights in has been published to the public library or through a share link, email with a link to the item and it will be taken down.
What this isn't
There's no tutoring service here and no homework help — the app is a tool and the guides are about method. For questions about your syllabus, your grades or your exam entries, your school, college or exam board is the right place to ask.