Terms and conditions

1. Who these terms are between

APIRecap is operated by MOLEBYTES LTD, trading as APIRecap (“we”, “us” and “our”).

• Company number: 17406550.
• Registered in England and Wales as a private limited company.
• Privacy enquiries: hello@apirecap.com.
• Support and legal notices: hello@apirecap.com.

These terms govern access to APIRecap’s website, hosted application and publishing API (the “service”). “You” means the business or professional individual responsible for the workspace (the “customer”) and, where the context requires, its authorised users. An order agreed with us may set out additional subscription details. The workspace Owner accepts for the customer; other team members acknowledge the user obligations and do not, merely by accepting an invitation, bind the customer to a new agreement.

The service is for business and professional use only, including use by sole traders and freelancers in their work. You must be at least 18 and, when acting for an organisation, authorised to enter this agreement on its behalf. Customers must ensure their team members use the service in accordance with these terms.

Our privacy policy explains how personal information is handled. Accepting these terms does not give blanket consent to optional marketing or cookies.

This agreement starts when you accept an identified version of these terms through a recorded acceptance step or an agreed written order. Optional analytics and marketing choices are separate.

2. What APIRecap provides

APIRecap hosts OpenAPI and Markdown documentation, records document versions, identifies changes, suggests release-note wording, provides controlled reader access and sends approved release alerts to confirmed subscribers. Features and allowances are described on the pricing page and in any agreed order.

You are responsible for maintaining your API and supplying accurate documents. APIRecap analyses the documents you publish; it does not inspect your live API to establish that the documentation matches deployed code. If you want documents to represent a production release, arrange for publishing to follow your successful deployment.

APIRecap is a documentation and release-communication service. It is not an archive you should rely on as your only copy of source documents. Keep your own copies of important content and integration instructions.

3. Accounts, teams and publishing keys

Provide accurate account details and keep a working contact email. Protect passwords, social sign-in accounts, publishing keys and share links. Tell us promptly if you believe an account or key has been compromised.

The workspace Owner manages membership, roles, project access and external sharing. Editors can publish and manage content within their permissions. Signed-in Readers can open only the projects granted to them. The customer is responsible for authorised team activity and for removing access when it is no longer needed.

Use an individual account for each team member. Use publishing keys only for authorised integrations, store them securely and revoke them when appropriate. A change to a member’s role or workspace access may also change what their keys can do.

4. Your content remains yours

You retain your rights in uploaded API specifications, Markdown documents, logos, release notes and other customer content. These terms do not transfer ownership of that content to us.

You grant us a limited, non-exclusive permission to store, copy, process, render and transmit your content as needed to provide and secure the service, follow your sharing instructions and fulfil our legal obligations. Service providers may perform those activities for us subject to the relevant protections. This permission does not allow us to sell your documentation or use it in advertising.

You must have the rights and permissions needed to upload the content and share it with your chosen readers. Use synthetic examples where possible. Remove live credentials and unnecessary personal information before publishing.

You must not use the service to store special-category or criminal-offence information, payment-card details or live credentials unless we expressly agree suitable safeguards in writing.

Subject to section 13, you will cover reasonable damages and defence costs finally awarded against us, or included in a settlement you approve, from a third-party claim caused by your customer content infringing intellectual-property rights or your unauthorised disclosure of personal or confidential information. This applies only to the extent caused by your breach, and not to our own fault. We will promptly notify you, allow reasonable control of the defence, cooperate and take reasonable steps to limit loss. No settlement may admit fault for, or impose obligations on, the other party without its consent.

We retain rights in the APIRecap application, branding and original site material. Open-source components remain subject to their own licences. Nothing in these terms overrides rights granted under those licences or rights that the law does not allow us to restrict.

5. Sharing documents and communicating with readers

Listed APIs can be opened through a project share link. Unlisted APIs require their own share link. Private APIs require authorised, signed-in team access. The Owner controls external sharing and can restrict historical documents and changes.

A valid external link grants access by possession. It can be forwarded, so it should be shared only with intended recipients. Turning off sharing or revoking a link stops future access through that route; it cannot recall copies already saved or messages already delivered.

