FINENZE LLC

PRIVACY POLICY

Last Updated: 16 October 2026

1. Scope of This Privacy Policy

This Privacy Policy (the “Policy”) explains how Finenze LLC, a Wyoming limited liability company (“Finenze,” “we,” “us,” or “our”), collects, uses, discloses, and protects personal information in connection with https://finenze.com (the “Site”), the Finenze application at https://finenze.app and on iOS and Android (the “App”), and the API at https://api.finenze.app. It is one Policy for the Site, the App, and the API. Canonical URLs are /privacy-policy, /terms-of-service, /cookies, and /support.

These pages cover the Finenze Site and App as one product. Accounts, profile, contacts, support, wallets, transfers, invoices, and verification are part of that product. Finenze provides wallets, transfers, bank deposits and payouts, and verification through the Payment Partner, a third-party financial infrastructure provider. The Payment Partner maintains the ledger of record for partner-provided wallets and transfers. Payment Partner terms are described below.

2. Who We Are

Finenze provides payment and digital asset infrastructure for businesses through third-party financial and technology providers. For personal information that Finenze collects directly through the Site and the App, Finenze is the business or controller responsible for the processing described in this Policy. The Payment Partner processes information under its own terms and privacy notice.

Finenze LLC, a Wyoming limited liability company, mailing address 60 Cutter Mill Road, Suite 212, Great Neck, New York 11021, is the controller for personal information it collects through the Site, the App, and the API.

3. Personal Information We Collect

We collect the following categories of information.

