MyNotes

End-User License Agreement

Last updated: April 28, 2026 (version 2026-04-28)

Summary

A plain-English outline of what this license permits and the protections it asserts. The numbered sections below are the actual EULA — they control if there's ever a conflict.

  • You get a personal, non-transferable right to use MyNotes, subject to the limits in Schedule A at the bottom of this page.
  • You may use the API on Dev / Dev-pro tiers — for your own scripts, jobs, and integrations — within the published rate limits, and you are responsible for every action taken with your API tokens until you revoke them.
  • You may make a note publicly readable by minting a per-note share link; you are responsible for what each shared note contains, and we may take down links that violate Acceptable Use.
  • You may not scrape, redistribute, reverse-engineer, train AI models on, or imitate the look-and-feel of the Software, and you may not create multiple Accounts to evade caps.
  • The Software incorporates open-source components, each licensed under its own terms; nothing in this EULA limits your rights under those licenses.
  • Use of the Software is at your own risk: we cap our liability and disclaim warranties (see §22 and Terms §§17–20), you indemnify us for misuse (see §23), and we may seek injunctive relief without bond for IP and brand breaches (see §24).
  • This EULA supplements the Terms of Service; the Terms govern the broader service relationship (account, billing, dispute resolution, etc.) and the Privacy Policy governs personal-data handling.

1. Parties and scope

This End-User License Agreement ("EULA") is a legal agreement between [COMPANY] ("we", "us", "our") and the individual using a MyNotes account ("you"). It governs your right to use the MyNotes web application, the MyNotes REST API, any client tools, examples, and documentation we make available, and any patches, updates, or new versions of the foregoing that we publish (together, "the Software").

This EULA supplements and incorporates our Terms of Service and Privacy Policy. Where two of those documents address the same subject, the more specific provision controls. The Terms govern your account, billing, conduct, dispute resolution, and termination; the Privacy Policy governs personal-data handling — read all three.

2. Definitions

  • Account — the unique MyNotes user record created when you register. One human per Account, per Terms §2.
  • API — the MyNotes REST API exposed under /api/v1, available on Dev and Dev-pro tiers.
  • API Token — a bearer credential generated from Settings → API tokens that authorizes API requests on behalf of your Account.
  • Tier — the capacity bracket your Account is assigned (Free, Paid, Dev, Dev-pro). Tier governs the limits in Schedule A.
  • Schedule A — the canonical service-limits table at the end of this EULA, also published at /limits and §Schedule A of the Terms. All three surfaces render from the same source.
  • Service — defined in the Terms; refers to the MyNotes hosted offering as a whole, of which the Software is the licensed-software component.
  • Your Content — defined in Terms §4; refers to anything you create, upload, or store through the Software.
  • Brand Assets — defined in §11.
  • Feedback — defined in §27.
  • Indemnitee — defined in §23.
  • Usage Statistics — defined in §26.

3. License grant

Subject to your continued compliance with this EULA and the Terms of Service, we grant you a limited, personal, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the Software for your own personal or business note-taking, within the limits set out in Schedule A. The license is for the benefit of one human — the Account holder — and is not assignable. Nothing in this EULA transfers ownership of the Software, the API, the underlying source code, or the MyNotes name and brand to you.

4. Acceptance, version, and continued use

You accept this EULA by creating an Account, by signing in to an existing Account on or after the effective date shown above, or by otherwise using the Software. We may publish a new version of this EULA at any time. Each version is identified by the date stamp at the top of this page; the version stamp is also recorded against your Account at registration.

For material changes, we will follow the notice mechanism in Terms §21 (which is incorporated here by reference). Continued use of the Software after the effective date of a new version constitutes acceptance of that version. If you do not agree, you may close your Account before the new version takes effect; closure follows the process in Terms §11.

5. Permitted use

  • Create, edit, organize, search, pin, rename, soft-delete, restore, and export your own notes through the web UI.
  • Generate API Tokens (Dev / Dev-pro tiers) and use them from your own scripts, cron jobs, CI pipelines, and CLI tools, within the rate limits in Schedule A and the token-handling rules in §6.
  • Embed MyNotes API calls in software you write, provided your software does not redistribute access to other end users as if it were a hosted service of its own (see §8).
  • Make individual notes publicly readable through per-note share links, governed by §7.
  • Make a reasonable number of personal backup copies of your exported notes for your own off-site retention. The export feature in Options → Download all is the authorized extraction method; bulk extraction by other means (browser scraping, headless automation against the web UI) is not permitted.
  • Cancel, export, or delete your Account at any time. Reading and exporting remain available even after a paid subscription lapses (see Terms §11–12).

