AstroEngine Get Access

Privacy

This page covers this website, the AstroEngine app and dashboard, your AstroEngine account and paying for Access.

This website

The pages of this website set no cookies, run no analytics and load nothing from other companies. Cookies are used only on your account pages, the download sign-in page and the dashboard, described below.

Signing in with Google

You sign in to your account with Google. We ask Google only for your email address and your Google account ID, not your name or picture. We store those two things:

  • Your Google account ID.
  • Your email address, updated to Google's current one each time you sign in.

Google must report your email address as verified. We check that when you sign in and do not store the answer.

Cookies on your account pages

Your account pages set two cookies. They are sent only to those pages, and scripts on a page cannot read them.

  • ae_customer keeps you signed in. It lasts 12 hours, and signing out clears it.
  • ae_customer_signin protects the sign-in step. It lasts 10 minutes, and finishing sign-in clears it.

Cookie on the download sign-in page

ae_download keeps you signed in to a download page that has its own username and password. It is sent only to that page, and scripts on a page cannot read it. It lasts 12 hours, and signing out clears it.

Cookies on the dashboard

The dashboard uses up to three cookies.

  • ae_trader keeps you signed in. It is sent only to dashboard pages, and scripts on a page cannot read it. It lasts 12 hours, and signing out clears it.
  • ae-unit remembers the display unit you pick, such as $ or %. It is set when you pick one and is sent only to dashboard pages. Scripts on a page can read it. It lasts one year, and signing out does not clear it.
  • ae-streamer makes the dashboard hide amounts and account names. The app sets it, only in its own Dashboard page, while Streamer covers the Dashboard, and removes it when Streamer stops covering it. Scripts on a page cannot read it.

What the dashboard keeps in your browser

The dashboard also keeps three settings in your browser's local storage.

  • ae-privacy remembers whether you chose to hide amounts.
  • ae-theme remembers whether you picked light or dark.
  • ae-trades-filters remembers your last filters on the Trades page: the search text, account, symbol, side, result, month, copied or not, and the sort order. It is kept only while a filter is on, and it goes when you press Clear filters or set every filter back to all.

Page scripts read these, and the first two are not sent to us. When you open Trades, the page puts your remembered filters in the address, so they reach our server as a normal page request. Local storage has no end date, and signing out does not clear it. On a shared browser, the next person to use the dashboard can see what you left there, including your last search. Clearing this site's data in your browser removes all three. In the app's Dashboard page, unlinking the computer or linking another trader clears them, along with the cookies there.

Payment

Stripe handles your card details. You enter them in Stripe's checkout and billing portal, not on our pages, and AstroEngine never sees them.

When you start checkout, we send Stripe your email address, or your Stripe customer ID if you already have one, and our own ID for your account.

What we keep about a subscription

  • Your Stripe customer ID and subscription ID.
  • The subscription's status, the end of the current billing period, and whether it is set to cancel then.
  • When your account record was created and last changed.

We also log each Stripe event we process: its ID, its type and when it arrived.

Connecting the app

To connect the AstroEngine app to your account, you confirm a one-time code that works for 10 minutes. We store only a hash of it. We then store your TradingView user ID and username with your account.

When you connect, we store a public key for that install. After that, each time the app checks in we store your platform, the app version, a machine ID and the time.

Your trades

If you link a computer to your AstroEngine account, the app records your closed trades and uploads them to your account. This happens on its own while the computer is linked and you are signed in to TradingView as the linked user. There is no separate switch for it: to stop recording, unlink the computer on the app's General page. Unlinking keeps your account and the trades already uploaded.

The app reads only Tradovate and NinjaTrader connections, so trades on TradingView's Paper Trading are not recorded. Demo accounts on those connections are recorded too. Trades from a firm login that the app's copier drives are recorded to your account as well. A copied trade also keeps the name or ID of the account it was copied from.

For each trade we keep the account's name and broker account ID, the broker, whether the connection is demo or live, the symbol, side, quantity, entry and exit times and prices, point value, gross and net P&L, commission when we have it, and the computer that sent it. We also keep each fill's ID, time, price, quantity, side and commission. We keep nothing else from the upload. Balances, passwords and broker sign-in tokens are not part of it.

Trades waiting to upload stay in a file on your computer, so a restart or an outage does not lose them. If you import a file from Tradovate or Rithmic, we keep the trades in it and the file's name, kind and row counts, but not the file. We keep your trades until your trader account is deleted: nothing removes them after a set time.

Your journal and screenshots

The journal keeps what you write: notes, tags, mood and confidence on a trade, and your plan, review and mood for a day. You can add up to 6 screenshots to a trade. Only you can open your screenshots, and they are not part of anything shared with friends or mentors. If you use Rules, we also keep your rules, your lockouts, the breaks you report and the entry acknowledgements the app records.

Where it is stored

