Privacy Policy

1. Controller

The data controller is RUNTIME GUARD, SASU, SIREN 106 846 777, RCS Paris, registered office at 1 rue Marguerin, 75014 Paris, France.

Privacy contact: contact@runtime-guard.io.

Runtime Guard has not appointed a data protection officer at this stage. This will be reassessed if the nature or scale of processing changes.

2. Privacy posture

Runtime Guard is designed to minimize personal data processing.

• Runtime Guard analyses public blockchain data, Safe transaction data, and user-provided transaction context.
• Runtime Guard does not hold, generate, store, or control user private keys, seed phrases, recovery phrases, or wallet credentials.
• Runtime Guard does not store full card numbers or payment method credentials.
• Paddle as merchant of record processes buyer billing, tax, receipt, payment, refund, and chargeback data under Paddle's own buyer terms and privacy notices.
• Runtime Guard normally receives only the Paddle identifiers and subscription status needed to operate entitlements.
• Runtime Guard does not sell personal data and does not run advertising profiling.

3. Data processed

Runtime Guard may process the following categories of data.

Wallet, Safe, and transaction data

• wallet addresses used for Sign-In with Ethereum or equivalent wallet authentication;
• Safe addresses and chain identifiers;
• Safe transaction hashes, Safe transaction URLs, calldata, signatures, approvals, signers, thresholds, owners, modules, guards, timelock state, and related public blockchain data;
• submitted transaction context, such as the page or application where a transaction was initiated, when that context is provided by the browser extension or application;
• address-book labels read locally from the Safe interface where the extension provides them for display context.

Address-book labels are treated as untrusted display metadata. They are not used as a source of truth for policy decisions, transaction classification, or signature decisions.

Account, entitlement, and application data

• wallet-authentication session data;
• Safe enrollment status;
• subscription tier, entitlement status, billing period, and opaque Paddle customer, transaction, and subscription identifiers;
• policy configuration, report status, product settings, and audit trail entries for paid features where applicable.

Technical, security, and abuse-prevention data

• IP address, user agent, timestamps, request metadata, error logs, rate-limit events, security events, fraud-prevention signals, and operational diagnostics;
• Cloudflare security signals, bot-protection outcomes, and strictly necessary cookies or local storage needed to operate the website and application;
• data required to investigate abuse, incidents, payment disputes, chargebacks, fraud, or legal requests.

Support and communications data

• emails, messages, attachments, and contact details you choose to send to Runtime Guard;
• information needed to respond to support requests, legal requests, payment issues, security reports, or account questions.

Runtime Guard does not request KYC documents from ordinary users. If you voluntarily send documents or sensitive information to Runtime Guard, Runtime Guard will process them only as needed for the relevant request and will avoid retaining unnecessary copies.

4. Purposes and legal bases

Runtime Guard processes personal data for the following purposes and legal bases.

• Providing the service: analysis, reports, extension workflows, application access, product settings, entitlements, and support. Legal basis: performance of a contract or steps taken before entering into a contract.
• Security and abuse prevention: bot prevention, rate limiting, fraud prevention, incident response, sanctions or abuse screening where applicable, service integrity, and protection of Runtime Guard, users, and third parties. Legal basis: legitimate interests and, where required, legal obligations.
• Billing and subscription administration: subscription state, entitlement checks, invoice or payment issue handling, refunds, chargebacks, and tax or accounting records. Legal basis: performance of a contract and legal obligations.
• Product operation and reliability: debugging, logs, uptime, error analysis, and improvement of service stability. Legal basis: legitimate interests.
• Legal compliance and dispute handling: preserving evidence, responding to lawful requests, enforcing terms, defending claims, and complying with tax, accounting, or regulatory obligations. Legal basis: legal obligations and legitimate interests.
• Optional communications or analytics: only where enabled by the user or where consent is required. Legal basis: consent.

5. Recipients and processors

Runtime Guard may share or make data available to service providers only where needed to operate, secure, bill, or support the service.

Current or expected categories include:

• Paddle, acting as merchant of record for payments, tax, receipts, refunds, chargebacks, and buyer support;
• Cloudflare, for website hosting, CDN, security headers, bot protection, and related infrastructure;
• Google Cloud Platform, for application hosting, logging, key-management infrastructure, and operational security;
• RPC, blockchain data, and simulation providers, for transaction analysis and public blockchain state reads;
• email, support, monitoring, and incident-response providers, where used;
• professional advisers, authorities, courts, or acquirers, where required for legal, accounting, compliance, corporate, financing, or M&A purposes.

Runtime Guard does not send Safe addresses or wallet addresses to Paddle in the ordinary checkout flow unless necessary for support, fraud prevention, dispute handling, compliance, or legal reasons.

6. International transfers