Release emails are sent to confirmed subscribers after the first approval of a version’s release note, subject to current access and subscription status. You are responsible for the accuracy and lawfulness of the approved note and for using subscriber information only for authorised purposes. Do not use release alerts to send unrelated advertising.

Retained versions have their own URLs. Deletion, revoked access or reader settings may make those URLs unavailable. Owners and Editors should check the effect of deleting content or changing the current version before doing so.

6. Change detection and AI-assisted notes

Automated change facts and AI suggestions help you prepare a release update. They can be incomplete or incorrect. A breaking-change flag is not an exhaustive compatibility assessment, and the absence of a flag does not guarantee that an integration will continue to work.

Review the source comparison, check the suggested wording and add any context or migration instructions your readers need. An Owner or Editor must approve the client-facing note. You remain responsible for the approved communication and for testing your API.

For CI/API publishing, the new document becomes current before the note is approved. For web uploads, the review step occurs before publication. Approval of a note is not approval of, or a gate on, your production deployment.

The privacy policy’s AI section describes the change facts sent to Amazon Bedrock.

7. Acceptable use

You may use APIRecap to document your own APIs and those you are authorised to manage for clients. You must not:

• Upload unlawful, infringing, deceptive or malicious material, or disclose another person’s confidential or personal information without authority.
• Attempt to access another workspace, guess or harvest share tokens, steal credentials or bypass permissions, rate limits or plan allowances.
• Disrupt the service, knowingly overload it, distribute malware or use it for spam, phishing or fraud.
• Sell access to another customer’s documents or scrape private content without permission.
• Test security in a way that risks other users’ information or service availability without prior agreement.

Report suspected vulnerabilities to the support contact in section 1, with enough detail for us to investigate and without including other users’ data.

8. Subscription fees and renewal

The workspace plan costs $6.99 USD per month, plus applicable taxes, unless a different price is agreed in your order. The total payable and plan allowances are shown before you subscribe. Paid subscriptions renew automatically each month unless cancelled before renewal. Payments are processed by Stripe. You authorise Stripe to collect the agreed recurring fees.

We will give you at least 30 days’ notice before a price increase applies to your subscription. You can cancel before renewal at the new price. An increase will not apply retrospectively to a period you have already paid for.

If a payment fails, we will notify you and give you seven days from that notice to update your payment method or settle the balance before suspending paid access. Section 12 still permits immediate restrictions for urgent security threats or unlawful use.

Billing is not yet enabled. These payment rules apply when you enter a paid subscription.

9. Cancellation and refunds

You can cancel at any time by contacting hello@apirecap.com, or through a billing cancellation option where provided. Cancellation stops the next renewal; access continues until the end of the current paid period.

We do not normally refund a partially used month. Exceptions include billing errors, refunds required by law and our failure to provide the paid service. We will review billing disputes fairly. Cancellation and a request to close or erase a workspace are separate actions.

If we discontinue a paid service during a prepaid period, or you terminate because of an unresolved material breach by us, we will refund the unused portion of the affected prepaid fees.

Nothing here removes mandatory rights or remedies. If consumer law applies to your purchase despite the service’s intended business use, any applicable cancellation, refund and service-quality rights continue to apply.

10. Privacy, data processing and confidentiality

Each party must comply with the data protection laws applicable to its activities. You are responsible for establishing the right to provide personal information to the service and for issuing notices and obtaining consent where required.

Where we process customer personal information on your behalf, the data processing agreement must be agreed with you and takes precedence over these terms for that processing.

Each party will protect the other’s confidential information using reasonable care and disclose it only to people who need it for the service, are bound by confidentiality duties, or must receive it by law. This does not cover information already lawfully known, independently developed or lawfully made public. Sharing content with your selected readers authorises that disclosure.

Application hosting and storage are in AWS Europe (London), eu-west-2. The privacy policy explains the distinction between that storage and external service-provider processing.

11. Service availability and changes

We will provide the service with reasonable care and skill. Maintenance, faults, network problems and events outside our reasonable control can affect availability. No particular uptime percentage, recovery time or support response time applies unless we agree it in writing.