Category	What	Source	Why	Stored or forwarded
Site contact	Name and email you submit on a contact form, plus the message you send.	You.	To reply and keep a record of the inquiry.	Where the Site offers a form, the submission is stored and forwarded by Formspree to support@finenze.com. The message is not stored in Finenze account records.
Account and sign-in	Email address, sign-in method (email, Google, or Sign in with Apple), phone number when you add one, and one-time sign-in codes.	You, and Google or Apple when you use those sign-in methods.	To create and secure your account.	Finenze stores the account identifier and sign-in method. One-time codes are used to sign you in and are not kept as a password. Private relay or anonymous forwarding addresses may not match an existing account for wallet-email or invoice access.
App profile	Name, billing address, phone, and an optional business name.	You.	To identify you and to prepare wallet and verification requests.	Finenze stores the profile. Date of birth is not part of the profile. It is collected later for verification and is sent to the Payment Partner.
Legal acceptance	The date and time you accept, and the Terms and Privacy links shown at that time.	You, when you check the box on first Create Profile.	To record that you accepted Finenze’s Terms of Service and Privacy Policy. The checkbox reads: “I agree to Finenze’s Terms of Service and Privacy Policy.”	Finenze logs the date, time, and agreement links shown when you accept. This record is retained after account closure to show assent. Finenze does not store a separate version identifier.
Waitlist	Email address and whether you joined.	You.	To record your request to join the payments waitlist and to send a transactional confirmation.	Finenze stores the join record. The confirmation is sent to your email. Finenze does not send a later launch notice from this list.
Contacts and payees	Names, emails, phone numbers, notes, optional legal name and address, date of birth, nationality, and an id number when you save them, recipient wallet addresses, and bank account details you save on a contact.	You.	To let you reuse recipients for later payments and to tell the Payment Partner who the outside recipient is.	Finenze stores the contacts you save, including wallet addresses and bank account numbers, and the recipient name for an outside address. Saving a legal name while a payments account is open creates one counterparty at the Payment Partner for that contact and stores that id. Later wallets and bank accounts stay on that same counterparty. Add wallet uses that id and the legal name. Add bank uses that id, the legal name, a full address, and any extra fields that bank asks for. Adding a wallet registers the address there, sends the label as the nickname, and stores that partner wallet id. The label can be renamed. The address and the bank account number cannot. A later send uses that counterparty and does not create another one. Paying a saved bank account from Send registers that account with the Payment Partner and sends the quoted amount to that bank. Those details are included in Download my data and deleted from Finenze when you close your account. The Payment Partner may keep the counterparty and the bank account. A send to another Finenze user does not ask for a name. You are responsible for having the right to provide another person’s information.
Wallets and transactions	Wallet status, custodial wallet addresses, transfer amounts, destination addresses, self-owned external wallets, transaction references, and a convert between your own USDC and USDT balances.	You, and the Payment Partner when it reports status.	To open a wallet, to send or receive value, and to move funds between your own balances.	The Payment Partner remains the ledger of record. Finenze also stores a local copy of balances, deposits, crypto transfers, custodial wallet addresses, and self-owned external wallets so the App can open without a live partner read. A self-owned send wallet is one on your own counterparty. Its label can be renamed. The address cannot. A saved self-owned send wallet can be held until review finishes or blocked so it cannot be used. That copy is updated from partner webhooks and is shown on Receive and Activity. A convert between your own balances appears as one outbound activity row. It is not included in Download my data and is not deleted when you close your account. Finenze also keeps a status-change log for each of those money records. The log holds the statuses and times Finenze observed, not every status the Payment Partner passed through, and it has no amounts or message bodies. Staff can read it. A wallet email must be a verified, non-relay address.
Bank deposits and payouts	Bank account details you enter, virtual-account deposit instructions, deposit and payout amounts, corridor eligibility, and the status of those movements.	You, and the Payment Partner for status.	To move funds between your wallet and a bank account, including a bank account saved on a contact.	Finenze sends sensitive banking and identity details to the Payment Partner and stores the payout-account list fields shown in the App, including masked bank details, plus virtual-account deposit instructions and which payout rails are available. Your cash-out list is the accounts on your own counterparty. The label can be renamed. The account number cannot. Activity shows bank deposit and withdrawal status from the ramp records the API keeps, including amount, currency, status, and the on-chain transaction hash when the Payment Partner reports one. Quotes and rates are not stored. Those stored copies are not deleted when you close your account. Finenze also keeps a status-change log for each ramp record. The log holds the statuses and times Finenze observed, not every status the Payment Partner passed through, and it has no amounts or message bodies. Staff can read it.
Verification (KYC/KYB)	One verification: tax identification number, nationality, and identity, proof-of-address, or company documents. A liveness check, if required, opens on the Payment Partner’s page.	You.	So the Payment Partner can verify eligibility for US bank deposits, US withdrawals, and international payouts.	Finenze forwards the tax identification number, nationality, answers, and documents to the Payment Partner and does not keep them on the profile. An audit row for that step may include questionnaire answers other than a tax identification number, document bytes, or a liveness link. Finenze stores one verification status. The liveness link is shown only to you and is not written to logs.
Invoices and payment records	Seller and buyer names, email addresses, addresses, and tax identifiers; invoice business details (name, address, tax ID) and a logo image; an uploaded original invoice file (PDF, PNG, or JPEG); line items; amounts; payment status; and, when the invoice is issued with a US deposit account, that account’s routing and account numbers.	You, for invoices you issue. A billed party or payer may also view an invoice they are party to.	To create a commercial record between you and your customer and to show payment status.	Finenze stores the invoice, the logo, and an uploaded original when you attach one. Issued invoices keep their copied name, address, legal name, logo, and original file after you replace the default logo or close your account. When you issue an invoice and you have an active US deposit account for that asset and network, the invoice also keeps that account’s bank name, beneficiary, and ACH, wire, and RTP routing and account numbers. The PDF and the invoice email show those numbers to the billed party. They are not written to the audit log. Download my data includes the file hash, not the file. You may email the PDF to any address except an Apple private relay address. That send-to address is not stored. Shared links require sign-in. You are responsible for having the right to share your customer’s information. Finenze is not a party to the underlying sale.
Account notifications	A record that Finenze queued an email about a completed or failed transfer, an incoming deposit, a conversion, a bank deposit or withdrawal, a payment to a contact’s bank, verification approval, or an invoice payment or refund. A conversion is not also emailed as a transfer or a deposit. The record includes a notice key, status, and how many times delivery was attempted.	Finenze, when the event happens.	To email you about that event from noreply@finenze.com.	Finenze stores the record with other payment records. It is not included in Download my data and is not deleted when you close your account. The email goes to your verified login address, or to a billed email that is not an Apple private relay when that person has no Finenze account.
Support messages	The category and text of a message you send from Help.	You.	To respond to your request.	Finenze stores the message for 24 months, including after you close your account. It is not included in Download my data. A copy may be emailed to support@finenze.com.
Security and device data	IP address, browser or app type, and security events such as sign-in, sign-out, and account changes. The audit row may include the new name, email, phone, or address from a change you made. Account → Devices lists browsers and phones that opened the account in the last 30 days, with a short label and the last IP.	Your device and our systems.	To operate the service, limit abuse, and keep an audit record.	Finenze stores these events and the signed-in device list. Account → Audit log shows you your own actions, from sign-in through sign-out. Payment-partner events and staff lookups are not shown there. Passwords, one-time codes, and keys are not stored in the log. The raw browser string stays on the audit record and is not shown in the App. Audit records are typically kept for up to 7 years and are not deleted when you close your account. The device list is deleted when you close your account. Neither is included in Download my data.

Scroll the table horizontally to see all columns.

Download my data returns the sign-in email of the account that was open and whether it is verified, your profile, invoice business details when you have saved them (name, address, tax ID, defaults, and logo hash — not the image), hashes of uploaded original invoices (not the files), waitlist status, contacts including saved bank accounts, outside recipient names, wallet-email claim, and the date, time, and links recorded when you accepted. It does not include support messages, invoices, account notification records, audit records, the signed-in device list, the status-change log, or Payment Partner ledger records.

