Terms of Service

Welcome to Fresh Jots. These Terms of Service ("Terms") are a binding agreement between you and Fresh Jots ("we", "us", "our"). They govern your access to and use of our website, applications, JSON API, and related services (together, the "Service"). Please read them carefully. By creating an account or otherwise using the Service, you agree to these Terms and to our Privacy Policy. If you do not agree, do not use the Service.

1. Eligibility

You must be at least 16 years old — the minimum age we enforce at signup — and otherwise old enough to form a binding contract in your jurisdiction to use the Service. If a higher minimum age applies where you live, you must meet that age. If you are using the Service on behalf of an organization, you represent that you have authority to bind that organization, and "you" refers to both you and the organization.

2. Your account

• You provide accurate registration information and keep it current — in particular the email address on your account, which we use for security and transactional notices (see §3).
• You are responsible for safeguarding your password and for every action taken under your account, including any actions taken via API tokens you have issued (see §10).
• You notify us promptly at support@freshjots.com if you suspect unauthorized use of your account or of an API token issued from it.
• One person per account — please don't share logins. A single human may hold only one account unless we agree otherwise in writing.
• If you lose access to the email address on your account, we may not be able to recover the account on your behalf. Keep that address current and reachable.

3. Communications

Some communications are an inherent part of operating an account and you cannot opt out of them while you have an active one:

• Security and account-integrity notices — sign-in confirmations, password resets, email-change confirmations, and alerts about activity that looks unusual.
• Billing and subscription notices — receipts, renewal reminders, payment-failure notices, and any notice we are required to send under consumer-protection law.
• Transactional notices triggered by your own actions — for example, the one-time download link emailed when you request a full-account export (see §15).
• Material changes to these Terms or to the Privacy Policy — see §24.

We do not currently send marketing emails. If we add an opt-in marketing channel in the future, you will be able to subscribe at the time and to unsubscribe from any such message at any time without affecting the transactional communications above. Notices we send to the email address on your account are deemed delivered when sent, regardless of whether you have opened them.

Invitations you send. When you invite someone to a Team workspace under §11, we send a one-time invitation email to the address you provide so they can accept and join. By sending the invitation you represent that you have authority to contact that person about Fresh Jots and that they would reasonably expect such a message from you (a colleague at your organization is fine; a scraped contact list is not — see §8). The recipient is not bound by these Terms unless and until they create an account, and we may decline to send, throttle, or retroactively suspend invitations that look unsolicited.

4. The Service

Fresh Jots is a note-taking service. You can create, edit, organize, pin, rename, and export rich-text and plain-text notes, and read them from any signed-in browser. Dev and Team tiers also expose a programmatic JSON API documented at /docs, and a remote Model Context Protocol (MCP) endpoint that lets AI clients, assistants, and agents you authorize work with your notes and folders — both are governed by §10. The full set of capacity limits and rate limits that apply to your account is set out in Schedule A at the end of this document (also published at /limits). We may adjust those limits from time to time with reasonable notice for material reductions. Full-account exports are produced asynchronously and delivered via a one-time email link valid for 24 hours — see §15 for the full export flow.

5. Beta and pre-release features

From time to time we may make new functionality available on a beta, preview, or experimental basis. Beta features are clearly labelled, are provided "as is" without any service-level commitment, and may be changed, withdrawn, restricted, or rolled out unevenly to different accounts at any time without notice. The disclaimers in §22 and the limitation of liability in §23 apply with full force to beta features. Any feedback you choose to share about a beta is governed by §7.

6. Your content

Your notes are yours. We do not claim ownership of anything you create, upload, or store in the Service ("Your Content"). You are solely responsible for Your Content and for ensuring you have the rights to store and share it.

You grant us a worldwide, non-exclusive, royalty-free license to host, store, reproduce, back up, transmit, display, and create derivative copies of Your Content solely to operate, secure, and improve the Service (for example, replicating notes between servers, generating search indexes, or producing export archives at your request). This license does not authorize us to use Your Content to train machine-learning or AI models, or to sell Your Content to third parties. It ends when you delete Your Content or close your account, except for residual copies in encrypted backups, which expire on our normal backup rotation.

