Terms of Service

Effective date: 2026-05-17. Last updated: 2026-05-17.

These Terms of Service (the “Terms”) form a binding agreement between you (the “User”) and Exploding Frame SAS, a French société par actions simplifiée with share capital of €1,000, registered as TODO, with its registered office at TODO (“FrameSight”, “we”, “us”, or “our”).

By accessing or using FrameSight, you confirm that you have read, understood, and agreed to be bound by these Terms. If you do not agree, do not use the service.

These Terms are written in English and governed by French law. A French translation is available on request and is provided for informational purposes only; the English version prevails in case of discrepancy.

Part A. Terms of Use

1. The service

FrameSight is a graphics-performance analysis platform. The service accepts RenderDoc frame captures (.rdc files) produced by the User, replays them on dedicated GPU hardware operated by us, extracts performance counters and structural metadata, and renders a static HTML report consultable from the User’s dashboard.

The infrastructure is hybrid:

• The web dashboard and the reporter service run on a virtual private server (VPS) operated by a third-party hosting provider (see Legal Notice).
• The orchestrator (which coordinates the extraction pipeline) and the runner fleet (physical machines performing the GPU replay) are self-hosted on premises controlled by Exploding Frame SAS, inside private networks not exposed to the public internet.

Users select which runner configuration their capture should target. Users cannot install, register, or otherwise manage runners. The runner fleet is FrameSight infrastructure.

2. Account and eligibility

Creating an account requires a valid email address. Authentication is provided through any of the following methods:

• Google OAuth 2.0 (your Google account)
• GitHub OAuth 2.0 (your GitHub account)
• Email magic-link (a single-use sign-in link sent to your inbox)
• Email and password (passwords are stored using bcrypt)

You are responsible for maintaining the confidentiality of your credentials and for all activity that occurs under your account. Notify us immediately at security@explodingframe.com if you suspect unauthorised access.

The service is intended for users aged 18 or over and acting in a professional capacity (game studio, freelance graphics engineer, researcher). Use of the service by consumers (B2C) is possible but subject to the additional protections described in Part B (Terms of Sale).

3. Organisations and roles

Every user is automatically provisioned with a Personal organisation upon first sign-in. Users may be invited to additional Team organisations. Within each organisation, three roles exist:

• User: read-only access to the organisation’s benchmarks and reports.
• Maintainer: read access plus the ability to upload captures, launch runs, and create benchmarks.
• Owner: full access including member management, plan changes, and invitations.

Owners are responsible for the conduct of all members of their organisation. Removing a member revokes their access to the organisation’s benchmarks and reports but does not delete data that other members of the organisation still own.

4. Intellectual property

4.1 User content

You retain all rights, title, and interest in the RenderDoc captures (.rdc files), shaders, textures, buffers, and any other content you upload (the “User Content”).

By uploading User Content, you grant FrameSight a non-exclusive, worldwide, royalty-free, temporary licence to: (i) host the User Content on our infrastructure for the duration strictly necessary to perform the analysis, (ii) process the User Content through the runner replay and extraction pipeline, (iii) generate, store, and display the resulting performance report to authorised members of your organisation, and (iv) operate aggregated, fully-anonymised statistics for the purpose of improving the service (no shader bytecode, texture content, or geometry is ever included in such statistics). This licence terminates upon deletion of the corresponding capture or report.

4.2 FrameSight technology

The FrameSight platform, including the dashboard user interface, the orchestrator software, the runner software, the extractor pipeline, the report HTML templates and styling, the SQLite report schema, the JSON report envelope, the GPU-time overhead correction model, the calibration dataset, the brand name, the logos, and all associated documentation (the “Platform IP”) is the exclusive property ofExploding Frame SAS and its licensors. No rights are granted to you in the Platform IP except as expressly set out in these Terms.

4.3 Third-party software

FrameSight integrates several open-source and commercial components. The applicable licences are listed below; their respective terms prevail for the portion of the service derived from each component:

• RenderDoc: MIT License (Copyright © Baldur Karlsson). We use RenderDoc’s Python API and C++ libraries to load and replay .rdc capture files. See renderdoc/LICENSE.md.
• NVIDIA Nsight Perf SDK (NPerf): used at replay time to collect per-event GPU counters on NVIDIA hardware. Subject to NVIDIA’s SDK End User License Agreement.
• Microsoft DirectXTex (texconv): MIT License. Used to decompress BC-format textures during preview generation.
• Next.js, React, Tailwind CSS, TypeScript: MIT License (Vercel, Meta).
• PostgreSQL, Drizzle ORM, better-sqlite3, tusd: PostgreSQL, Apache 2.0, MIT, and MIT licences respectively.
• Auth.js (NextAuth v5): ISC License. Used for authentication.
• Pillow, NumPy, SciPy, scikit-learn, Matplotlib, pandas, openpyxl: used by the analysis and calibration tooling; each under its respective permissive licence (HPND, BSD, BSD, BSD-3, PSF, BSD-3, MIT).
• Jinja2: BSD-3 License. Used by legacy report templates.
• LemonSqueezy: payment processing services (see Part B, §11). Use of the checkout flow is subject to LemonSqueezy’s own terms.

A complete dependency manifest with version numbers and licence details is available on request to legal@explodingframe.com.

5. Acceptable use

You agree NOT to:

• Upload captures of software you do not have the legal right to analyse. Reverse engineering or performance analysis of third-party software typically requires the rights holder’s authorisation, either by virtue of an end-user licence agreement, an interoperability exception, or an explicit contract. You represent and warrant that you hold such rights for every capture you upload. FrameSight is not a party to, and bears no responsibility for, any infringement claim arising from unauthorised analysis.
• Upload User Content containing illegal material, malware, code designed to exploit vulnerabilities in the service, or data subject to export-control restrictions you cannot lawfully transfer to France.
• Attempt to bypass the storage cap, credit accounting, role gates, or any other technical limit imposed on your organisation’s plan.
• Use the service to harass, defame, or otherwise harm any other person.
• Resell, sublicense, or otherwise commercially exploit access to the service without our prior written consent.
• Scrape, mirror, or otherwise harvest content from the dashboard beyond what the dashboard’s own UI permits.

6. Administrator access and the Privacy Mode flag

At benchmark creation you may set the “Allow FrameSight admin access” flag. Its semantics are:

• Flag enabled (default): FrameSight staff with Administrator role may consult the benchmark, its captures, and its reports for the purposes of (a) responding to a support request you have opened, (b) diagnosing extractor or runner bugs surfaced by your benchmark, (c) verifying compliance with these Terms.
• Flag disabled: FrameSight staff cannot load the benchmark’s reports through the standard dashboard access path. We retain technical access at the storage layer (we operate the disks) but undertake not to consult report contents under this flag except where (i) you explicitly invite us to in writing, (ii) we are required to do so by valid legal process, or (iii) such consultation is strictly necessary to prevent imminent damage to the service or its users.

All Administrator accesses are recorded in an append-only audit log retained for 90 days. Owners of the organisation may request a copy of the log entries pertaining to their organisation at any time at support@framesight.io.

7. Data security and retention

FrameSight implements the following technical and organisational measures:

• Encryption in transit. All communication with the dashboard and the orchestrator uses TLS 1.2 or higher.
• Encryption at rest. Capture bundles, report HTML and JSON, and the SQLite extraction databases are encrypted on disk using AES-256. Encryption keys are managed exclusively by FrameSight; we cannot consult report contents without decrypting them, which is performed only by authorised service processes serving a request from an authenticated, authorised member of the relevant organisation.
• Access control. Database-level row scoping by organisation_id, role-based gates on every mutating API route, and isolated runner processes per job.
• Audit logging. Every administrative action (role change, member removal, plan change, manual deletion) is recorded with actor identity, timestamp, target, and before/after metadata.

Retention periods.