4. How We Collect Information

We collect information directly from you when you use a Site contact form, create an App account, save a profile, join the waitlist, add contacts, complete verification, issue an invoice, or send in-app Help. We collect information automatically from devices, including request logs, audit entries, and the session cookie on the web App. We receive identifiers from Google and Apple when you use those sign-in methods.

Where the Site offers a contact form, submissions go to Formspree, which stores them and forwards them to support@finenze.com. Finenze does not set a shorter Formspree retention period. Submissions are not automatically added to a mailing list.

The Site is hosted on Google Firebase Hosting, self-hosts its fonts, and loads no third-party analytics, advertising, or tracking scripts.

5. How We Use Personal Information

We may use personal information to:

operate, host, maintain, secure, and troubleshoot the Site, App, and API;
create and authenticate accounts, including MFA;
receive, evaluate, and respond to contact and in-app support inquiries;
send an immediate transactional waitlist join confirmation;
send transactional email about a completed or failed transfer, an incoming deposit, a conversion, a bank deposit or withdrawal, a payment to a contact’s bank, verification approval, or an invoice payment or refund, from noreply@finenze.com;
maintain business, legal, security, audit, and correspondence records;
detect, investigate, prevent, and respond to fraud, abuse, security incidents, or unlawful activity;
comply with law, legal process, and enforceable obligations;
protect Finenze, its personnel, users, providers, and third parties; and
evaluate or complete a merger, financing, acquisition, restructuring, sale of assets, or similar corporate transaction.

We do not currently use this information for automated decision-making that produces legal or similarly significant effects, behavioral advertising, or profiling for ads.

6. How We Disclose Personal Information

We may disclose personal information to the following categories of recipients for the purposes described above:

Google Cloud and Firebase, for hosting, database, authentication, SMS delivery for MFA, and abuse protection;
Apple and Google, for Sign in with Apple / Google;
Formspree, for Site contact-form submissions only;
Google Workspace, for receiving and managing transactional and operational email, including invoices from invoices@finenze.com, account and sign-in messages from noreply@finenze.com, account event notifications from noreply@finenze.com, waitlist confirmations, and support notifications to support@finenze.com;
the Payment Partner, for wallets, transfers, bank deposits and payouts, and verification. Finenze sends your name, verified email, billing address, date of birth (individuals), verification data and documents, bank details you enter, destination addresses, and transfer instructions. The Payment Partner processes that information under its own terms and privacy notice;
attorneys, accountants, auditors, insurers, compliance advisors, and other professional advisors;
governmental authorities, regulators, law enforcement, courts, or other parties where disclosure is required or permitted by law or reasonably necessary to protect rights and safety; and
potential or actual counterparties and advisors in connection with a merger, financing, investment, acquisition, sale, restructuring, or similar transaction.

Third-party providers may process information under their own terms and privacy notices.

Payment partner terms. Opening a wallet requires a separate agreement with the Payment Partner. Checking the Finenze Terms and Privacy box does not accept the Payment Partner’s terms. Continue asks Finenze to accept those terms with the Payment Partner. The agreement is recorded only when the partner reports it signed.

Finenze does not currently sell personal information for money or other valuable consideration, share personal information for cross-context behavioral advertising, or use personal information for targeted advertising. The Site and App do not currently use advertising pixels, retargeting tools, advertising SDKs, analytics, crash reporting, or push notifications.

If our practices change, we will update this Policy and provide any notice, consent, or opt-out mechanism required by applicable law before implementing the new practice.

8. Cookies and Similar Technologies

The Site does not use cookies, local storage, analytics cookies, or advertising cookies. Because the Site does not currently use non-essential tracking technologies, no cookie-consent banner is displayed on the Site.

The consumer web App sets a first-party session cookie named finenze_session, lasting up to five days, so signed-in users can reach their accounts. The App may also keep short-lived setup drafts on your device for interrupted onboarding. Details are in the Cookie Policy. The iOS and Android apps do not set that web session cookie.

9. Retention

We retain Site contact submissions for as long as reasonably necessary to respond, maintain records, resolve disputes, protect security, and comply with law. Formspree may retain form information under its terms. Finenze does not set a shorter Formspree retention period.

Closing your account deletes your profile, invoice business details, waitlist entry, saved contacts, and signed-in device list, and signs you out. Logos that no invoice still uses are deleted. Logos copied onto an issued invoice stay with that invoice. Finenze keeps the record of your legal acceptance, account notification rows (user_notice), the verification status (user_compliance), the local copy of balances, deposits, crypto transfers, custodial wallet addresses, virtual-account deposit instructions, payout accounts, self-owned external wallets, and corridor eligibility, and the status-change log kept with those ramp and movement rows. That log is not pruned. Support messages are kept for 24 months. Audit records are typically kept for up to 7 years and are not deleted when you close your account. Payment Partner records follow the Payment Partner’s retention (typically up to 7 years). The web session cookie lasts up to five days.

