Language

Privacy Policy

Version 0.1.0Last updated: Jun 2, 2026

Overview

This starter Privacy Policy describes expected data processing for ForgePay accounts, wallet activity, marketplace orders and merchant API usage. It must be adapted to the final controller, processors and jurisdiction.

Legal review required

This is a starter template and must be reviewed by a qualified lawyer before commercial launch.

ForgePay is not a bank. ForgeCredit is an internal settlement unit for services available in the ForgePay ecosystem.
ForgePayforgepay.ai

Privacy Policy

Version 0.1.0. Starter text for review and editing. Last updated: Jun 2, 2026.

This is a starter template and must be reviewed by a qualified lawyer before commercial launch.

This starter Privacy Policy describes expected data processing for ForgePay accounts, wallet activity, marketplace orders and merchant API usage. It must be adapted to the final controller, processors and jurisdiction.

Editable placeholder variables

  • [COMPANY_LEGAL_NAME]
  • [COMPANY_ADDRESS]
  • [COMPANY_REGISTRATION_NUMBER]
  • [VAT_ID]
  • [OWNER_NAME]
  • [CONTACT_EMAIL]
  • [SUPPORT_EMAIL]
  • [DPO_EMAIL]
  • [JURISDICTION]
  • [PAYMENT_PROVIDER]
  • [LAST_UPDATED_DATE]

Core ForgePay statements

  • ForgePay is not a bank.
  • ForgeCredit is not money issued by a government or central bank.
  • ForgeCredit is not a savings product.
  • ForgeCredit does not create ownership, yield or repayment rights.
  • Ordinary users cannot withdraw FGC to EUR.
  • Bonus FGC is non-transferable.
  • Transferable FGC may be sent between users subject to limits and fees.
  • The user-to-user transfer fee is 0.02%.
  • Sellers are settled according to Seller Terms.
  • External merchant API usage is governed by API Terms.

Controller and contacts

The controller placeholder is [COMPANY_LEGAL_NAME] at [COMPANY_ADDRESS]. Privacy, support and DPO contacts should be replaced with [CONTACT_EMAIL], [SUPPORT_EMAIL] and [DPO_EMAIL].

Data categories

ForgePay may process account data, profile data, authentication records, transaction metadata, ledger references, seller onboarding data, merchant API events, subscription mandate consent records and support messages.

Legal bases and retention

Final text should define legal bases, retention periods, processor lists, international transfers and user rights under [JURISDICTION].

Security records

Security events, audit logs, PIN lockout metadata and webhook delivery logs may be processed to protect users, sellers and merchants.

No final legal advice

This page is starter content for drafting and product planning only. It must be reviewed and adapted by a qualified lawyer before commercial launch.