Content you send elsewhere. Our promise not to mine, sell, or train AI on Your Content governs how we handle it on our own systems. It does not, and cannot, govern what happens to Your Content once you yourself route it to a third party — in particular where you connect an AI client or other application through the API, the MCP endpoint, or our OAuth flow (§10), which sends Your Content out of the Service to that provider at your direction and under that provider's terms, not ours.

You retain all moral rights you may have in Your Content under applicable law. Public-share links you choose to generate are subject to the public-notes throttle in Schedule A and may be revoked by you at any time from within the Service.

Public share links. Public sharing is opt-in per note; no note is shared unless you explicitly turn sharing on for it. Public notes live at unguessable URLs (the share token carries 43 url-safe characters of entropy), and the rendered page is served with a noindex robots directive by default to discourage search-engine inclusion. Anyone in possession of the URL can read the note without signing in — treat the URL itself as the access control. Revoking a share takes effect immediately on our side (the URL returns 404), but copies a visitor has already loaded, cached in their browser, archived, or republished are outside our control.

Version history. For editable notes we keep a small, capped number of recent revisions per note so that an accidental save can be rolled back; older snapshots are pruned automatically as new ones land. The exact cap and the snapshot-debounce window are set out in Schedule A. Append-only notes do not generate snapshots, since appends are additive rather than destructive.

Team-shared content. Notes you author inside a Team workspace belong to the workspace, not to you personally. Every accepted member of the team can read, edit, and export those notes within the team's permissions; if you leave the team or close your account, your team-authored notes remain with the workspace and are reassigned to the team owner — see §15 for the full deletion-and-departure flow.

7. Feedback

If you send us suggestions, feature requests, bug reports, or other feedback, you grant us a perpetual, irrevocable, royalty-free license to use it without restriction or compensation. You are not obligated to send us feedback, and we are not obligated to act on it or to keep it confidential.

8. Acceptable use

You agree not to, and not to attempt to:

• Store, upload, or distribute content that is illegal, infringing, defamatory, fraudulent, or that you do not have the right to share — including content that sexually exploits minors, which we report to the relevant authorities.
• Use the Service to harass, threaten, dox, stalk, or otherwise violate the rights or privacy of others.
• Impersonate any person or entity, or misrepresent your affiliation with one — including in profile fields, note content, or shared links.
• Upload malware, execute scripts against the Service, or use it to distribute spam or unsolicited messages.
• Probe, scan, reverse engineer, or attempt to disrupt, overload, or test the security of the Service or its infrastructure, except as expressly permitted by a published responsible-disclosure policy.
• Circumvent billing, rate limits, free-plan limits, the per-tier capacity limits in Schedule A, the API limits in §10, or any other access control — or use automated means to create accounts.
• Interfere with another user's lawful use of the Service, or use the Service to interfere with any third-party service.
• Resell, sublicense, or provide the Service to third parties without our prior written consent.
• Use the Service's software, other users' data, or non-public details of how the Service works to train machine-learning models, to benchmark it, or to build a competing product. (This does not stop you from connecting an AI client to your own account, under §10, to work with your own notes.)
• Use the Team-tier invitation flow (§11) to send unsolicited messages, to invite recipients who have not asked to be invited and would not reasonably expect an invitation from you, or to re-target an invitation that the recipient has previously declined or ignored.
• Use the Service in violation of applicable export-control or sanctions laws (including those administered by OFAC, the European Union, and the United Kingdom), or make it available to persons or entities subject to such restrictions.
• Use the Service in life-critical, life-supporting, medical, aviation, nuclear, or other safety-critical contexts where failure of the Service could lead to death, personal injury, or environmental damage. The Service is not designed, built, or warranted for such use.

We may investigate suspected violations and cooperate with law-enforcement requests as required by law. Repeated or material breach of this section is grounds for suspension or termination under §14.

9. Free plan

Every account can keep up to 10 notes free, indefinitely — no trial clock, no card required. When you reach the cap, an active subscription is required to create additional notes. Reading, editing, and exporting your existing notes remain available on any account, and deleting a note frees its slot. Subscription tiers (Personal, Dev, Team) raise this and other caps; the full breakdown is in Schedule A at the end of this document.

Trial overflow. The optional 14-day API trial temporarily raises the free account's allotment (currently 100 notes and 300 MB). Notes created above the free cap during a trial remain readable and exportable for 30 days after the trial ends; if the account is still on the free plan at that point, notes beyond the oldest 10 are moved to the trash (where they remain recoverable for a further 30 days) and then permanently deleted. Starting a subscription before the deadline keeps everything in place.