• RenderDoc .rdc upload. The original .rdc file is deleted automatically within 24 hours after the extraction pipeline completes (whether successfully or with a definitive failure). Only the derived report and the structural metadata persist. The User retains the right to re-upload at any time.
• Report bundles and SQLite extraction databases. Kept for 30 days after benchmark deletion (soft-delete window). Users may shorten this window via support request; a self-service control may be published in a future release.
• Account data. Retained until the User deletes their account or, if earlier, three years after the User’s last sign-in.
• Audit logs. 90 days.
• Connection logs (IP addresses, user-agent). One year, in compliance with the French Loi pour la confiance dans l’économie numérique (LCEN, Article 6).

8. Termination and account deletion

You may delete your account at any time from your account settings, or by writing to support@framesight.io. Account deletion triggers (i) the immediate suspension of access, (ii) the deletion of your personal organisation and all benchmarks within it, (iii) the removal of your membership from any Team organisation you were part of. Team organisations are NOT deleted when their owners delete their accounts; the operator should ensure another Owner exists or transfer ownership before proceeding.

FrameSight may suspend or terminate your account, with prior notice where reasonably possible, in case of (i) material breach of these Terms, (ii) prolonged inactivity (more than 24 months without sign-in), (iii) non-payment for paid plans (see Part B, §11.4).

Part B. Terms of Sale

9. Subscriptions and credits

FrameSight is offered under four pricing tiers (the “Plans”): Free, Indie, Pro, and VIP (by invitation only). Each Plan defines a monthly inclusive credit allocation, a monthly storage cap, a queue priority class, and (for paid plans) a credit-pack exchange rate available for top-ups.

The current Plans and their pricing are configured by FrameSight administrators and are displayed live on the /usage page within the dashboard. The structure is:

“Credits” are the unit of compute used to launch runs on FrameSight runners. The credit cost of a capture depends on when the run executes:

• Day-rate capture (run scheduled to the runner’s day window): 100 credits per capture.
• Night-rate capture (run scheduled to the runner’s night window): 50 credits per capture.

Each runner’s day and night windows are published on the /runners fleet page and on the run-launch screen.

Two categories of credits exist:

• Inclusive credits: granted automatically each month as part of a paid subscription. Inclusive credits expire one (1) calendar month after they are granted. Unused inclusive credits do not roll over.
• Bonus credits: purchased separately through the credit-pack flow. Bonus credits remain valid for one (1) year from the date of purchase.

When a run is launched, inclusive credits are consumed first (FIFO by grant date); bonus credits are consumed second.

Two paid add-ons may be purchased in credits at any time:

• Additional storage: 50 credits per GB per month, beyond the Plan’s included cap.
• Queue priority boost: 50 credits to elevate a single run’s queue priority by one class.

Credit packs are sold in fixed denominations between €5 and €50, with the exact credits-per-euro ratio configured by FrameSight administrators and displayed at the moment of purchase on the /usage page. Pricing parameters (day rate, night rate, monthly allocations, storage cap, credit packs) may be revised at our discretion; any change in pricing applies to billing periods starting after the change becomes effective and does not affect credits already granted.

10. Payment and billing

Payments are processed by LemonSqueezy (operated by Lemon Squeezy Inc., 100 King St W, Suite 5700, Toronto, Ontario, Canada), our Merchant of Record. LemonSqueezy is responsible for invoicing, payment collection, tax computation, and remittance to local tax authorities. By purchasing a subscription or credit pack you agree to LemonSqueezy’s own Terms of Service and Privacy Policy.

Invoices are issued by LemonSqueezy and delivered to the email address associated with your account at the time of purchase. We do not store full payment-card details; only the last four digits and the brand, returned by LemonSqueezy for display purposes, are held in your account record.

All prices are stated exclusive of VAT, which is added at checkout based on the customer’s billing country.

11. Withdrawal right (B2C only)