10. Security

The Site is hosted on Firebase Hosting and delivered using TLS. The App and API run on Google Cloud. Finenze and its providers use administrative, technical, and organizational measures designed to protect personal information, including access limitations, MFA for password accounts, and a secure session cookie on the web App. No security measure is infallible.

Do not submit passwords, private keys, seed phrases, government IDs, bank account credentials, payment card information, or other sensitive information through the public contact form or the in-app Help form.

If we determine that a security incident involving personal information requires notification, we will provide notice as required by applicable law.

Security reports: see security.txt. That file is the disclosure contact (security@finenze.com; Policy /privacy-policy). There is no separate vulnerability-disclosure page. Expires 22 February 2027.

11. International Processing

Finenze is based in the United States. Personal information is processed in the United States and may be processed where our service providers operate. Those countries may have data protection laws different from the laws in your jurisdiction. The product is not geo-restricted. This Policy does not set out a standard-contractual-clause or adequacy schedule.

12. Legal Bases for EEA and UK Visitors

If the European Economic Area or United Kingdom data protection laws apply, we process personal information based on one or more of the following legal bases: your consent; steps requested before entering into a contract; performance of a contract for the App account; our legitimate interests in operating the Site and App, responding to inquiries, developing business relationships, maintaining security, and protecting legal rights; and compliance with legal obligations. You may withdraw consent where processing is based on consent, but withdrawal does not affect prior lawful processing.

13. Your Privacy Rights

Depending on where you live and applicable law, you may have rights to request access to, correction of, deletion of, or a copy of personal information; to object to or restrict certain processing; to withdraw consent; to opt out of certain sales, sharing, targeted advertising, or profiling; and to appeal certain decisions. You may also have the right to lodge a complaint with a privacy or data protection authority.

Signed-in App users may use Account → Audit log to see their own sign-in, changes, and sign-out. Account → Privacy and data → Download my data returns a copy of the sign-in email of the account that was open and whether it is verified, profile information, waitlist status, saved contacts including saved bank accounts, wallet-email claim status, and the date, time, and links recorded when they accepted. A completed profile is required. The export includes invoice business details when saved (text and logo hash, not the image) and hashes of uploaded original invoices (not the files). It does not include support messages, audit records, the signed-in device list, account notification records, passkeys, invoices, the status-change log, or Payment Partner records. Account → Privacy and data → Delete account closes the login and starts the account-deletion process described in Section 9. To submit other requests, email privacy@finenze.com or support@finenze.com. We may request information reasonably necessary to verify your identity. There is no published calendar response window.

14. California Notice at Collection

For California residents, the categories of personal information collected through the Site may include identifiers, professional or business information you provide in an inquiry, communications content, and standard technical request information. Through the App, categories may also include account identifiers, profile information, and financial information (invoices, including seller and buyer tax identifiers; masked bank details; and verification documents forwarded to the Payment Partner). We use and disclose those categories for the business purposes described in Sections 5 and 6.

We do not currently sell or share personal information as those terms are defined by the California Consumer Privacy Act, and we do not use or disclose sensitive personal information for the purpose of inferring characteristics. We retain information using the criteria described in Section 9. If applicable law grants you rights to know, access, correct, delete, or obtain a copy of personal information, you may exercise those rights by contacting us as described below. We will not discriminate against you for exercising a legally protected privacy right.

15. Do Not Track and Global Privacy Control

Because the Site and App do not currently use behavioral advertising, sale, or sharing technologies, browser-based Do Not Track or Global Privacy Control signals do not change current practices. If we later engage in activities for which applicable law requires recognition of an opt-out preference signal, we will implement an appropriate process.

16. Children

The Site and the App are intended for users 18 or older and are not directed to children under 18. We do not knowingly collect personal information from children under 18. Signup and profile do not collect date of birth and do not enforce an age gate. If you believe a child has submitted personal information, contact us so we can investigate and take appropriate action.

17. Third-Party Websites and Services

The Site and App may link to third-party websites or services, including Apple, Google, Formspree, and the Payment Partner. This Policy does not govern third parties, and Finenze is not responsible for their privacy, security, or data-handling practices except to the extent required by law. Review the relevant third-party privacy notice before providing information.

18. Changes to This Policy

We may update this Policy from time to time. The revised version will be posted with an updated “Last Updated” date. Changes apply when posted. A material change does not re-prompt the App and does not use a Finenze version identifier. If a change materially affects how we handle personal information, we will provide additional notice where required by law.