6. API tokens

On Dev and Dev-pro tiers, you may generate API Tokens up to the per-tier active-token cap in Schedule A. Each Token authorizes the same actions your Account would perform through the web UI, scoped to that single Account.

  • Treat tokens as credentials. An API Token is the equivalent of a password — anyone holding it can read and modify your notes within the API surface and your Tier limits. Store tokens in a secrets manager, environment variable, or equivalent; never paste them into chat, screenshots, public repositories, issue trackers, or LLM web UIs.
  • You are responsible for what tokens do. Until you revoke a Token, every request it makes is conclusively attributed to your Account, counts against your Tier's limits, and is your responsibility — including under §17 (Your representations) and §23 (Indemnification).
  • Revoke immediately on compromise. If you suspect a Token has been exposed, revoke it from Settings → API tokens at once and rotate to a fresh Token. Email support@example.com for help if needed.
  • Don't share or impersonate. Do not share a Token with parties not authorized to act for your Account, do not operate the API on behalf of a person whose Account we have suspended or terminated, and do not misrepresent the origin of API requests.
  • Rate limits. The API is throttled per the values in Schedule A. Sustained over-cap traffic returns HTTP 429 and is logged at Settings → API errors. Repeated abuse may result in token revocation.
  • Our revocation rights. We may revoke any Token that has been used in breach of this EULA, that we reasonably believe is compromised, or that is generating abusive traffic — even before any Account-level action. Where it is reasonable to do so, we will notify you.

7. Public share links

You may opt to publish an individual note as a public, read-only page by minting a share link. The link is a URL containing a high-entropy token (e.g. /n/<token>). Anyone with that URL can view the note's current content without signing in.

  • Possession is access. The link is the access control. Distribute it only to people you intend to share with, and treat it as you would any unguessable URL.
  • Revocation. Toggle sharing off (or rotate the link) from the note's actions menu at any time. Revocation takes effect immediately; previously-cached copies on the visitor's side are outside our control.
  • Live content. A public link always reflects the current saved content of the note. If you do not want a viewer to see further edits, revoke the link before editing.
  • Your representations. You represent and warrant, for each note you publish via a share link, that (a) you own or have all necessary rights to publish the content, (b) the content does not infringe any third-party right and is not unlawful, and (c) the content complies with Acceptable Use (Terms §6). You are solely responsible for what your share links display, and your liability for share-link content is governed by §23 (Indemnification).
  • Acceptable Use. Public share links are subject to Terms §6 (Acceptable Use). We may disable a public link without notice if its content is unlawful, infringing, abusive, or otherwise in breach of these terms; we will tell you when we do.
  • Footer and discoverability. We may render an unobtrusive footer on public share-link pages identifying the Software, linking to our Acceptable Use rules, and providing a means to report abuse. We may delist share-link URLs from search engines or omit them from any internal "popular shares" surface at our discretion.
  • Throttling. Public-link URLs are rate-limited per visitor IP to deter scraping; the values are listed in Schedule A. Do not embed public links in spam, link farms, or automated polling systems.

8. Restrictions

