Terms & Conditions

Napper is a private tool built and operated by Paul Bennett for his own use. It is not offered to anyone else. These terms set out what it is, what it is not, and the basis on which it is made available.

1. Who these terms are between

Napper is operated by Paul Bennett, an individual, referred to here as "the operator". These terms govern any access to or use of Napper, its dashboard at napper.thepaulbennett.com, and these pages.

Napper is not a company, has no employees, and is not a commercial product. If you are reviewing these terms as part of an API or platform authorisation process, the relevant fact is that the operator and the sole user are the same person.

2. Napper is a single-user application

Napper has exactly one authorised user: the operator. There is no sign-up, no account creation, no invitation mechanism, and no way for another person to connect their own accounts or view the operator's data.

Because there is no second user, Napper has no pricing, no subscription, no free tier, no service-level commitment, and no support obligation.

3. Acceptable use

You must not attempt to access Napper, its dashboard, its database, or any account it connects to. You must not attempt to circumvent its authentication, probe it for vulnerabilities without the operator's written permission, or interfere with its operation.

If you believe you have found a security issue, the operator would rather hear about it than not — write to cicero@cicerolearning.com. Reporting a genuine issue in good faith is welcome; exploiting it is not.

4. What Napper does and does not do

Napper reads the operator's own mail, calendar, documents, and business records, classifies what it finds, and prepares summaries and draft replies. The application homepage describes this in full.

Certain limits are structural rather than discretionary:

• Napper does not send email. No send capability is implemented, and an automated check fails the build if one is added. Two of the Google permissions it holds would technically permit sending; the absent code is what prevents it, not the permission.
• It does not delete mail, calendar entries, or files. The one change it makes to a mailbox is removing a message's inbox label when the operator dismisses it — the message remains in All Mail.
• It does not post to any service on the operator's behalf.
• It takes no action the operator has not explicitly approved.

These are commitments about how the software is built, not merely settings. If they change, these terms and the privacy policy change first.

5. Generated content

Napper uses large language models to classify messages and to write summaries and draft replies. Output of that kind can be wrong, incomplete, or misleading. Nothing Napper produces is reviewed by anyone before the operator reads it.

Every draft it writes is left unsent for the operator to read, edit, and send himself. Every summary it produces is his to check. Napper is a filter and a first draft, never an authority, and its output is not advice of any kind — professional, financial, legal, or otherwise.

6. Third-party services

Napper connects to services operated by others — Google, Zoho, GitHub, Supabase, Railway, Vercel, and Anthropic. Use of each is subject to that provider's own terms, and the operator's authorisation of Napper against his own accounts does not alter them.

Napper's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The operator may revoke Napper's access to any connected account at any time, from that provider's own settings.

7. Intellectual property

The Napper source code, its design, and the content of these pages belong to Paul Bennett. No licence to copy, adapt, or redistribute them is granted by their being published here. Content Napper reads — mail, documents, records — remains the property of whoever owned it already; Napper claims no rights over any of it.

8. Availability and changes

Napper is a personal project under active development. It may be changed, interrupted, or switched off permanently at any time, without notice, for any reason or none. There is no commitment that it will work, keep working, or continue to exist.

9. No warranty

Napper is provided as-is and as-available, with no warranties of any kind, express or implied, including any implied warranties of merchantability, fitness for a particular purpose, accuracy, or non-infringement. The operator does not warrant that Napper will be error-free, uninterrupted, secure, or that its classifications and summaries will be correct.

10. Limitation of liability

To the fullest extent permitted by law, the operator is not liable for any indirect, incidental, special, consequential, or punitive damages, or for any loss of data, profits, revenue, or goodwill, arising from Napper or from these pages — whether in contract, tort, or otherwise, and whether or not the possibility of such loss was known.

Nothing here limits liability that cannot lawfully be limited, including liability for death or personal injury caused by negligence, or for fraud or fraudulent misrepresentation.

11. Privacy

What data Napper accesses, where it is stored, how long it is kept, and who can see it are all set out in the Napper privacy policy, which forms part of these terms.

12. Changes to these terms

These terms may be updated. When they are, the "last updated" date above changes with them. If Napper's data handling or its structural limits change, both these terms and the privacy policy are updated before the change takes effect.

13. Governing law

These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-laws rules. Any dispute arising from them is subject to the exclusive jurisdiction of the state and federal courts located in Delaware.

14. Contact

Paul Bennett — paul@cicerolearning.com
About Napper · Privacy policy · thepaulbennett.com