1. About these terms
These Terms and Conditions cover the BugCapsule website and participation in its design-partner service, subject to any signed pilot agreement. “You” means the person or organisation using the service. If you act for an organisation, you must have authority to agree on its behalf.
A separate signed agreement controls where it conflicts with these terms. SDKs and other distributed software remain subject to the licences included with their repositories or packages. Browsing this website or composing an enquiry does not by itself enrol you in a pilot or create a paid subscription.
2. Pilot scope and availability
BugCapsule captures application failures into capsules that teams can inspect, replay, and verify. The design-partner pilot described on this site is a four-week collaboration for QA and internal builds, with one project and integration support as agreed during onboarding.
Pilot features, supported platforms, limits, and delivery schedules may change as the product develops. Production capture is outside the described pilot scope unless separately agreed. There is no general availability or uptime guarantee in these website terms; any service commitments must be set out in your agreement.
3. Access and credential security
You are responsible for activity using your project credentials and for ensuring that authorised users follow your agreement. Keep secret and administrator keys out of client builds, public repositories, issue reports, and shared screenshots. Restrict access, rotate credentials when access changes, and promptly report suspected compromise through your pilot contact.
Share links are bearer links: anyone with a valid link can download its capsule. Choose suitable expiry periods and revoke links when no longer needed. You remain responsible for deciding who may receive your data.
4. Your data and integration responsibilities
You retain your rights in the application code, data, and capsule content you provide. You authorise the processing needed to deliver the agreed service, including storing capsules and making them available to your authorised users and chosen share-link recipients.
- Have the permissions and lawful basis needed to record and upload data, and provide any required notices or consent flows.
- Use test data where possible, minimise recorded information, configure redaction and exclusions, and inspect sample capsules before rollout.
- Do not upload passwords, payment credentials, or other sensitive information that the agreed environment is not approved to handle.
- Set appropriate retention and keep any independent copies you need before deletion or termination.
- Agree any required data processing terms before sending personal data.
The Privacy Policy explains the documented data flow and controls. Automated redaction is pattern based and cannot identify every type of personal or confidential information.
5. Acceptable use
Use BugCapsule only for lawful, authorised development and debugging. Do not use it to monitor people without authority, collect data from applications you do not control, distribute malicious content, access another project’s information, bypass security or usage limits, or disrupt the service.
Security testing against hosted infrastructure requires prior written authorisation and an agreed scope. Report suspected vulnerabilities privately to contact@bugcapsule.com or through your pilot contact, with enough detail to reproduce the issue and without exposing other people’s data.
6. Replay results and technical limits
Replay depends on the recorded inputs, SDK integrations, runtime, build, and supported execution environment. Unsupported integrations, missing requests, or changes in external state may prevent reproduction or make verification inconclusive.
A FIXED result describes the requested verification attempts under BugCapsule’s verdict rules. It is not a promise that an application is free of defects, safe for all users, or compliant with any standard. You remain responsible for reviewing results and deciding whether to release your software.
7. Fees and commercial terms
The landing page does not offer a self-serve paid subscription. Any pilot fees, future paid plan, billing period, taxes, payment schedule, cancellation conditions, and refund rights must be agreed separately before billing begins. Sending an application does not authorise a charge.
No automatic renewal or conversion to a paid plan is created by these terms. Changes to commercial terms require the process set out in the relevant agreement.
8. Software, ownership and feedback
BugCapsule and its licensors retain their rights in the service, website, documentation, branding, and software, subject to applicable open-source licences. These terms do not transfer ownership of your application or capsule data to BugCapsule.
You may provide suggestions during the pilot. Avoid including confidential customer information in feedback; any rights to use confidential feedback, case studies, your name, or your logo should be agreed separately. Third-party components remain subject to their own licences and terms.
9. Confidentiality and third-party services
Each party should protect non-public project information it receives through the pilot and use it only for the agreed relationship, subject to any confidentiality agreement. Do not post capsules, secret keys, personal data, or confidential application details in public issue trackers.
External services linked from this site, third-party SDK dependencies, email providers, and customer-selected hosting operate under their own terms. Review those terms before relying on them or sending data to them.
10. Suspension, ending the pilot and export
Access may be restricted where reasonably necessary to address credential compromise, unlawful use, material breach, or a threat to service security. Where practical, the pilot contact should receive notice and an opportunity to resolve the issue.
Either party may request that the pilot end, subject to the signed agreement. Coordinate export and deletion with your pilot contact before access ends. Retention sweeps and deletion can make capsules unavailable; downloaded copies remain under their recipients’ control, and backups expire according to the applicable backup schedule.
11. Warranties and liability
The pilot is an evaluation service and may contain errors, interruptions, and incomplete capabilities. Except for express commitments in a signed agreement and rights that cannot lawfully be excluded, it is provided on an “as available” basis without a guarantee of uninterrupted operation, successful reproduction, or fitness for a particular workflow.
Any agreed liability limits, remedies, or indemnities belong in the pilot or commercial agreement. Nothing in these terms excludes liability that applicable law does not permit the parties to exclude, or removes mandatory consumer or data protection rights.
12. Changes, disputes and contact
Revisions will be dated on this page. Material changes to an active pilot should be notified through the pilot relationship; they do not override a signed agreement without following its change process.
Raise questions or disputes with your designated pilot contact so the parties can try to resolve them directly. Governing law and jurisdiction should be specified in the signed agreement, subject to mandatory applicable law. For general enquiries, email contact@bugcapsule.com.