You will not, and will not assist, encourage, or permit anyone else to:

  • copy, mirror, scrape, or systematically extract notes (other than your own) from the Software;
  • resell, sublicense, lease, rent, or otherwise make the Software available to third parties as a hosted service;
  • reverse-engineer, decompile, disassemble, or attempt to derive the source code of any compiled component (this does not restrict ordinary, lawful interoperability work where applicable law — including the EU Software Directive (2009/24/EC) and the equivalent UK provisions — expressly allows it);
  • use the Software, the API, or any output thereof to train, fine-tune, evaluate, benchmark, or distill any artificial-intelligence or machine-learning model, including by way of API responses, screenshots, error messages, or any other Software-rendered output, without our prior written consent;
  • operate any bot, crawler, scraper, or automated agent against the Software, except via the API and within the rate limits in Schedule A;
  • create or operate more than one Account, evade Free-tier or other Tier limits, or use disposable / temporary email addresses to circumvent any rate limit, capacity cap, or signup gate (see also §18);
  • upload, transmit, or expose any malware, virus, worm, ransomware, exploit, or other code intended to damage, surveil, or interfere with the Software or its users;
  • use the Software to store, transmit, or distribute content that is unlawful, infringes a third party's rights, or violates the Acceptable Use rules in the Terms of Service;
  • circumvent, disable, or interfere with security, throttling, signature verification, billing, or other technical limits of the Software (including the rate limits and capacity caps in Schedule A);
  • use automation against the browser surface to bypass the API rate limits, capacity caps, or Tier gating (i.e. don't headless-browser the web UI to fake API usage on a Free / Paid Account);
  • misrepresent the origin of API Tokens, share Tokens with unauthorized parties, or operate the API on behalf of a person whose Account we have suspended or terminated;
  • remove, obscure, or alter any copyright, trademark, or other proprietary notice on the Software, the API documentation, or materials exported from the Service;
  • produce, distribute, or assist in the development of a product, application, or service that imitates the look-and-feel, structure, sequence, organization, copy, or user experience of the Software, in whole or in material part, whether or not based on observation of the Software;
  • publish or distribute any benchmark, performance result, security finding, or competitive analysis of the Software without our prior written consent (responsible-disclosure reports to support@example.com are welcome and may be published with our consent);
  • perform any unsolicited security testing, vulnerability scanning, penetration testing, or denial-of-service activity against the Software or its infrastructure without our prior written consent;
  • make false, misleading, or disparaging public statements about the Software, or use the Software to harass, threaten, or disparage us, our personnel, or other users; or
  • use the Software in any way that would cause us to violate sanctions, export controls, or applicable law (see §16).

9. Reservation of rights

All rights in the Software not expressly granted to you in this EULA are reserved by us and our licensors. No rights are granted by implication, estoppel, exhaustion, or otherwise. The MyNotes name, logo, and product look-and-feel are our trademarks or trade dress; this EULA does not grant you a right to use them other than to identify the Software in factual references made in accordance with §11.

10. Open-source and third-party components

The Software incorporates components made available under open-source and other third-party licenses (for example, the Ruby on Rails framework and a number of Ruby gems and JavaScript libraries). Each such component is licensed under its own terms.

Nothing in this EULA limits, supersedes, or alters the rights granted to you under those third-party licenses with respect to the components they cover. Where a third-party license conflicts with this EULA in respect of the licensed component, the third-party license controls for that component. A list of notices and licenses for the components included in the Software can be requested from support@example.com.

11. Trademarks and brand assets

"MyNotes", the MyNotes logo, the look-and-feel and trade dress of the Software, and any related word marks, design marks, taglines, or product names (collectively, "Brand Assets") are our trademarks and trade dress, whether or not registered. We grant you no license to use the Brand Assets except as expressly set out below.

Permitted reference. You may make truthful, descriptive references to "MyNotes" — for example, in a personal review, an article that discusses tools you use, or a non-commercial educational context — provided your reference is accurate, does not imply endorsement or partnership, and does not use a Brand Asset in a manner likely to cause confusion as to source, sponsorship, or affiliation.

Not permitted. You will not (a) register or use a domain name, application name, social-media handle, app-store listing, ad keyword, or trademark that incorporates "MyNotes" or a confusingly similar term; (b) use the Brand Assets in commercial materials, paid advertising, or partner-program collateral; (c) modify the logo or use it as a favicon, profile picture, or app icon; (d) create derivative branding suggesting endorsement or affiliation; or (e) imply that we sponsor, endorse, or are affiliated with you, your product, your service, or your content.

Revocation. Any limited brand permission granted under this section is revocable at any time, with or without cause, on notice. On revocation, you will promptly cease the challenged use and remove any uses then within your control.

12. Service limits

Your right to use the Software is bounded by the limits in Schedule A below. We enforce these limits in code. Exceeding them does not entitle you to additional capacity; rather, the Software will refuse the over-cap operation (e.g. a 422, 413, or 429 response, or an in-app cap message) and the excess request is simply rejected. We may revise these limits, including reducing them, at our discretion — material reductions will be announced with reasonable notice, consistent with Terms §13. We may also throttle or restrict any Account whose usage materially impacts shared infrastructure or other users, even where the Account has not exceeded a stated Schedule A cap.

13. Updates and changes

We may release new versions of the Software, change features, fix bugs, or modify the API surface (including endpoints, schemas, error codes, and rate limits) at any time. We aim to keep documented changes backwards-compatible within a major API version, but we do not guarantee it for unannounced or undocumented behavior. Updates may install automatically without further notice; you are licensed to use the Software as we make it available from time to time, not to any specific version of it.

Live propagation to the browser is limited. When you have a note open in the web UI and a write hits it through the API, only append-only notes update in place without a refresh — the browser subscribes to a per-user, per-note stream and replaces the body as new content lands. Edits to editable (CRUD) notes made through the API (PATCH /api/v1/notes/:id and similar) are not pushed to an open browser tab; the tab continues to show the previous content until you refresh the page. This is by design — pushing mid-edit content swaps into the editor would clash with in-flight, autosaved local changes.

14. Support, availability, and service levels

We may, at our discretion, provide informal email support; we are not obligated to do so for any particular request. We do not commit to any service-level agreement, uptime target, response time, or resolution time for the Software. Time-sensitive matters — security reports, suspected token compromise, billing disputes, privacy and data-deletion requests — are prioritized; general questions and feature requests may go unanswered.

We aim for high availability of the Software, but we do not guarantee that it will be uninterrupted, error-free, or secure against every threat. Maintenance, upgrades, dependency outages, or factors beyond our reasonable control may cause temporary unavailability. Nothing in this section limits any right you have under mandatory consumer-protection law.

15. Beta and experimental features

We may make features available that are labelled "beta", "preview", "experimental", "early access", or similar. Beta features are provided as is, may change materially or be withdrawn without notice, may have known defects, and may be excluded from any informal availability or backwards- compatibility expectations described in §13 or §14. Use of a beta feature constitutes acceptance of these additional limitations.

16. High-risk uses and export controls

High-risk uses. The Software is general-purpose note-taking software. It is not designed, built, or licensed for use in environments where its failure or unavailability could lead to death, personal injury, environmental harm, or significant property damage — including, without limitation, aviation, medical-device control, life-support, nuclear-facility operation, autonomous-vehicle control, weapons systems, or other safety-critical or hazardous applications. You agree not to use the Software in any such environment.

Export controls and sanctions. You represent and warrant that you (a) are not located in, organized under the laws of, or ordinarily resident in a country or territory subject to a comprehensive embargo or trade sanctions administered by the United States, the United Kingdom, the European Union, or the United Nations, (b) are not on any sanctions or denied-party list maintained by those authorities (including the US OFAC SDN List), and (c) will not access, use, or export the Software in violation of applicable export-control or sanctions laws. You will not use the Software in connection with the development, design, or production of nuclear, chemical, or biological weapons, or missiles capable of delivering them.

17. Your representations and obligations

By using the Software, you represent and warrant on a continuing basis that:

  • Authority and capacity. You have the legal capacity to enter into this EULA, are at least the age of majority in your jurisdiction (or otherwise meet the eligibility rules in Terms §1), and, if you are entering on behalf of an organization, you have authority to bind that organization.
  • Accuracy. All registration and Account information you provide is accurate, current, and complete, and you will keep it so. We may suspend an Account whose information we reasonably believe is materially false or stale.
  • Lawful use. You will use the Software only for lawful purposes, in compliance with all laws applicable to you (including data-protection, export-control, sanctions, tax, and consumer law).
  • No malware. You will not introduce, host, or transmit through the Software any virus, worm, ransomware, or other malicious code.
  • Third-party rights. You have, and will maintain, all rights necessary to upload, store, share, and (where applicable) publish Your Content through the Software, and your use of the Software does not infringe any third party's intellectual-property, privacy, publicity, or other rights.
  • Sanctions and prohibited use. You are not on a sanctions or denied-party list and will not use the Software for any purpose that would cause us to violate sanctions or export-control law (see §16).
  • Credential safekeeping. You will safeguard your password, your API Tokens, and any private share-link URLs; we may rely on any action authenticated by those credentials as your action.
  • Cooperation. You will cooperate, on reasonable request, with our investigation of any suspected breach of this EULA, security incident, or abuse complaint involving your Account.

18. Account integrity and anti-abuse

  • One Account per human. You will hold only one Account, unless we agree otherwise in writing. You will not create or operate additional Accounts to evade Free-tier caps, paid-tier caps, throttling, suspension, termination, or any other gate.
  • No automated signup. You will not use scripts, bots, or other automation to create Accounts, accept terms, or evade signup controls.
  • No account sharing. Each Account is for one human; you will not share your password, your Account, or your sign-in session with any other person, except as expressly contemplated by Account-delegation features (none currently exist).
  • No impersonation. You will not register an Account under another person's name or email address, or in a manner that misrepresents your identity, affiliation, or authority.
  • Suspect activity. We may, at our discretion, suspend, throttle, or restrict an Account that we reasonably believe is being used in breach of this section — even before any final determination — including by requiring identity re-verification before re-enabling Software access.

19. Compliance and regulated industries

  • General-purpose Software. The Software is general-purpose note-taking software. We do not represent that it complies with — and you will not use the Software in a way that requires us to comply with — sector-specific regulation, including (without limitation) HIPAA, GLBA, FERPA, COPPA, PCI-DSS, FedRAMP, ISO 27001/27018 certification, SOC 2 attestation, or the EU NIS2 Directive.
  • Personal data of others. If Your Content includes personal data of any individual other than yourself, you are the controller of that data under applicable data-protection law (including the GDPR and UK GDPR where they apply); we act as processor only to the extent necessary to operate the Software for you. If you require a Data Processing Addendum (DPA), contact privacy@example.com before storing such data in the Software.
  • Children. You will not use the Software to collect or store personal data from a child below the age threshold required by applicable law (e.g. 13 in the US under COPPA, 16 in many EU member states under GDPR), and you will not register an Account for or on behalf of any such child.
  • Industry-specific risk. Where your use case is subject to additional law (medical, financial, legal-professional privilege, classified information, etc.), you are solely responsible for assessing whether the Software is fit for that use; we make no such fitness representation.

20. Chargebacks and payment disputes

  • Contact us first. If you believe a charge was made in error or is not authorized, you agree to contact support@example.com in good faith before initiating a chargeback or payment-network dispute.
  • Chargebacks as breach. Initiating a chargeback or payment-network dispute against us or our payment processor without first contacting us is a material breach of this EULA. We may suspend or terminate your Account for the duration of the dispute and thereafter, recover any costs we incur (including chargeback fees, processor penalties, and reasonable legal fees), and use Account information to oppose the dispute.
  • Cooperation. You will cooperate in good faith to resolve disputes informally, and will promptly withdraw any chargeback that we have shown to be unfounded.

Statutory consumer rights preserved. Nothing in this section limits any statutory right you have to a refund, withdrawal, or chargeback under mandatory consumer-protection or payment-services law (including the EU/UK rights described in Terms §17 and §9).

21. Termination

This EULA terminates automatically if you breach it, on closure of your Account (whether by you or by us, per Terms §11), or as set out below. We may also terminate this EULA, suspend your Account, revoke API Tokens, or remove public share links at any time, with or without cause, on reasonable notice — and immediately, without notice, in the case of (a) a material breach, (b) a security or abuse risk to the Software or its users, (c) a legal or regulatory requirement, or (d) suspected fraud, chargeback abuse, sanctions exposure, or impersonation. Where the issue can reasonably be remedied, we will try to give you notice and a chance to correct it first; we are not obliged to do so where the breach is material, repeated, or where notice would be inappropriate.

On termination by us for breach, no refund of pre-paid fees is owed except to the extent required by mandatory consumer-protection law (see Terms §9 and §17). Pre-existing payment obligations and any costs recoverable under §20 (Chargebacks) survive termination. On termination, your license to use the Software ends immediately; you must stop using the API and any Tokens you hold, all of which we may revoke. Your data is handled per Terms §12.

Survival. The following sections survive termination of this EULA, in addition to any provisions that by their nature should survive: §2 (Definitions), §6 (API Tokens — to the extent it allocates responsibility for actions taken before revocation), §8 (Restrictions), §9 (Reservation of rights), §10 (Open-source and third-party components), §11 (Trademarks and brand assets), §12 (Service limits — as to past use), §16 (High-risk uses and export controls), §17 (Your representations), §19 (Compliance and regulated industries), §20 (Chargebacks), §22 (Disclaimers and liability), §23 (Indemnification), §24 (Equitable remedies and limitations on claims), §25 (Compliance with legal process), §26 (Statistics and usage data), §27 (Feedback), §28 (Privacy), §29 (Governing law and contact), and §30 (General provisions).

22. Disclaimers and liability

The Software is provided "as is" and "as available", without warranty of any kind, express, implied, or statutory — including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, and uninterrupted or error-free operation — except as required by mandatory consumer-protection law. You acknowledge that the disclaimers in this section, the indemnification in §23, the equitable-remedies and limitation-on-claims provisions in §24, and the liability cap in Terms §20 are essential to the basis of the bargain — without them we would not be able to make the Software available at the prices charged or, for the Free tier, at all.

The disclaimer, liability framework (including the cap), and consumer-rights provisions set out in the Terms of Service (§§17–20) apply to this EULA and are incorporated here by reference. Nothing in this EULA limits any right you have under mandatory law that cannot be excluded by contract.

23. Indemnification

To the fullest extent permitted by law, you will defend, indemnify, and hold us, our officers, employees, and contractors (each, an "Indemnitee") harmless from and against any claim, demand, action, proceeding, loss, damage, cost, or expense (including reasonable legal fees) arising out of or related to:

  • Your Content, including any content you publish via a public share link (§7);
  • Your use of the API or any actions taken with your API Tokens before revocation (§6);
  • Your breach of this EULA, the Terms of Service, or the Privacy Policy;
  • Your violation of applicable law or any third-party right (including intellectual-property, privacy, publicity, defamation, or contract rights);
  • Any chargeback or payment dispute initiated in breach of §20;
  • Any false or misleading representation or warranty under §17; and
  • Any claim that would not have arisen but for your use of the Software in breach of §16 (high-risk uses, sanctions, export controls), §18 (account integrity), or §19 (sector compliance).

We may assume the exclusive defense and control of any matter subject to this section, in which case you will cooperate with us at your expense; we may settle on terms that bind you, provided no settlement imposes a non-monetary obligation on you (such as an admission of liability) without your prior written consent, not to be unreasonably withheld.

This section does not apply to consumers to the extent prohibited by applicable law; where it does apply to a consumer, it applies only to the extent the loss is attributable to your fault (consistent with Terms §18).

24. Equitable remedies and limitations on claims

  • Equitable relief for us. You acknowledge that a breach of §6 (API Tokens), §7 (Public share links — to the extent it concerns content rights), §8 (Restrictions), §11 (Trademarks and brand assets), §17 (Your representations), §18 (Account integrity), or your obligations regarding our intellectual property, may cause us irreparable harm for which money damages are inadequate. We may, in addition to any other remedy, seek injunctive or other equitable relief in any court of competent jurisdiction, without the obligation to post any bond or undertaking, and without prejudice to the consumer-forum rule in Terms §17 / §22.
  • Limitation period. Except where mandatory law provides a longer period, any claim arising out of or related to this EULA or the Software must be brought within one (1) year of the date the claim accrued, failing which the claim is permanently barred.
  • Individual claims only. Where permitted by applicable law, claims arising out of or related to this EULA must be brought in your individual capacity and not as a plaintiff or class member in any purported class, consolidated, or representative proceeding. This paragraph does not apply (a) where prohibited by mandatory consumer-protection or procedural law, or (b) to any consumer in a jurisdiction whose law renders class-action waivers unenforceable in consumer contracts (including EU member states and the United Kingdom).
  • Jury-trial waiver (US only, where permitted). To the maximum extent permitted by applicable law, the parties waive any right to a jury trial in respect of any dispute arising out of or related to this EULA. This paragraph does not apply where the waiver is unenforceable under mandatory law.
  • No setoff. You will not set off any amount you allege we owe you against fees you owe us; disputed fees must be raised under §20 (Chargebacks), not unilaterally withheld.

Mandatory consumer rights, statutory limitation periods, and procedural rights conferred by law (including, for EU/UK consumers, the rights in Terms §17) override the foregoing to the extent they conflict.

25. Compliance with legal process

We may comply with subpoenas, court orders, lawful requests from regulators or law-enforcement agencies, and other legal process, including by disclosing information about your Account, Your Content, and your use of the Software as we reasonably determine to be required. Where law permits, we will use reasonable efforts to notify you in advance so that you may seek a protective order; where law prohibits notice (for example, under a statutory non-disclosure obligation), we will not notify you until the prohibition lifts. We are not liable to you for compliance with legal process undertaken in good faith.

26. Statistics and usage data

We may collect, generate, and analyze aggregated, anonymized, and de-identified statistics, telemetry, and usage data about how the Software is used (collectively, "Usage Statistics"). Usage Statistics are owned by us and may be used for any lawful purpose, including operating, securing, and improving the Software, capacity planning, public reporting, and marketing. Usage Statistics do not identify you and are not subject to the license-grant restrictions on Your Content in Terms §4; nothing in this section authorizes us to use Your Content (in identifiable form) outside the scope permitted by the Terms or the Privacy Policy.

27. Feedback and idea submissions

If you send us suggestions, feature requests, bug reports, screenshots, mock-ups, code samples, or other feedback or ideas about the Software ("Feedback"), the following apply:

  • Free use. You grant us a perpetual, irrevocable, worldwide, royalty-free, fully sublicensable license to use, reproduce, modify, distribute, and otherwise exploit the Feedback without restriction or compensation, including to develop and improve the Software.
  • No confidentiality. Feedback is not confidential, and we have no obligation of confidentiality, attribution, or compensation in respect of it. Do not send us anything you wish to keep confidential.
  • No fiduciary duty. Submitting Feedback does not create any partnership, joint venture, employment, agency, or fiduciary relationship between you and us.
  • Independent development. You acknowledge that we may already have, or may independently develop or acquire, products, features, or ideas that are similar to or compete with your Feedback, and that nothing in this EULA restricts us from doing so. You waive any claim that we have misappropriated, taken advantage of, or owe you compensation for any idea, concept, or feature, however similar to your Feedback.
  • You are not obligated to submit Feedback, and we are not obligated to act on it.

28. Privacy and data protection

Your use of the Software involves the processing of personal data; that processing is governed by our Privacy Policy, which explains what we collect, why, how long we keep it, and the rights you have over it. Nothing in this EULA limits any right you have under applicable data-protection law (including the GDPR and UK GDPR where they apply).

29. Governing law and contact

This EULA is governed by the laws of [Your jurisdiction], without regard to its conflict-of-law rules, and subject to the consumer-forum rule in Terms §17 where it applies. Questions about this EULA can be sent to support@example.com; privacy and data-deletion requests go to privacy@example.com.

We aim to respond to email enquiries as soon as we reasonably can, but we do not commit to any specific response time and are under no obligation to reply to every message. Time-sensitive matters — security reports, suspected token compromise, billing disputes — are prioritized; general questions and feature requests may go unanswered. Nothing in this section limits any right you have under mandatory consumer-protection law.

30. General provisions

  • Entire agreement. This EULA, together with the Terms of Service and the Privacy Policy, is the entire agreement between you and us about the Software, and supersedes any prior or contemporaneous understandings on the same subject.
  • No reliance. You have not relied on any representation, warranty, or statement (other than the express terms of this EULA, the Terms of Service, and the Privacy Policy) in agreeing to this EULA. Where applicable law gives a consumer rights in respect of pre-contract statements that cannot be contractually excluded, this clause does not exclude those rights.
  • Severability. If any provision of this EULA is held unenforceable, that provision will be modified to the minimum extent necessary to make it enforceable, and the rest of the EULA remains in force.
  • No waiver. Our failure to enforce any right under this EULA, or any delay in doing so, is not a waiver of that right or any other right.
  • Cumulative remedies. Our rights and remedies under this EULA are cumulative and not exclusive of any other right or remedy available to us at law or in equity.
  • Assignment. You may not assign or transfer this EULA, by operation of law or otherwise, without our prior written consent; any purported assignment in breach of this clause is void. We may assign this EULA in connection with a merger, acquisition, reorganization, or sale of all or substantially all of our assets, on notice to you.
  • No third-party beneficiaries. Except for Indemnitees identified in §23, this EULA is for the exclusive benefit of you and us; no other person has any right to enforce it.
  • Successors and assigns. This EULA binds, and benefits, the parties and their respective permitted successors and assigns.
  • Construction. This EULA is drafted in good faith between the parties; ambiguities will not be construed against the drafter.
  • Notices. We may send notices to the email address on your Account or by an in-app notice; you may send notices to support@example.com. Notices are deemed received on transmission to a working address.
  • Electronic communications and signature. You consent to receive notices, agreements, and disclosures from us electronically — by email and through the Software — and you agree that those electronic communications satisfy any legal requirement that such communications be in writing. This EULA may be accepted electronically (for example, by checking an acceptance box at registration or by continuing to use the Software). Electronic acceptance has the same effect as a written signature.
  • Force majeure. We are not liable for delays or failures in performance caused by events beyond our reasonable control (including upstream provider outages, network failures, natural disasters, or governmental action).
  • No agency. This EULA does not create any partnership, agency, joint venture, or employment relationship between you and us.
  • Headings. Section headings are for convenience only and do not affect interpretation.
  • Language. The English-language version of this EULA controls. Any translation is provided for convenience and has no legal effect to the extent it conflicts with the English version.

Schedule A — Service limits

The same canonical reference is also published at /limits; both surfaces render from the same source so the values cannot drift.

1. Account

  • Minimum age: 16 years.
  • Password: 8–128 characters, must include at least one uppercase letter, one lowercase letter, one digit, and one special character (!@#$%^&*()<>?"{}[]).
  • Profile name: up to 80 characters. Bio: up to 500 characters.
  • Disposable / throwaway email domains are not accepted at signup.

2. Notes per account, by tier

Free and Paid use a single shared cap for both note formats. Dev and Dev-pro split the cap by format (rich-text vs plain-text) so a writer who fills their plain quota doesn't lose access to rich-text notes.

Tier Rich notes Plain notes Storage API access Active API tokens
Free shared 10 no per-account cap no 0
Paid shared 1,000 no per-account cap no 0
Dev 1,000 10,000 15 GB yes 1
Dev-pro 1,000 30,000 30 GB yes 10

Deleting a note frees its slot — the cap counts active notes, not lifetime creations. A user whose subscription has lapsed enters read-only mode: existing notes remain readable and exportable forever, but new writes are blocked until they resubscribe.

3. Per-note size limits

  • Title: up to 200 characters; control characters (CR/LF, NUL, etc.) are stripped on save.
  • Rich-text body, plain-text projection: 1 MB on every tier.
  • Rich-text body, raw HTML: 2 MB (defence against markup-inflation as a storage bypass).
  • Plain-text note body:
    • Free / Paid: 1 MB per note.
    • Dev: 1.5 MB per note.
    • Dev-pro: 3 MB per note.
  • Note format is immutable after creation — a rich note cannot become a plain note (or vice versa) without delete-and-recreate.

4. Per-note version history

  • Up to 5 snapshots are kept per note. When a newer save lands beyond the cap, the oldest snapshot is permanently deleted.
  • Capture is debounced. Saves within ~10 minutes of each other share a single snapshot, so a burst of autosaves doesn't burn through the 5-snapshot window inside one editing session.
  • Append-only notes do not generate snapshots — appends are additive, not destructive, so there is nothing to roll back to.
  • Snapshots are accessed via the History link on any editable note and can be restored with one click. The restore captures your current content as a fresh snapshot first, so it is itself reversible within the same 5-snapshot window.

5. Folders

  • Up to 100 folders per account (one is seeded as "My First Folder" at signup).
  • Folder name: up to 80 characters; folder names must be unique within an account (case-insensitive).

6. API (Dev and Dev-pro tiers)

Per-token, per-minute. Each request consumes one slot in the matching bucket; X-RateLimit-* headers on every successful response let clients pace themselves before they trip a 429.

Bucket Dev Dev-pro Counts
Reads 600/min 2,000/min GET, HEAD on /api/v1/*
Writes 60/min 200/min POST/PATCH/PUT/DELETE on /api/v1/* (excluding append + bulk)
Appends 300/min 1,000/min POST /api/v1/notes/:id/append and the by-filename variant
  • API creates and updates are plain-text only; rich-text notes belong to the browser/Trix flow.
  • Bulk endpoint (Dev-pro only): up to 50 notes per call. Counts as one event against the writes bucket regardless of the batch size.
  • Pagination: 50 per page by default, up to 200 via ?limit=N.
  • Stream-addressed filename: up to 200 bytes; no slashes, no control or invisible characters.
  • API tokens: default expiry of 90 days when no expiry is set; user-set expiry can be at most 1 year from now. Tokens revoked manually, or automatically when the account loses API access.
  • Anonymous / bad-token requests on /api/v1/*: 60/min/IP.
  • Request body: oversized writes (over 3 MB for API, 2 MB for browser) are rejected at the HTTP boundary before parsing.

7. Browser-surface rate limits

Designed for legitimate human pacing. Authenticated limits key off the user; anonymous limits key off the IP. 429 rate_limited responses include a Retry-After header so clients can back off cleanly.

  • Sign-in: 10/min/IP, 5/20 min per email.
  • Sign-up: 5/hour/IP.
  • Password reset: 5/hour/IP, 5/hour per email.
  • Confirmation resend: 5/hour/IP, 5/hour per email.
  • Account email change: 3/day per account, 3/day per target email — protects unrelated mailboxes from being used as a confirmation-spam target.
  • Other account updates (name / bio): 10/hour per account.
  • Note saves / autosave: 30/min per account.
  • Per-note PDF / DOCX / TXT downloads: 10/min per account.
  • Full-account export: 2/hour per account; the archive is built in the background and the download link is emailed to you (see §7).
  • Billing portal / plan-change: 5/min per account.
  • Health probe (/up/deep): 60/min/IP.
  • Webhook deliveries (/webhooks/lemon_squeezy): 100/min/IP.

8. Full-account export

  • Triggered from Options → Download all; archive is built off-request by a background worker.
  • A one-time download link is emailed to the address on your account when the archive is ready (usually a few minutes).
  • The link is valid for 24 hours from the moment the build completes; after that the file is removed from our servers and you'll need to request a fresh export.
  • The link only works while signed in to your own account, so a forwarded email cannot be used by anyone else to download your notes.
  • The archive contains .txt, .docx, and .pdf renderings of every rich-text note (or .txt only in software-development mode).

9. Inbound webhooks

  • Lemon Squeezy webhooks only; no public webhook surface for end users.
  • HMAC-SHA256 signature verification on X-Signature; unsigned or tampered payloads are rejected with 401 before parsing.
  • Payload cap: 1 MB. Real LS payloads are well under 10 KB; oversized requests are dropped at the HTTP boundary.
  • Replays of an already-applied delivery are acknowledged with 200 but produce no side effects (signature uniqueness is enforced by a database index).