Trust Center
Infrastructure & partners, by role
Each logo describes the service a provider delivers to Coinstancy. It does not mean that the provider guarantees, audits or insures Coinstancy products.
-
Circle: User wallet infrastructure. Circle also issues USDC.
-
Safe: Multisignature wallets for treasury and strategy operations.
-
OpenCover: Facilitates access to optional protocol cover. The cover itself is carried by the provider.
-
Sumsub: Identity verification (KYC).
-
Scorechain: Transaction screening and monitoring (AML).
-
Coinme: On/off-ramp flows for eligible US users.
-
Cloudflare: Traffic routing, HTTPS and protection against common web threats.
-
AWS: Cloud hosting of the Coinstancy application.
Account security
Your Coinstancy account is protected with strong authentication across the platform.
Two-factor authentication is required on every account. Sensitive actions (withdrawals, email, password or 2FA changes, account deletion) require a fresh confirmation with a passkey or a 2FA code, so that only the account owner can validate them.
Your account is protected by mandatory 2FA, with passkey or 2FA code confirmation before sensitive actions.
What we put in place
-
2FA required on every account - Passkey or 2FA code authentication
- Re-authentication before withdrawals and security changes
- Recovery codes if you lose your device
- Identity verification with Sumsub
Proof
- Enforced in the application
- 2FA enrolment is mandatory (TOTP authenticator or passkey, with recovery codes).
- Step-up confirmation
- Required for withdrawals, email, password and 2FA changes, and account deletion.
- Provider role
- Sumsub performs identity verification (KYC).
Checked on .
Infrastructure security
Coinstancy runs on AWS cloud infrastructure behind Cloudflare, with HTTPS enforced on every connection and automated error tracking and alerting.
Our technical stack is designed to detect incidents, reduce operational risks and maintain a secure environment for users.
Our infrastructure is protected by Cloudflare, served over HTTPS only, and monitored by automated alerts.
What we put in place
- Professional cloud infrastructure (AWS)
- Cloudflare protection against web threats
- HTTPS enforced with HSTS
- AES-256 encryption of sensitive application secrets
- Automated error tracking and alarms
Proof
- Encryption in transit
- Traffic goes through Cloudflare; HSTS (one year, subdomains included) and secure session cookies are enforced.
- Encryption at rest
- Sensitive secrets such as 2FA keys, provider tokens and webhook payloads are encrypted with AES-256 by the application.
- Monitoring
- Sentry error tracking and CloudWatch alarms on critical events, with alerts sent to the team.
Checked on .
Wallet and crypto asset security
User wallets are powered by Circle infrastructure, allowing Coinstancy to manage crypto flows through a professional wallet stack.
For treasury, strategy execution and multisig operations, Coinstancy also uses Safe to add structured control over sensitive on-chain movements.
Your USDC first enters a secure multisignature wallet operated by Coinstancy before being deployed into the selected on-chain strategies. For USDC x Tangent, the option available in Dollar Savings: all USDC deposited in USDC x Tangent is then allocated to Tangent.
User wallets are powered by Circle, while Safe is used for treasury, strategy and multisig operations.
What we put in place
- Circle infrastructure for all user wallets
- Safe for treasury operations
- Safe for strategy execution
- Safe for multisig operations
- Savings deposits enter a multisig before strategy allocation
- Automated reconciliation and alerts on fund movements
- Reinforced control on sensitive operations
Proof
- Provider roles
- Circle provides user wallet infrastructure; Safe provides the multisignature wallets.
- Fund flows
- Payouts are reconciled automatically every minute, and deposits and withdrawals trigger internal notifications.
Checked on .
Strategy and protocol selection
Coinstancy does not select strategies only based on yield.
Before a strategy is used, our team reviews the protocol, its history, its risk profile, its audits, its liquidity and its operational resilience. Strategies are reviewed over time and can be reduced, paused or removed if their risk profile changes.
Every strategy goes through internal due diligence before being made available through Coinstancy.
What we put in place
- Review before any integration
- Verification of protocol audits
- Liquidity analysis
- Economic risk analysis
- Ongoing review over time
- Ability to reduce or pause a strategy
- No dependency on yield alone
Proof
- USDC x Tangent
- All USDC deposited in USDC x Tangent is then allocated to Tangent.
Checked on .
Additional cover for selected protocol risks
Coinstancy can classify a protocol as sensitive and decide, case by case, whether to acquire or maintain compatible cover through OpenCover, with Nexus Mutual or another cover provider. Classifying a protocol as sensitive does not automatically mean that it is covered.
When a policy is active, it can help address eligible protocol incidents within its terms, limits and dates. Depending on the protocol, the amount and the period, the covered share of an exposure can range from 0%, when no cover is acquired, to 100%. No minimum coverage is promised.
OpenCover facilitates access to cover; the cover itself is carried by the provider. Its cost is borne by Coinstancy, and clients have no direct claim against OpenCover or the provider. Additional cover is not a guarantee of your capital or of your deposits.
Protocol incidents that can affect a strategy include smart contract bugs, oracle manipulation or failure, liquidation failure and malicious governance takeovers. Whether a specific incident is eligible depends on the terms of the policy in force, if any.
Selected protocol exposures may benefit from additional coverage arranged through OpenCover, subject to the applicable policy terms, conditions, and coverage limits.
What we put in place
- Targeted cover on selected protocol exposures
- Case-by-case decision, never automatic
- From 0% to 100% of an exposure, depending on protocol, amount and period
- No minimum coverage promised
- Cost of cover borne by Coinstancy
- Eligible incidents, limits and exclusions set by each policy
- Not a guarantee of your capital
Proof
- Active policies
- A policy is listed here only once its scope, limits and dates can be published.
- Provider role
- OpenCover facilitates access to cover; it does not guarantee Coinstancy products.
Checked on .
Risks to know
Stablecoin risk
USDC is issued by Circle. A stablecoin can temporarily or durably lose its peg to the US dollar.
Protocol risk
The on-chain protocols used by a strategy can be affected by code bugs, exploits, oracle failures or governance incidents, which can lead to a partial or total loss.
Liquidity risk
In stressed markets, a protocol may not have enough available liquidity to process withdrawals immediately, which can delay settlement.
Network risk
Blockchain congestion, outages or fee spikes can delay transactions and confirmations.
Market risk
When a pool holds an asset other than a dollar stablecoin, its value in US dollars moves with the market price of that asset and can fall. Yield does not offset a price drop.
Compliance and transaction monitoring
Sumsub
Identity verification (KYC)
Scorechain
Transaction monitoring
Coinme
On/off-ramp flows for eligible US users
Security contact
Security coverage and protections described on this page depend on the applicable terms and conditions and may evolve over time.