Privacy Policy

Effective October 26, 2026 · A Path is Formed by Walking Inc.

This Privacy Policy describes how A Path is Formed by Walking Inc., a corporation incorporated under the federal laws of Canada (“Payfer”, “we”, “us”), collects, uses, discloses and protects personal information when you use Payfer at payfer.me, our hosted approval and management pages, dashboard, APIs and SDKs (together, the “Service”). It applies to end users who fund accounts and approve allowances, and to developers who register applications. Questions or requests: support@payfer.me.

A Path is Formed by Walking Inc., operating Payfer, is the organization responsible for personal information collected through the Service, except where a developer application or a third-party service (such as Privy or Stripe) is responsible for its own collection. Contact our privacy contact at support@payfer.me for any question, access, correction, deletion or portability request, or complaint about this Policy.

  • Account information: your email address, an internal account identifier, your Privy user identifier, embedded-wallet identifiers and wallet address, sign-in and step-up verification events, and dashboard session information.
  • Allowance and payment information: app-scoped payment identifiers (paymentUserId), application names and identifiers, signed authorization terms and signatures (limits, payee, chain, token, period, nonce, version and signer address), spending, reservations, charges, metered collections, refunds, receipts and transaction hashes.
  • Funding information: top-up amounts, card-processing fee amounts, settlement and payout status, Stripe checkout and payment identifiers, and your wallet’s resulting balance and settlement activity. Payfer does not receive or store full card numbers; Stripe collects card details directly.
  • Developer information: account email, application name, publishable key, a hash of the secret key (never the secret itself after issuance), payout address, registered origins, live/test status, pricing tier and lifetime charge totals, and payment and refund records for the application.
  • Technical and security information: IP address, browser and device information, request timestamps, rate-limit counters, error and audit logs, and abuse-prevention signals needed to operate and secure the Service.
  • Communications: messages you send to support, and records of notices we send you.
  • What we do not collect: Payfer does not require or receive your prompts, model responses, provider credentials or provider invoices from developer applications. Developers are responsible for what their own applications collect.
  • Directly from you when you sign in, fund, approve, change or revoke an allowance, register an application, or contact support.
  • From Privy when you authenticate and use an embedded wallet, and from Stripe when you fund by card, as needed to complete those flows.
  • From developer applications when they create connections or submit charges, metering, refunds or settings through our APIs.
  • From public blockchain networks, where wallet addresses, balances and transactions are publicly recorded.
  • Automatically, through server logs, rate limiting and strictly necessary local storage in your browser (for example dashboard sign-in tokens and display preferences). The Service does not use advertising or cross-site tracking cookies.
  • To create and authenticate accounts, issue app-scoped payment identifiers, verify wallet signatures, activate, enforce, change and revoke allowances, execute charges and refunds, deliver card-funded top-ups, settle developer proceeds and fees, and maintain receipts and reconciliation records.
  • To show you and, for developers, your applications, balances, limits, payments, refunds, keys, origins, payout settings and pricing tier.
  • To prevent fraud and abuse, enforce rate limits and allowance controls, secure accounts and keys, debug and maintain the Service, and comply with legal, tax, accounting, sanctions and dispute obligations.
  • To communicate about sign-in codes (through Privy), settlement status, changes to the Service, these Terms or this Policy, and to respond to support requests.
  • In aggregated or de-identified form for understanding usage and improving the Service, where it no longer identifies you.
  • We use personal information only for the purposes above or a purpose you consent to, as required or permitted by law. Providing information needed for sign-in, allowances and payments is necessary to use those features; if you do not provide it, we cannot provide them.