We may improve or change the service. For a material reduction in paid functionality, we will give reasonable advance notice and explain your options. If a change materially prevents the agreed use during a prepaid period, contact us to resolve it or arrange cancellation and an appropriate refund for the affected unused period.

Third-party services, including sign-in and email providers, may have their own terms and outages. We remain responsible for obligations the law or our agreement places on us.

12. Suspension, termination and your documents

We may restrict access where reasonably necessary to address a security threat, unlawful content, non-payment or a material breach of these terms. Restrictions will be proportionate and explained where lawful. Non-payment restrictions follow the seven-day notice period in section 8. For other material breaches that can be corrected, we will allow the 14-day remedy period below before suspension or termination, except for urgent security threats or unlawful use.

For a material breach that can be corrected, either party may terminate if the breach remains unresolved 14 days after written notice describing the issue. Immediate, proportionate suspension may be necessary to address an urgent security threat or unlawful use. Termination may be immediate where continued service would be unlawful or the breach cannot be corrected.

Closing a workspace immediately stops ordinary access, share links and integrations. The Owner can reopen it within 30 days; after that deadline, recovery and export are blocked and the hourly deletion process removes its data from the live application. RDS snapshots expire separately as described in the privacy policy. Keep your own source documents.

The Owner can download retained workspace data in Account settings, or from the closure page during the recovery period. The download includes original documents and relevant metadata in a machine-readable form and excludes APIRecap authentication secrets. Requests for other data or return during a service suspension can be sent to hello@apirecap.com; we verify authority and arrange a secure transfer. Request return before permanent deletion; erased data cannot be returned. This limited download access does not reopen a closed workspace.

13. Responsibility and limits of liability

Nothing in these terms excludes or limits liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, or any other liability that cannot lawfully be excluded or limited. Mandatory statutory rights remain unaffected.

Subject to those protections, and only to the extent lawful and reasonable for this business service, neither party is liable to the other for indirect or consequential loss, or loss of profits, revenue, business opportunities or anticipated savings. Reasonable direct costs of restoring customer data are not excluded merely because they relate to data loss; the applicable cap below still applies.

Each party’s total aggregate liability arising from or connected with the service, whether in contract, negligence or otherwise, is limited to the greater of $1,000 USD or the fees paid or payable for the affected workspace in the 12 months immediately before the first event giving rise to the claim.

For breaches of confidentiality or data-protection obligations, and the customer-content third-party claims described in section 4, the corresponding aggregate cap is instead the greater of $5,000 USD or twice those 12-month fees. These caps are not cumulative: all capped claims together remain subject to the highest applicable cap, and related claims are treated as arising from the same first event. A different cap may be expressly agreed in a written order.

Neither cap limits fees properly owed, the liabilities in the first paragraph, an individual’s statutory right to compensation, a regulator’s powers or any statutory contribution or liability that cannot lawfully be restricted. Each party must take reasonable steps to limit its loss. The data processing agreement takes precedence where data-protection law requires.

14. Updates and general terms

We may update these terms to reflect changes to the service, law or business. Material changes will be notified in advance with an effective date and an opportunity to cancel where appropriate. Changes needed urgently for security or legal reasons may take effect sooner, with notice as soon as reasonably possible.

An agreed order takes precedence over these terms where it expressly varies them. If a provision cannot be enforced, the remaining provisions continue so far as the law permits. A delay in enforcing a right does not by itself waive it.

Neither party may transfer the agreement in a way that materially reduces the other party’s rights without consent, except as permitted by an agreed order or applicable law. We may transfer it with the business if the successor assumes our obligations and we notify you.

Notices may be sent to the account contact or to our contact in section 1. Keep that contact information current.

15. Governing law and complaints

Please contact us first about a complaint so we can investigate and try to resolve it. This does not prevent either party seeking urgent relief or exercising a statutory right.

These terms and disputes arising from the agreement are governed by the law of England and Wales, with disputes subject to the courts of England and Wales. Any mandatory rights or jurisdiction rules that apply elsewhere remain unaffected.