10. API access and tokens

Dev and Team tiers expose a JSON API documented at /docs. Access is authenticated with bearer tokens you generate from your profile. The number of active tokens you can hold per account, the per-token rate limits, and the request and payload size limits are set out in Schedule A. A remote Model Context Protocol (MCP) endpoint at /mcp presents the same note and folder operations to AI clients and agents and is authenticated either with the same bearer tokens or, for click-to-connect AI clients, through our OAuth 2.1 flow. Over the OAuth flow, every account may connect an AI client to read its notes; write operations (create, append, edit, move, delete) require an active subscription (Personal or higher), and the token-driven JSON API remains a Dev and Team feature. In addition, any active subscriber — the Personal tier included — may hold one append-only browser-extension token bound to a single note (see the bullet below).

• Tokens are credentials. Treat them like passwords: do not share them, embed them in client-side code, or commit them to public repositories. Anyone in possession of a token can act as your account up to the API's rate and capacity limits.
• Browser-extension token. Independent of the tier limits above, every active subscriber (including Personal) may hold one append-only token, scoped to a single note, for the browser-extension clip utility. It can only append to the one note it is bound to — it cannot read, edit, or delete that note or reach any other endpoint — is counted and rate-limited separately (Schedule A), and is revoked automatically if the subscription lapses.
• You are responsible for traffic. Every request authenticated by your token counts against your account's limits, applies to your stored content, and is your responsibility — whether issued by you, by an integration you authorized, or by a third party who obtained your token.
• MCP endpoint and connected applications. Through the MCP endpoint, or by authorizing an application in our OAuth flow, you can connect AI clients, assistants, agents, and other tools to your account (or, on the Team tier, to your workspace). A connected application can list, read, create, append to, edit, move, and delete notes and folders, limited by the scope of the credential it uses — a read-only or single-note token restricts it accordingly. Deletions made this way act on your live data and may be irreversible. Authorizing a connected application, and choosing the scope you grant it, is your decision and your responsibility: you are responsible for what it does under the access you grant, you should grant it no more access than it needs, and you should review its own terms and privacy policy before connecting it. We do not vet, endorse, or control connected applications and are not responsible for their availability, security, or conduct.
• Third-party AI clients and your notes. When a connected application is, relies on, or forwards your notes to a third-party AI or large-language-model provider, connecting it sends your note content out of the Service to that provider, at your direction and at your own risk. What that provider does with your content — including whether it logs, retains, or trains on it — is governed by its terms and privacy policy, not by ours and not by our undertaking in §6, which binds only our own systems. You are responsible for ensuring any such transmission is lawful and that you have the right to make it, especially where your notes contain personal data of others or confidential material.
• Revocation. You can revoke any token from your profile at any time, and withdraw a connected application's access — by revoking the token it uses or, for an OAuth connection, by disconnecting it from that client or asking us to revoke it. We may also revoke a token, withdraw a connected application's access, or revoke all credentials for an account on reasonable notice if their use threatens the integrity, security, or availability of the Service, or appears to be circumventing rate or capacity limits.
• Idempotent retries. The API accepts an Idempotency-Key header on mutating requests so that retries are safely no-op replays. Replays that present the same key but a conflicting body are rejected; otherwise idempotency is opt-in and writes without the header proceed normally.
• Real-time browser sync. See §16 for the deliberate limit on browser propagation of API writes to open editor tabs.
• Deprecation. If we remove or materially change an API or MCP endpoint, we will give at least 30 days' notice through the Service or by email to the address on the account. The MCP endpoint and the OAuth connection flow are newer, still-evolving parts of the Service and are offered "as is"; we may change or restrict them, including with shorter notice where reasonable.

11. Subscriptions and billing

We offer annual plans in three paid tiers (Personal, Dev, Team). Team is a multi-seat tier; the seat-pack add-on charge is part of the Team subscription on each renewal. Payment is handled by our payment processor, Lemon Squeezy, which is also the merchant of record for your purchase. Their terms and privacy policy apply to the payment relationship in addition to ours.