For users acting as consumers (i.e. not in the course of a professional activity), Article L.221-18 of the French Code de la consommation normally grants a 14-day withdrawal right for distance contracts. By starting to use the service before the end of that 14-day period (specifically, by launching the first run and consuming the first credit) you expressly waive your right of withdrawal for the consumed portion of the service, in accordance with Article L.221-28, 1° of the same Code.

Unconsumed credits and subscription periods not yet entered may still be refunded within the 14-day window upon written request to billing@framesight.io. B2B customers (acting in a professional capacity) are not eligible for the withdrawal right.

12. Service-level commitment

FrameSight is provided on a best-effort basis. We target 99.0 % monthly availability of the dashboard and the reporter (the VPS-hosted components). The runner fleet is a separately monitored resource pool described in §12.1 below.

12.1 Runner availability

Each runner operates on a daily schedule with two windows: a “day window” (during which the day rate of 100 credits per capture applies) and a “night window” (during which the discounted night rate of 50 credits per capture applies). The split is specific to each runner and is published on the /runners page so users can align their submissions with the rate they prefer.

Every runner undergoes a daily maintenance window of up to 30 minutes at a fixed time-of-day announced at least one week in advance on the /runners page. Time spent in the announced maintenance window does NOT count as downtime for SLA purposes, and runs queued during that window are deferred to the next available slot.

Downtime outside the announced maintenance window is measured per runner, on a calendar-month basis, separately for the day window and the night window.

• Day-window downtime: refundable above 5 %. If a paid-plan customer experiences more than 5 % unplanned downtime accumulated over the day windows of a given runner in a calendar month (measured as a fraction of total day-window minutes in that month), the customer is entitled, upon written request to billing@framesight.io, to a pro-rata refund of the monthly subscription fee covering that runner’s use.
• Night-window downtime: not refundable. The discounted night rate (50 credits per capture instead of 100) reflects the “best-effort” nature of the night window. Downtime during the night window does not give rise to a refund, but its duration is added to the validity period of bonus credits affected by it, on a one-for-one basis.

Queue priorities by Plan: Pro > Indie > Free = VIP. Within the same Plan, runs are dispatched in submission order. A user may temporarily elevate the priority of a single run by purchasing the priority-boost add-on described in §9.

12.2 Force majeure

Failures attributable to force majeure events (Article 1218 of the French Civil Code), including but not limited to natural disasters, power outages affecting the data centre or the on-premises runner facility, internet backbone failures, third-party-API outages, and labour disputes, do not engage our liability and do not count toward the 5 % SLA threshold.

13. Limitation of liability

To the maximum extent permitted by applicable law:

• FrameSight’s aggregate liability under these Terms is capped at the amount paid by the User to FrameSight in the twelve (12) months preceding the event giving rise to the claim, or €100 if the User is on the Free plan.
• FrameSight is not liable for indirect, consequential, special, incidental, or exemplary damages (including loss of profits, revenue, data, or use) arising out of or related to the service.
• The User remains liable for ensuring that uploaded captures comply with §5; any indemnification arising from a third-party infringement claim related to User Content is the User’s sole responsibility.

14. Changes to these Terms

We may amend these Terms from time to time. Material changes will be notified to active account holders by email at least 14 days before they take effect. Continued use of the service after the effective date constitutes acceptance of the amended Terms. Users who do not accept the new Terms may terminate their account without penalty during the notice period.

15. Governing law and jurisdiction

These Terms are governed by French law. Any dispute arising from or in connection with these Terms shall be subject to the exclusive jurisdiction of the competent courts of [Tribunal de commerce, to be filled per registered office] for B2B users. B2C users retain the protections of Articles R.631-3 and R.212-2 of the French Code de la consommation.

Before initiating any judicial proceedings, the parties agree to attempt an amicable resolution by writing to legal@explodingframe.com and waiting 30 days for a substantive reply.

16. Contact

General questions: support@framesight.io
Legal and contractual questions: legal@explodingframe.com
Billing: billing@framesight.io
Security: security@explodingframe.com