Privacy policy

Information you provide

We process your account email, display name and authentication records to provide and secure your account. You may also provide an optional phone number, profile photo, trade records, CSV imports, notes, strategy tags and journal screenshots. Your phone number is a profile field; it is not used as a sign-in factor.

We use journal information to save and organize your trades, reconcile imports, calculate results and display your trading history. Broker identifiers and source record IDs help associate imports with the right account and avoid duplicates.

Google sign-in

If you choose Continue with Google, Google provides your name, verified email address, Google account identifier and a profile image when available. We use this identity information to create or authenticate your account and link a matching, verified IterateView account without creating a second journal.

We request only basic identity permissions: openid, email and profile. Google sign-in does not give IterateView access to your Gmail messages, contacts, Drive files or financial accounts. Your Google password is entered on Google’s website and is never received by IterateView.

Google access tokens, refresh tokens and ID tokens are used temporarily to complete sign-in and are not saved in our database or provider-account cookies. We retain the account identifier and identity information needed for later sign-ins.

IterateView’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not sold, used for advertising or used to train generalized AI models.

Broker connections and imports

CSV files and manual entries supply trading records that you choose to add. A direct broker connection reads account information and trading history needed to select an account and import available records. Saved trade history remains in your journal after disconnecting.

Broker passwords and verification codes are not saved. Broker access tokens stay only in server memory for a fixed connection period of at most five minutes. Broker refresh tokens are not persisted. A broker may grant broader permissions than the history-reading features implemented by IterateView; review the broker’s own authorization and security settings.

Storage and service providers

IterateView uses Google Cloud for hosting and private image storage, Neon for application and authentication data, and Resend for account and verification emails. These services process information as needed to operate the app. Protected backups and migration archives may also contain earlier account records and files.

Access to journal records and uploaded images is restricted to the authenticated account owner through the app. We do not publish your journal or images as part of importing or connecting an account. Your own downloads and sharing outside IterateView are under your control.

Hosting and security systems may process request information such as IP addresses, browser details, timestamps and error or access records to operate the service and investigate failures or abuse. Information may be processed outside your country through our service providers.

Cookies and browser storage

Essential cookies maintain sign-in, short-lived verification and Google authorization state. If you choose Trust this device, a protected browser cookie and server record remember that choice for a fixed 30 days. You can forget trusted browsers in your account’s Security settings.

Browser storage also remembers your appearance preference and an activity timestamp used for idle sign-out. These settings do not contain broker passwords or tokens. Embedded market widgets, such as TradingView quotes, and external websites may receive browser and connection information under their own privacy policies when you use them. Google may also use its own cookies during Google sign-in.

Retention and your choices

Account and journal records are retained to provide your workspace. Signing out, disconnecting a broker or revoking Google access does not by itself delete your IterateView account or saved journal. Short-lived authentication codes and temporary connections expire separately.

You can edit supported profile fields, remove your uploaded profile photo, export journal records using the available export tools and revoke app access through your Google or broker account settings. Contact ablestdigitalsolutions@gmail.com to request corrections, account removal or help with your data. We may need to verify account ownership and review protected backup or migration copies when handling a request. Security or legal obligations may require retaining some records.

Security and updates

We use encrypted network connections, access controls, private image storage, hashed account passwords and protected authentication cookies. Verification codes are required unless valid browser trust is present. These protections reduce risk; no online service can guarantee absolute security.

We update this notice as the service changes and show the revision date above. A new use of Google user data requires an updated disclosure and any consent required by Google’s policies.

Membership and billing information

When membership billing is available, AblestPay and Stripe process subscriptions for ABLEST SOLUTIONS LLC. Card details are entered only in Stripe-hosted checkout or billing management. IterateView does not receive or store your card number or security code.

We use an application customer reference, selected plan, coupon validation, subscription references, confirmed billing periods and signed status notifications to provide the correct features. We also retain trial start/end dates and reminder delivery records so a trial is not restarted and reminder emails are not duplicated. Trial reminders use your account email through Resend. Payment and invoice details are managed through the payment providers.