• Prices, currencies, and applicable taxes or VAT are shown at checkout. You authorize recurring charges for the plan you select.
• Subscriptions renew automatically at the end of each billing period until you cancel.
• We do not see or store your full card number. Lemon Squeezy returns only a customer and subscription identifier to us.
• If a charge fails, we may retry it, suspend paid features until payment is received, and, after reasonable notice, downgrade or close the account. Notes you have already created remain readable and exportable in line with §15.
• Receipts and renewal reminders are sent to the email address on your account as transactional notices under §3.
• Team tier seats include the buyer. On the Team tier, the account that purchases the subscription (the team owner) counts as one of the paid seats. A purchase of N seats covers the owner plus N−1 invited members; the 2-seat minimum therefore covers the owner plus one invited member, and the maximum is 25 seats. Seat additions and removals via the billing portal apply to the same total — the owner's seat is not a separate, free seat.
• Team-tier roles. Each accepted member holds one of three roles: owner (the buyer; can do everything; in the current version of the Service ownership cannot be transferred to another member — a future release will add this), admin (can invite or remove members, manage the team's billing through the portal, and view the team audit log), and member (can read, write, and export team notes; create team-scoped API tokens within Schedule A's per-team cap; and acknowledge team-scoped alerts).
• Team invitations. Invitations are sent to an email address. The accept link is single-use and expires 14 days after sending; an expired link is rejected and a new one must be issued by an owner or admin. A user may hold an accepted membership in at most one team at a time; we will refuse a second-team acceptance until the first membership is removed. Removing an accepted member from a team takes effect immediately and revokes their access to team notes and team API tokens issued from the workspace.
• Team subscription lapse. If a Team subscription is cancelled, expires, or fails final renewal, the entire team workspace enters read-only mode for every member: notes, folders, exports, and the team audit log remain accessible, but new writes, new invitations, and new API tokens are blocked until the subscription is reactivated. The 12-month read-only / purge schedule in §15 applies to a lapsed Team workspace in the same way it applies to a personal account.

12. Cancellation, refunds, and plan changes

You can cancel your subscription at any time from the billing portal. Cancellation stops the next renewal and takes effect at the end of your current annual term. We do not refund the unused portion of an annual term.

Except where refunds are required by applicable consumer-protection law (including the statutory rights described in §20), all fees are non-refundable. We may offer refunds at our discretion.

You can change your tier at any time from the billing portal; an upgrade takes effect immediately, a downgrade takes effect at the end of the current billing period. If a downgrade would put you above the new tier's caps in Schedule A, we will not delete content — you will be in read-only mode for new writes in the affected category until you reduce usage below the new cap or upgrade again.

We may change pricing, plan features, or plan availability for future billing periods with at least 30 days' notice; the new price applies on your next renewal. Mid-term price changes do not apply to a billing period you have already paid for.

13. Third-party services

The Service relies on third parties to operate, including the payment processor described above, a transactional email provider, and a cloud hosting and database provider. We are not responsible for the content, policies, or practices of third-party services, and your use of them is governed by their own terms. Our handling of personal data by these sub-processors is described in the Privacy Policy.

Applications you connect are different. A third-party application or AI client that you choose to connect to your account — through an API token, the MCP endpoint, or our OAuth flow (§10) — is not one of our sub-processors. It acts at your direction, under its own terms and privacy policy, and the data it receives is sent to it because you asked us to. You are responsible for what you connect and for the data it receives; you can disconnect it at any time as described in §10.

14. Suspension and termination

You may close your account at any time from your profile page, or by emailing support@freshjots.com from the address on your account. Closing your account cancels any active subscription as of the end of the current billing period.

We may suspend or terminate your account, remove content, or restrict features if you violate these Terms (in particular §8), if your account poses a security, legal, or abuse risk to the Service or to other users, if a payment fails and is not cured after notice (see §11), or if we are required to do so by law. Where the issue can reasonably be remedied, we'll try to give you notice and a chance to correct it first. Where it cannot — for example, an active security or legal threat — we may act first and notify you afterwards.

A suspension is not a deletion: while your account is suspended you may still be able to sign in to retrieve a full export under §15, unless the suspension is for active abuse or a legal hold. If we terminate your account, we will tell you the reason at the time of action unless doing so is unsafe or prohibited by law.

15. Your data after termination