Wallet addresses, token balances, transfers, fees and transaction hashes on the Tempo network (and any other network the Service may use) are public, replicated by third parties, and generally cannot be edited or deleted by Payfer or anyone else. Anyone may be able to correlate on-chain activity. App-scoped payment identifiers reduce what developer applications receive, but they do not make blockchain activity anonymous, and Payfer necessarily maintains the internal mapping between accounts, wallets and app-scoped identifiers in order to operate.

  • Privy — authentication, email one-time codes and embedded-wallet infrastructure. Privy processes your email, authentication events and wallet operations under its own terms and privacy policy.
  • Stripe — card funding through Stripe Checkout, including payment, dispute and chargeback processing. Stripe receives the information needed to process your card payment under its own terms and privacy policy.
  • Tempo network and token infrastructure — wallet addresses, authorization-related and settlement transactions are submitted to a public blockchain, where they are visible to network participants and the public.
  • Hosting and infrastructure providers — currently including Railway for application and database hosting, and email/delivery providers used by our processors — only as needed to run and secure the Service.
  • Developer applications — a developer receives only its own application’s app-scoped paymentUserId, that application’s allowance status and remaining budget, and its own payments, refunds and receipts. Applications do not receive your email, wallet address, Privy identifier, global account identifier, other applications’ data, or your total balance or funding details. Developers are independent controllers of information they collect through their own applications.
  • Legal, safety and business recipients — where required by law, court or regulator order, sanctions or tax obligations; to prevent fraud or protect rights, property or safety; to professional advisors under confidentiality; or to a buyer, investor or successor in connection with a financing, merger, acquisition or sale, subject to applicable law.
  • No sale of personal information. Payfer does not sell personal information, and does not share it for cross-context behavioural or targeted advertising. We do not use personal information to train models on your content, because we do not collect your application content (see above).

We keep account, allowance, payment, refund and funding records while your account or application is active and thereafter as needed for settlement, reconciliation, dispute and chargeback handling, fraud prevention, tax, accounting, sanctions and other legal obligations — typically up to seven years after account or application closure, and longer where a law, hold or unresolved dispute requires it. Security and rate-limit logs are kept for shorter operational periods unless needed for an investigation.

When retention is no longer required, information is deleted or de-identified, subject to backups expiring in the ordinary course. Information recorded on a public blockchain cannot be deleted by Payfer (see “Public blockchain information”). App-scoped identifiers held by developers, and records held by Privy or Stripe, are subject to their retention practices and your requests to them.

We use administrative, technical and organizational safeguards appropriate to the nature of the information, including encryption in transit, hashed storage of developer secret keys, signature verification of allowances, access controls, rate limiting and audit logging. No system is perfectly secure, and we cannot guarantee absolute security. You are responsible for the security of your email account and devices, for keeping developer secret keys confidential, and for reviewing allowances before approving them. If we become aware of a breach affecting your personal information, we will notify you and regulators as required by applicable law.

Subject to applicable law and to exceptions for settlement, legal, tax, accounting, dispute, security and on-chain records, you may request access to, correction of, a copy of, or deletion of your personal information, and may withdraw consent to future collection or use (which may mean the Service can no longer operate your account or allowances). End users can at any time reduce or revoke allowances and stop using the Service; developers can contact support to manage or close their applications.

To exercise a right, email support@payfer.me. We may verify your identity (for example through your account email) before responding, will respond within the time required by applicable law (generally 30 days under Canadian federal privacy law, extendable where permitted, and 45 days under California law, extendable once where permitted), and will explain any information we must retain and why. You will not be discriminated against for exercising a privacy right. If you are in Canada and are not satisfied with our response, you may complain to the Office of the Privacy Commissioner of Canada or your provincial commissioner. California residents may also contact the California Attorney General. Authorized-agent requests are accepted where required by law.

Depending on where you live, additional rights may apply (for example, to limit certain uses or to appeal a denied request). We honour the rights applicable to you. Because the Service is offered only in Canada (excluding Quebec) and the United States at this time, we do not market to or knowingly collect information from residents of Quebec or other countries.

Payfer is a Canadian corporation and uses processors and infrastructure located in Canada, the United States and other countries where our providers operate. Personal information may be processed and stored outside your province, state or country and may be subject to the laws of those jurisdictions, including lawful access by courts and authorities there. By using the Service you understand and, where required, consent to those transfers. We use contractual and organizational measures intended to protect information wherever it is processed.

The Service is for adults only (18 years or the higher age of majority where you live). We do not knowingly collect personal information from children. If you believe a child has provided information, contact support@payfer.me and we will take appropriate steps to delete it, subject to legal retention duties.

Developer applications, Stripe Checkout, Privy authentication and other third-party sites have their own terms and privacy practices, which Payfer does not control. Review them before use. A developer’s own privacy policy governs information that the developer collects through its application; Payfer’s role for app-scoped payments is described in this Policy and the developer documentation.

We may update this Policy from time to time. The updated Policy will be posted at payfer.me/privacy with a revised effective date, and material changes will be announced by posting, email or in-Service notice where required by law. Continued use after an update takes effect means the updated Policy applies to information processed from that time. Privacy contact: A Path is Formed by Walking Inc. (Payfer), support@payfer.me.

See also: Terms of Service. Questions: support@payfer.me