How we handle payments, crypto and privacy.

For companies and structured teams, we prefer a straightforward, documented process.

• Formal proposal and scope of work (SOW) before we start.
• Invoices in USD (or other agreed currency) with clear deliverables and dates.
• Payment methods typically include bank transfer and card via a payment provider.

If your company has specific vendor onboarding or compliance requirements, let us know early so we can confirm feasibility.

For smaller or private projects, we keep it lighter but still clear.

• Short written agreement or email confirmation of scope and price.
• Invoicing per phase or per fixed scope.
• Funding-friendly options for early-stage founders (smaller first steps, clear next checkpoints).

If you prefer not to have your name publicly attached to the project, we can discuss alias-based communication where lawful.

We treat crypto as one possible way to settle invoices for our work, not as a product in itself.

• On request and by prior agreement, we may accept payment in major cryptocurrencies (for example BTC, ETH or USDT) instead of a traditional wire transfer.
• Invoices still describe the work, scope and value in a reference currency (usually USD).
• We confirm addresses and networks with you directly and do a small test transaction, where it makes sense.

Crypto availability depends on your location, regulatory context and project type. We may decline crypto for certain engagements even if we accepted it previously.

There are clear boundaries around what we will not provide in relation to crypto.

• We are not an exchange, broker, wallet provider or custodian.
• We do not trade, swap or hold crypto assets on your behalf.
• We do not provide investment, tax or legal advice.
• We do not help bypass sanctions, KYC/AML rules or other compliance requirements.

If your project involves regulated financial services, you are responsible for obtaining your own legal and regulatory advice. We can only participate within a clearly lawful and compliant framework.

By default, we try to operate with as little personal data as reasonably necessary.

• Details you submit via the contact form or email (name or alias, contact info, project description).
• Technical data like IP address and user agent when you use the site (mainly for security and anti-abuse).
• Analytics data, if enabled, to understand basic traffic and improve the site (e.g. page views, referrers).

Some analytics and hosting providers may process data on our behalf. We aim to choose vendors with strong privacy practices and a good reputation.

For more sensitive or low-profile work, we can discuss a stricter, privacy-first setup.

• Alias-based communication instead of full legal names in casual channels.
• Use of encrypted messengers (for example Telegram) for day-to-day coordination.
• No ad trackers and minimal logging on project-related endpoints where feasible.

Privacy-first does not mean “outside the law”. We still need to comply with applicable regulations and may need basic identity and billing details, especially for larger or ongoing engagements.

We reserve the right to decline or terminate any project that falls into certain categories, even if it might appear technically interesting.

• Projects clearly intended to violate applicable law in any jurisdiction.
• Work designed to facilitate fraud, money laundering or evasion of sanctions.
• Products that intentionally promote harm, hate or violence.
• Tools whose primary purpose is to hide assets from lawful authorities.

If you are unsure whether your idea fits within these boundaries, it’s better to ask up front. We prefer a clear “no” to a vague “maybe”.