Some providers may process data outside the European Economic Area, including in the United States or the United Kingdom.

Where required, Runtime Guard relies on appropriate safeguards such as adequacy decisions, standard contractual clauses, provider transfer safeguards, or equivalent legal mechanisms.

7. Retention

Runtime Guard keeps personal data only for as long as needed for the relevant purpose.

• Website, application, security, and operational logs are normally retained for up to 12 months, unless an incident, dispute, fraud investigation, legal obligation, or security need requires longer retention.
• Free, Plus, and Pro Solo report data is not intended to create a user-facing cloud history. Temporary operational or debugging copies may be retained for a short period, normally up to 7 days, where needed to operate or troubleshoot the service.
• Pro Team report history, audit trails, and team-visible data are retained according to the plan, application settings, order form, or written agreement.
• Subscription and entitlement records are retained for the subscription period and then as long as needed for tax, accounting, dispute, fraud-prevention, and legal obligations.
• Support records are retained for as long as needed to answer the request and preserve reasonable evidence of the exchange.
• Public blockchain data is outside Runtime Guard's control and may remain available on public networks and third-party services independently of Runtime Guard.

8. Browser extension

The browser extension is designed to show Runtime Guard information inside supported Safe workflows and reduce manual report submission.

Depending on the page and feature, the extension may read:

• the current Safe page URL and Safe transaction identifier;
• the connected Safe address, chain, transaction hash, and transaction metadata visible in the Safe interface;
• local Safe address-book labels for display context;
• the origin or application context from which a transaction was submitted, where available.

The extension may send the minimum data needed to request or display a Runtime Guard report. The extension does not receive or store private keys, seed phrases, wallet recovery phrases, or wallet signing credentials.

Wallet signatures remain handled by the wallet, Safe interface, or relevant signing application.

9. Chrome Web Store data disclosures

For the Chrome Web Store privacy disclosure, Runtime DeFi Guard handles the following categories:

• Financial and payment information: proposed Safe transaction details such as destination addresses, asset and amount context, calldata-derived actions, approvals context, Safe transaction hashes, Safe metadata, and related execution context needed to generate a risk report.
• Website content: transaction-related content displayed on app.safe.global and Safe-owned pages that is necessary to understand the proposed Safe transaction and generate the requested analysis.

Runtime Guard uses this data only to provide the extension's core transaction-review, report, security, reliability, abuse-prevention, and support functionality. Runtime Guard does not sell this data, does not use it for advertising, and does not transfer it for purposes unrelated to the extension's core functionality.

Runtime Guard's use of information received from the Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

10. Cookies and local storage

Runtime Guard may use strictly necessary cookies, local storage, and similar technologies to operate the website, maintain sessions, remember interface state, prevent abuse, and protect the service.

Runtime Guard may use Cloudflare Turnstile or equivalent bot-protection tools to protect forms and public endpoints.

Non-essential analytics or marketing cookies are not required for the current public website. If Runtime Guard later enables non-essential cookies or analytics requiring consent, the website will request consent where required.

11. Security

Runtime Guard applies technical and organizational measures intended to protect the service, including access controls, encryption in transit, segmented infrastructure, operational logging, and least-privilege access where practical.

No system is perfectly secure. Users remain responsible for safeguarding wallets, signing devices, Safe configuration, private keys, recovery phrases, and operational access.

12. User rights

Subject to applicable law, you may request:

• access to your personal data;
• rectification of inaccurate data;
• erasure of data;
• restriction of processing;
• portability of data;
• objection to processing based on legitimate interests;
• withdrawal of consent where processing is based on consent.

Because Runtime Guard is wallet-based and often pseudonymous, Runtime Guard may ask you to prove control of the relevant wallet, Safe, email address, or support channel before acting on a request.

You may lodge a complaint with a supervisory authority. In France, the supervisory authority is the CNIL.

Requests can be sent to contact@runtime-guard.io.

13. Automated processing and verdicts

Runtime Guard performs automated analysis of transaction data to produce risk reports and verdicts (such as GREEN, AMBER, RED, or BLACK) and, where a paid co-signing plan is enabled, to apply one non-decisive co-signature to a transaction that passes the configured policy checks.

This automated processing evaluates transactions and configurations. It is not intended to make decisions that produce legal effects concerning you, or similarly significantly affect you, as an individual within the meaning of Article 22 GDPR. Verdicts are advisory, and you keep final authority to sign, reject, modify, or delay any transaction through your own Safe signers.

You can contact Runtime Guard at contact@runtime-guard.io for information about this processing.

14. Children

Runtime Guard is not directed to persons under 18 and does not knowingly provide paid services to children.

15. Changes

Runtime Guard may update this Privacy Policy from time to time. The latest version is published on the website with its update date.