Before closing your account, you can request a full export of your notes at any time from Options → Download all. Exports are produced asynchronously: when you request one, we build the archive in the background and email a one-time download link to the address on your account. The link is valid for 24 hours; after that, the file is automatically removed from our servers and you can request a fresh export. You consent to receive these transactional emails as part of using the export feature (see §3).

After your account is closed, your notes are deleted from our production database; copies may remain in encrypted backups until they expire on our normal backup rotation. We retain the minimum billing and log records required to meet legal, tax, and accounting obligations, and aggregated, non-identifying analytics about Service usage. Specific retention periods are set out in the Privacy Policy.

Lapsed paid accounts. If you previously held a paid plan and your subscription becomes inactive (cancellation, expiry, or final payment failure), your account moves to read‑only mode: you can sign in, read your notes, and request a full export at any time, but you cannot create or edit notes until you resubscribe. We retain your notes in this read‑only state for twelve months from the date your subscription went inactive. About thirty days before that window closes, we email a one‑time reminder to the address on your account. If the subscription has not been reactivated by the end of the twelve‑month window, the account and all its notes are permanently deleted on the schedule described in the paragraph above. Reactivating at any time before the window closes restores full access and resets the retention clock.

Team workspaces and member departures. Notes authored inside a Team workspace (§11) belong to the workspace, not to the individual member who wrote them. When a team member closes their account or is removed from the team, their team-authored notes are reassigned to the team's owner so the workspace's content is preserved across the departure; the member's personal notes (those outside any team) are deleted along with their account on the schedule above. If a Team subscription itself lapses, the workspace as a whole enters the same twelve‑month read-only window described above and the same one‑time reminder is sent to the team owner; if the window closes without reactivation, the team and all its notes and folders are permanently deleted. A team owner can request an export of the team workspace on the same flow that a personal account uses.

16. Service changes and availability

We may add, change, or remove features, and we may release new versions of the Service, at any time. We aim for high availability but do not guarantee that the Service will be uninterrupted, error-free, or secure against every threat. Maintenance, upgrades, or factors beyond our reasonable control may cause temporary unavailability. We do not offer a contractual service-level agreement; planned maintenance windows, where they affect availability, will be announced through the Service or by email where reasonably practicable.

Real-time browser propagation of API writes is limited to append-only notes. If you have a note open in the web UI while another client (e.g. a script using your API token) writes to it, the browser tab is updated in place only for notes that are append-only — those use a per-user, per-note streaming channel that replaces the body as new content lands. Editable (CRUD) notes updated through the API are not pushed to an open browser tab; the tab will continue to show the previous content until the page is refreshed. This is a deliberate design choice to avoid clobbering in-flight, autosaved edits in the browser editor.

Dead-man's-switch alerts (Dev and Team). An append-only note may optionally be configured with a deadline so that if no new entry is appended within the configured window (between 1 hour and 30 days), an alert is dispatched. Personal alerts are sent to the email on the note (or, by default, the account email); Team workspaces may instead direct alerts to a list of email addresses or to a webhook URL the team has configured. Alert delivery is best-effort: it does not constitute a service-level agreement, and a Service incident, a third-party email or webhook outage, or a misconfigured destination may cause an alert to be missed entirely. You are responsible for the destination — including securing any webhook URL you provide, restricting who can read messages sent to a list address, and keeping any account email valid and monitored — and you should not rely on this feature as the sole safety net for any task whose failure would cause material harm. Notification content may include the note's title and metadata in addition to a link back to the Service.

17. Your own backups

We take reasonable steps to keep your notes safe, including regular encrypted backups. Even so, the only way to be sure you have an offline copy of your notes is to export them yourself. Because exports are delivered via a time-limited email link (see §15), please save the resulting archive locally before the 24-hour link expires. If anything you write is irreplaceable, please request and save an export periodically.

18. Intellectual property

The Service, including its software, design, trademarks, logos, and text (other than Your Content), is owned by us or our licensors and is protected by intellectual-property laws. We grant you a limited, non-exclusive, non-transferable, revocable license to use the Service for its intended purpose under these Terms. The corresponding end-user licence and its restrictions are set out in full in the End-User License Agreement; in case of conflict between this section and the EULA on a licence-scope question, the EULA controls (see §26). No other rights are granted by implication, estoppel, or otherwise.

19. Copyright complaints (DMCA)

We respect copyright. If you believe content stored on the Service infringes your copyright, send a notice to support@freshjots.com with the subject line DMCA Notice, and include:

• Your physical or electronic signature.
• Identification of the copyrighted work you claim has been infringed.
• Identification of the allegedly infringing material and a link or description sufficient for us to locate it.
• Your contact information (address, telephone number, email).
• A statement that you have a good-faith belief that the use is not authorized by the copyright owner, its agent, or the law.
• A statement, under penalty of perjury, that the information in the notice is accurate and that you are the owner or authorized to act on behalf of the owner.

We may remove or disable access to allegedly infringing material and terminate the accounts of repeat infringers. If you believe your content was removed in error, you may send a counter-notice to the same address. Bad-faith notices may result in liability for damages under applicable law. Outside the United States, we follow equivalent notice-and-takedown procedures where available and respond to lawful takedown requests under the law of the requesting jurisdiction.

20. Consumer rights (EU / UK)

If you are a consumer in the European Union, the United Kingdom, or another jurisdiction with mandatory consumer-protection laws, nothing in these Terms limits rights you cannot waive by contract. In particular:

• Right of withdrawal. You have a statutory right to withdraw from a paid subscription within 14 days of purchase without giving a reason. Because Fresh Jots is a digital service supplied immediately, we ask at checkout that you consent to performance beginning before the withdrawal period ends and acknowledge that you will lose the right of withdrawal once performance has started and you have benefited from the Service. Where the right still applies, contact support@freshjots.com within 14 days of your purchase and we will refund you in line with applicable law.
• Statutory warranties. The disclaimers in §22 and the liability cap in §23 apply only to the extent permitted by law. Statutory warranties of conformity, satisfactory quality, and fitness for purpose apply where required.
• Forum. Consumers may bring proceedings in the courts of their country of residence where applicable law so provides, and may rely on mandatory provisions of the law of that country.
• Online dispute resolution. EU consumers may also use the European Commission's Online Dispute Resolution platform. We are not, however, obliged to participate in ODR proceedings before a consumer arbitration body.

21. Indemnification

You will defend, indemnify, and hold us harmless against claims, losses, and costs (including reasonable legal fees) arising from (a) Your Content, (b) your use of the Service in breach of these Terms, (c) your violation of law or of any third-party rights, or (d) misuse of an API token issued from your account (see §10). We may assume the exclusive defense of any matter subject to this section, in which case you will cooperate with us. This section does not apply to consumers to the extent prohibited by applicable law.

22. Disclaimers

To the fullest extent permitted by law, the Service is provided "as is" and "as available", without warranties of any kind, whether express, implied, or statutory — including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, and uninterrupted or error-free operation. We do not warrant that the Service will meet your requirements, that any defects will be corrected, or that data you store will not be lost or corrupted. Some jurisdictions do not allow the exclusion of certain warranties; in those jurisdictions, the above exclusions apply to the extent permitted.

23. Limitation of liability

To the fullest extent permitted by law, in no event will we, our officers, employees, or contractors be liable for any indirect, incidental, special, consequential, or punitive damages, or for lost profits, lost revenues, lost data, loss of goodwill, or business interruption, whether based on contract, tort (including negligence), statute, or any other legal theory, even if we have been advised of the possibility of such damages.

Our aggregate liability arising out of or related to the Service or these Terms, across all claims combined, will not exceed the greater of (a) the amounts you paid us for the Service in the twelve months preceding the event giving rise to the liability, or (b) USD 100. Nothing in these Terms excludes or limits liability that cannot be excluded or limited under applicable law (for example, liability for fraud, gross negligence, death, or personal injury caused by our negligence, or — for EU/UK consumers — liability that cannot be excluded under mandatory consumer law; see §20). Each provision of this section is severable: if one carve-out is held unenforceable, the remainder of the cap continues to apply.

24. Changes to these Terms

We may update these Terms from time to time. Each version has an identifier shown at the top of this page (driven by the CURRENT_TERMS_VERSION constant in the application). If changes are material — for example, a change to fees, to the licence in §6, to the limits in Schedule A in a way that materially reduces what your tier receives, or to the dispute-resolution mechanics in §25 — we'll notify you by email or through the Service at least 14 days before they take effect, unless a shorter period is needed for legal or security reasons.

