Retro paper trading. Real market data, fake money.

Privacy Policy

Last updated: 11 November 2026

FINZ is operated by Subert Holdings LLC ("we", "us"). This policy explains what we collect, why, who it is shared with, and how to get rid of it. It covers the FINZ website at finz.online and the FINZ apps for iPhone and Android.

The short version

What we collect

DataWhy we have it
Email addressPassword resets and essential service messages. Never shown to other users.
UsernameIdentifies you publicly on the leaderboard, posts and chat.
PasswordStored only as a bcrypt hash. We can't read it and never see it.
Date of birthTo confirm you meet the minimum age of 13. We store the date you enter.
Portfolio and tradesYour in-game cash, holdings, option positions and net-worth history.
Trade historyEach buy and sell you make, kept for 30 days. Used only to count, anonymously, which assets and option contracts players are trading for the TRENDING boxes. No one else ever sees your individual trades there.
Posts, chat messages, replies, votes, followsThe social features. Chat messages under an asset, with their usernames and replies, can be read by anyone using FINZ, including visitors who are not signed in. Posts on the Socials page, profiles and the leaderboard are visible to signed-in users only.
Reports and blocksContent moderation and keeping people away from users they've blocked.
Purchase and promo code recordsWhich in-game cash purchases were credited, so you're never charged twice, and which promo codes you redeemed and when, so each works once per account.
Subscription records (Deep Dive)Only if you subscribe: whether your subscription is active, the date it is paid up to, whether you have cancelled, the references Stripe gives us for you and for your subscription, and which weeks your weekly cash was paid. No card details.
Device token (apps only)Sent to Apple (iPhone) or Google (Android) so notifications reach your device. Only stored while you are signed in and notifications are allowed for FINZ on your phone.
Session tokenKeeps you signed in. Deleted when you sign out, when you reset your password, and automatically after 90 days.
Visitor code (signed out)A random code your browser or the app keeps while you are signed out, so our servers can count requests for market data per visitor rather than per network, and people sharing one Wi-Fi do not share one limit. It says nothing about who you are and is not linked to an account. Our servers hold it only in memory to count requests, and never write it to our database or logs.
Password-reset tokenStored only as a hash, expires after 30 minutes, and is erased as soon as it is used.

What we deliberately do not collect

Who we share it with

We do not sell personal data, and we never hand any company your account: your holdings and trades stay with us, and so do your email and username, with one exception. If you subscribe to Deep Dive, your email and username go to Stripe to run the subscription. Data reaches these companies only for the purpose described:

WhoWhat they receive
AppleiOS app. Your device token, to deliver notifications. Purchase verification for in-app purchases.
Google (Play and Firebase)Android app. Google Play processes in-app purchases, and we ask Google to verify each one. Firebase Cloud Messaging delivers notifications: it receives your device token and the text of each notification, and Firebase's code on your phone creates an app installation identifier to do it. It receives nothing else from your FINZ account.
StripePayment details for purchases made on the website. Stripe processes the card; we only receive a confirmation and an amount. If you subscribe to Deep Dive, we also give Stripe your email address and your FINZ username, so it can keep a customer record for your subscription, send receipts and let you manage or cancel it. Stripe keeps that record under its own privacy policy.
Unusual WhalesOur market-data provider. They receive the ticker symbols our servers request and no user data whatsoever: not your identity, not your holdings.
ResendDelivers our password-reset emails. They receive the address the message is sent to and the message itself, and nothing else.
Amazon Web ServicesHosts our servers and database, and stores our encrypted nightly backups.
Google (AdSense)Website only. Serves the ads on finz.online. Google receives your IP address, browser and the page you are on, and sets its own cookies. It receives nothing from your FINZ account.
Google (AdMob)Both apps. Serves the banner ad in the app. Google's software receives your IP address (used for approximate location), device and app information such as model and operating system version, a device identifier (on Android, your phone's advertising ID), which ads were shown and tapped, and crash and performance data. It receives nothing from your FINZ account.

We may also disclose data where legally required, or to protect the safety of our users.

Advertising

FINZ is free, and advertising from Google is how it pays for itself. The website and the apps use two different Google products, and they work differently.

On the website (Google AdSense)

Google's ad tags load from Google's servers. That means Google, not us, receives your IP address, your browser and device type, and which page you are viewing, and may set or read cookies on your browser to measure and target ads. This is how essentially all web advertising works.

In the iPhone and Android apps (Google AdMob)

A banner at the bottom of the screen comes from Google AdMob, through Google's software built into the app. The website's AdSense code is not in the apps at all.

On both

The ads are the one part of FINZ where a third party observes you directly. What Google does not get from us: your email address, username, date of birth, holdings, trades, posts or anything else attached to your account. We do not pass any of it to them, and the ad code cannot read it.

You can control how Google uses your data for ads at myadcenter.google.com, and review Google's own explanation of how it handles data from partner sites and apps at policies.google.com/technologies/partner-sites. On the website, a browser-level ad or cookie blocker also works; nothing in FINZ depends on ads loading.

What other people can see

FINZ is partly a social product, so some things are public to other signed-in users:

Signed-out visitors can read the chat under each asset, with its usernames and replies, and can see the leaderboard rankings. They cannot see posts in the SOCIALS feed or anyone's holdings. Your email address, date of birth and password are never shown to anyone.

Children

FINZ is not directed at children under 13, and we do not knowingly collect data from them. Registration requires a date of birth and accounts reporting an age under 13 are refused. If you believe a child under 13 has created an account, email us and we will delete it.

How long we keep it

Account data is kept while your account exists. When you delete your account, your profile, holdings, posts, chat messages, replies, votes, follows, purchase and promo code records, subscription records, device tokens and parental-control settings are deleted along with it. If you have Deep Dive, deleting your account also cancels the subscription with Stripe. Stripe keeps its own record of you and your past payments for as long as its policy and the law require; that record is not ours to delete.

Your net-worth history is deleted with the account as well. It used to be kept in anonymised form, and is not any more. Aggregate records required for accounting or fraud prevention may still be retained where the law requires it.

Backups. So that FINZ can be put back together if a server fails, the database is copied every night into an encrypted backup, stored with Amazon Web Services and kept for 35 days. Backups are used only to restore the service. A deleted account disappears from FINZ straight away, and from the last of these backups within 35 days.

Your choices

Depending on where you live you may have additional rights over your data, including access, correction, deletion and portability. Contact us and we'll honour them.

Security

Passwords are stored as bcrypt hashes. Traffic between the app and our servers uses HTTPS. Payment card details never touch our systems. No system is perfectly secure, but we don't retain data we don't need, which is the most effective protection available.

Changes

If we change this policy we'll update the date at the top of this page. Material changes will be announced in the app.

Contact

Questions about privacy, or a request about your data? Use the contact button on our support page.