Your trader account, trades, journal and rules are in a PostgreSQL database at Amazon Web Services in the United States. Its storage is encrypted, and only our server can connect to it directly. The dashboard runs on Vercel, so your data passes through Vercel when you open it. Screenshots and custom card backgrounds are image files, stored outside the database in a private Cloudflare R2 bucket.

Who can see it

Nothing is shared until you choose. On the Sharing page you choose one setting for all your friends and a separate one for each mentor. Each setting names the accounts to include, how much to show and the unit, such as % or $. Only the accounts you tick are included, and their names are masked. Totals shows your daily results, win rate and badges. Every trade also lists each trade, and in $ or points it shows size, prices and fills.

If you share your journal, that person sees your notes, tags and mood on trades in those accounts, and your plan and review for days in the last 30 on which those accounts traded. You can also let a mentor see your rules, breaks and lockouts, and end a mentor's access after 30, 90 or 180 days. Changes apply right away. Removing a friend, ending a mentorship or blocking someone stops what they can see.

Each time a friend or mentor opens your data we log who viewed what, by the hour, and the Sharing page shows you the last 90 days. We keep that log until your trader account is deleted.

If you join a mentor's weekly board, the mentor and the other students on it see your username, trade count, average R, profit factor and rules score for that week. If you make a P&L card, anyone with its link can see your username, its figures and masked account names. A card for one trade, or a card with trades switched on, also shows those trades with their prices and fills. We ask search engines not to list card pages. If your recorded trades earn the Verified record mark, it shows beside your name unless you hide it on your Marks page.

The people who run AstroEngine can reach the database and the image files. Our team pages do not show your trades, journal or screenshots. They do show reports people make about a card or comment: the reason someone gave and any comment reported.

Deleting your trades and journal

The dashboard has no button yet to delete your trader account or a single trade, and no way to download your trades or journal.

You can delete a screenshot in the journal, which removes its record and then its file. You can delete a P&L card, which stops its link and removes its custom background. The card's record, with the figures it showed, stays in our database until your trader account is deleted.

To delete your trader account, write to us at the address below. Deleting the account removes your image files first: your journal screenshots and your cards' custom backgrounds. If any file cannot be deleted, your account and its records stay and we tell you; files already removed stay removed. It then removes these from the database: your trader record with your TradingView ID, username and email, your accounts, trades, fills, import records, journal, tags, rules, lockouts, cards, friends, mentors, sharing settings, view log, linked computers and the crash and bug reports linked to your record. Your P&L card links stop working. Comments you wrote on someone else's thread stay there without your name, and so do rules you proposed to a student.

The delete does not change your customer record or subscription record, described above. It does not reach your computer either: unsent trades stay in the app's file there. If you were given a protected add-on, we keep the personal copy made for you and a record that it was served, both named with your TradingView ID. The delete does not remove them.

A deleted record stays in our backups until they expire. An older copy of the database, from before we moved to AWS in November 2026, is still held at Supabase. A delete does not reach it until we remove that copy. AWS keeps automatic database backups for 1 day. We also make an encrypted backup each night, kept in a separate AWS S3 bucket. Each nightly backup can be restored for 14 days and is removed about 28 days after it was made. We do not take one person's data out of a backup, so deleted data can last in backups for about 28 days.

Crash and bug reports

The app sends crash and bug reports to us. The version customers install sends them too. It sends a crash report on its own, with no prompt, when it hits an uncaught error, when its window stops, when an update fails or when one of your scripts reports an error. While the app is running, it sends the same crash at most once an hour. It sends no crash report until it knows your TradingView identity. A bug report goes only when you send one, with Report a bug on the General page or Send report on a problem the app shows. Report a bug sends what you write, up to 4,000 characters.

Every report holds a message, the app's version, your platform, the app's recent log and the app's state. A crash message is the error and where in the app's code it happened. The log is the last 500 lines the app wrote while running, with any error details, and we keep up to 20,000 characters of it. The state holds your TradingView username, the file names of your scripts and whether each is on, the app's status, what your access allows and when the app last checked in. The app sends your TradingView ID with a report, and we use it to link the report to your record. If the app does not know your identity yet, a bug report goes with the app's machine ID, and we keep that ID in the report.

Before a report leaves your computer, the app removes from its message and log any cookie lines, bearer tokens, the value after words such as password, token, session, secret, key or sign, and any run of 32 or more letters and numbers. It finds these by pattern, so it can miss something. It does not look for names, email addresses, symbols or file paths, and a file path can include your computer's user name. The username and script names in the state are sent as they are. There is no setting to turn crash reports off.

Reports are stored in the same database as your trader account, so they are in its backups too. Nothing removes a report after a set time. Deleting your trader account deletes the reports linked to your record. It cannot reach other reports, such as one sent with only the app's machine ID, or with a TradingView ID we had no record for. Those stay. To ask us about them, write to us at the address below. Our team can read a whole report on its team pages: the message, the state and the log. Friends, mentors and other traders cannot see reports.

Deleting your data

To ask us to delete what we hold about you, write to astroengine123@gmail.com.