Non-material changes (typographical fixes, clarifications, reorganization that doesn't change rights or obligations) take effect on publication. Your continued use of the Service after the effective date means you accept the updated Terms. If you don't agree, you may close your account before the new Terms take effect, and §15 governs the export of your data.

25. Governing law and dispute resolution

These Terms are governed by the laws of North Macedonia, Skopje court, without regard to conflict-of-laws rules. The courts of North Macedonia, Skopje court have exclusive jurisdiction over any dispute arising out of or in connection with these Terms, subject to the consumer-forum rule in §20.

Amicable resolution comes first — and it is a required step. Almost every problem with a service like this turns out to be an outage, a billing slip, a misunderstanding, or a bug, and almost all of them are resolved fastest by talking to us. So before either you or we begin any formal legal proceeding arising out of or relating to the Service or these Terms, the party raising the dispute must first give the other written notice of it and then attempt, in good faith, to resolve it directly. You send that notice to support@freshjots.com; we send ours to the email address on your account. A valid notice describes the issue, the facts behind it, and the resolution the notifying party wants.

For 60 days after a notice is delivered, both sides will negotiate in good faith and neither side will commence a formal claim. Completing this 60-day informal-resolution period is a condition that must be satisfied before suit, and any limitation or filing deadline applicable to the claim is paused while the period runs. If the dispute remains unresolved after 60 days, the parties may, by mutual agreement, refer it to non-binding mediation before a single mediator and share the mediator's fees equally, before resorting to the courts. We will handle every notice promptly and in good faith and will not use this process to delay a legitimate claim.

This required first step does not apply to, and does not delay: (a) an application for an injunction or other urgent equitable relief; (b) a claim to protect intellectual property; (c) a claim that may be brought in a small-claims court; or (d) any right an EU/UK or other consumer holds under mandatory law, including the right to bring proceedings in, and rely on the law of, their country of residence (§20) and to use the EU Online Dispute Resolution platform. Nothing in this section waives, or asks you to waive, any right you cannot waive by contract: it sequences how a dispute is raised, it does not remove your access to a court.

26. General

• Entire agreement. These Terms, the Schedule A incorporated by reference, the Privacy Policy, and the End-User License Agreement are the entire agreement between you and us about the Service and supersede any prior agreement on the same subject.
• Order of precedence. If there is a conflict between (a) the figures in Schedule A and explanatory text in these Terms, the figures in Schedule A control; (b) these Terms and the EULA, the EULA controls for matters within its scope (licence grant, permitted use, restrictions); (c) these Terms and the Privacy Policy, the Privacy Policy controls for matters within its scope (personal-data handling). In all other cases these Terms control.
• Survival. Sections 6 (your content licence to us), 7 (feedback), 18 (intellectual property), 19 (DMCA), 21 (indemnification), 22 (disclaimers), 23 (liability cap), 25 (governing law), and this §26 survive termination of these Terms to the extent necessary to give effect to their purpose.
• Severability. If any provision is held unenforceable, the rest of the Terms remain in force, and the unenforceable provision will be modified to the minimum extent necessary to be enforceable while preserving its intent.
• No waiver. Our failure to enforce a right is not a waiver of that right, and a waiver on one occasion does not waive any other right or future enforcement.
• Assignment. You may not assign these Terms without our written consent, and any attempted assignment is void. We may assign them in connection with a merger, acquisition, reorganization, or sale of all or substantially all of our assets.
• Notices. We may send notices to the email address on your account; you may send notices to support@freshjots.com. Notices are deemed delivered when sent to the address on file.
• Force majeure. We are not liable for delays or failures caused by events beyond our reasonable control, including network outages, denial-of-service attacks, third-party-provider failures, natural disasters, war, civil unrest, or government action.
• No agency. These Terms do not create any partnership, agency, joint venture, fiduciary, or employment relationship.
• Headings. Section headings are for convenience only and do not affect interpretation.
• Language. The English-language version of these Terms is the controlling version. Translations are provided for convenience only.

27. Contact

Questions about these Terms? Email support@freshjots.com. Privacy and data-deletion requests go to support@freshjots.com. DMCA notices use the same privacy address with the subject line described in §19.

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 issues — for example a withdrawal request under §20, a billing dispute, a DMCA notice, or a privacy / data-deletion request — are prioritized; general feedback and feature requests may go unanswered. Nothing in this section limits any right you have under mandatory consumer-protection law.