OpScout Privacy Policy

Version 1.3 · Effective date: October 17, 2026

This Privacy Policy explains how OSHER MEVIN, INC. ("OpScout," "we," "us," or "our") collects, uses, shares and retains information when you use the OpScout mobile application, websites and related services (the "Service").

Capitalized terms such as Monitor, Alert and Notification have the meanings given in our Terms of Use.

1. Information We Collect

We collect only the information the Service needs for the features you use.

1.1 Account information

• Sign-in identity. When you sign in with Apple or Google, we receive an account identifier from that provider. We may also receive your email address, which can be a private relay address if you use Apple's "Hide My Email," and a display name if the provider supplies one.
• Apple authorization token. If you use Sign in with Apple, we store a token issued by Apple so that we can revoke OpScout's access to your Apple ID when you delete your account.
• Account record. We keep your OpScout account identifier, its status and when it was created.

1.2 Onboarding responses

When you set up OpScout, we ask a few questions, for example:

• what you want to monitor;
• your investing style;
• how often you check the market;
• how quickly you want to be notified.

We store your answers as fixed choices, along with when you started and finished onboarding and when you were shown the subscription screen.

1.3 Monitors, watchlists and preferences

We store:

• the Monitors you create: the securities, conditions, thresholds and options-screening criteria you choose, and whether each was created in the app or through a connected app (Section 1.14);
• your watchlists;
• your settings, such as time zone, locale, currency, notification frequency and delivery preferences.

1.4 Alert history

When a Monitor's conditions are met, we record an Alert. An Alert includes:

• when it was detected;
• the values involved;
• whether a Notification was delivered;
• whether you have seen it.

1.5 Notification settings and delivery records

• Push notifications. When you enable push notifications, we store your device's push token together with:
  • the device platform;
  • the app version;
  • the device language and time zone;
  • when the device was last active.
• WhatsApp (optional). When you link WhatsApp, we store:
  • your WhatsApp phone number;
  • whether and when it was verified. To verify the number, you send a code to OpScout from your WhatsApp account. We keep only a one-way fingerprint of each such inbound message, to prevent it being processed twice.
• Discord (optional). When you link Discord, we store:
  • your Discord user ID and username;
  • the direct-message channel we use to reach you.
• Delivery records. For each Notification, we keep:
  • the channel used;
  • the result of each delivery attempt;
  • any reference number the delivery provider returns;
  • error details if delivery failed.
• Notification limits. We count the Notifications sent to you on each channel in each month, and the Alerts sent to you within the last hour, and keep a record of any pause of your Notifications and when you resumed them.

1.6 Subscription information

You can subscribe in the iPhone app, where Apple processes your payment, or on our website (a "web subscription"), where Stripe processes your payment for us. We do not receive your full payment-card details in either case.

From Apple, or from Stripe for a web subscription, we receive and store:

• product and transaction identifiers, including the original transaction identifier;
• subscription status;
• the current period's start and end dates;
• auto-renewal status;
• the App Store or Stripe environment;
• the subscription notifications Apple and Stripe send us;
• a history of your subscription: each payment with its date, plan, price and any introductory offer, and each renewal, plan change, change to auto-renewal, failed payment, end of the subscription and refund.

For a web subscription, we also store:

• the Stripe customer and subscription identifiers;
• the amounts of payments and refunds, which we use to calculate affiliate commissions;
• where the purchase started: the page, any link it was opened from, and the code of the person who referred you, if any.

We send Stripe your account's email address and account identifier, so that Stripe can bill you and send receipts. When someone who referred you is an affiliate, we compare a fingerprint of the paying card, which Stripe provides, with the fingerprints of that affiliate's own cards, to detect self-referral. We do not store the fingerprint.

If you have an App Store subscription and a web subscription at the same time, we keep a record of how we resolved it under Section 21.4 of our Terms of Use: the two subscriptions, the days they overlapped, and any refund we made, with its amount, its Stripe reference and the brand and last four digits of the card refunded.

We use this information to determine whether your paid features are active, to keep a record of your subscription, to bill web subscriptions, to calculate affiliate commissions, and as described in Section 3.7.

Proof of your consent to automatic renewal. When you subscribe, we keep a record of your agreement that the subscription renews automatically:

• the plan, its price and how often it renews, including any introductory price;
• the exact words you were shown and agreed to;
• the version of our Terms of Use in force, with a fingerprint of its text;
• how you agreed, and when;
• on the web, your IP address and your browser's description of itself (its "user agent").

For an App Store purchase, the record also holds the product, price, currency and any introductory price from Apple's signed transaction.

Subscription emails. For a web subscription, we email you:

• a confirmation when you subscribe, with its terms, how to cancel, and the receipt for your first payment;
• a receipt for each later payment;
• a confirmation when you cancel;
• a notice before an annual plan renews;
• a yearly reminder for other plans;
• a record of any refund we make under Section 21.4 of our Terms of Use.

They go to the email address of your account.

Payment and tax records. For each payment, refund and dispute, whether in the App Store or on the web, we keep a financial record for our tax and accounting obligations: the amounts, any tax, the payment processor's fees, the product and period, and the location used for tax purposes (country, region and postal code, and the country of the card or App Store storefront). It does not include your name or email address.

1.7 Support communications

When you contact us, we keep the type of request, your message, the part of the Service it is about, technical details about the app and your device (such as the screen you came from, the app version and build, the operating system and its version and, where the form shows them, the device model, language, time zone and display settings), the identifier of any record you were viewing, an error message or search text that the form includes, any picture you choose to attach, the request's status, and our replies. The form shows you what it will include before you send it. Your app keeps an unsent draft of your message on your device.

1.8 Shared content

If you create a share link, we create a snapshot of what you chose to share: for example, an Alert, a Monitor, the Monitors you have on one ticker, or a summary of the tickers you monitor. Anyone with the link can view it. If you publish an Alert share as a public page, anyone can find it, including through search engines, until you take it down.

Share snapshots are designed not to include your name, email address, phone number, account identifiers or device identifiers. The exception is a profile share: if you share your profile, the page shows your profile as described in Section 1.15, including, unless you turn it off, the tickers you monitor and how many Monitors and Alerts you have. You can take the page down, and put it back, in Settings → Sharing; while it is down, its link shows only that the profile isn't shared.

1.9 Legal acceptance records

When you accept our Terms of Use or acknowledge one of our disclosures, we record:

• your account;
• the document version;
• the time you accepted;
• where in the Service you accepted it.

When you delete your account, we keep these records without your account. In its place we store a one-way code made from your former account identifier, which tells us which records belonged to the same account; on its own, it does not tell us who you are.

1.10 Technical and security information

Our servers and network may automatically generate technical records when the Service is used, including:

• IP addresses;
• request details;
• timestamps;
• error and diagnostic information.

We use these records to operate, troubleshoot and secure the Service. We also record the day you last opened the app (the day only, not the time or what you did), which is used as described in Section 3.7.

We keep a one-way fingerprint of each device's push token together with the accounts that have used that device, so that we can detect an affiliate earning commission on their own purchase.

1.11 App measurement

We use a mobile measurement service to understand how the app is installed and opened, and to open the right page when you tap an OpScout link. This service receives:

• information about app installs and sessions;
• technical details about the device and app;
• the link that opened the app, which may contain an invite code, a Club's address or a share link's code.

We do not ask for permission to track you across other companies' apps and websites, and we do not use the measurement service to do so.

1.12 Information stored on your device

The app stores some information on your device:

• your sign-in session, in your device's secure storage;
• cached data such as the list of supported securities, your display preferences and service notices;
• copies of your lists and analysis, such as your Monitors, feeds, Journal, Portfolio and profile, kept separately for each account, so that they appear at once;
• drafts of forms you have not sent yet, such as a post, a support message or your profile;
• links you share to OpScout from other apps, until you post or discard them.

This information is stored locally on your device. Copies and drafts are removed when you sign out or delete your account.

1.13 If you take part in our affiliate program

If you are an OpScout affiliate, we also keep:

• your channels: the platforms where you promote OpScout, a link to each, and the audience size you give for each. You add, change and remove them yourself on the partner console;
• your application for complimentary Pro: the channels as they were when you applied, your confirmation that Pro is for your personal use, and our decision and its reason;
• your affiliate agreement and the evidence of your signature: the signed document and its fingerprint; the legal name, postal address, country and email address you typed when you signed; the time of each step; the Google account you signed in with; the IP address and browser you signed from; and an independent timestamp of the signed document;
• your commissions and payouts: what each referred payment earned you, its status, any amount reversed or set off, and what was paid out to you;
• your payout account: you give your identity, taxpayer information and bank account to Stripe, not to us. From Stripe we receive your payout account's status and country, whether it is set up for an individual or a business, what Stripe still needs from you, whether your taxpayer information has been provided (never the number), whether the name Stripe verified matches the name you signed with (never the name Stripe holds), the name of your bank, the last four digits of your bank account number with Stripe's identifiers and fingerprint for it, and the records of each transfer and payout;
• your partner console security: if you turn on two-step sign-in, an encrypted copy of your authenticator secret and one-way fingerprints of your recovery codes; for each browser you sign in from, a one-way fingerprint of a cookie we place in it, a short description such as "Chrome on macOS" and the first part of its IP address; and a record of security events, such as sign-ins from a new browser, changes to two-step sign-in and the security notices we sent you;
• tax reports: the amounts we paid you in each year and the legal name you signed with, which we use to report payments to tax authorities as Section 3.11 describes;
• repayment requests: if OpScout asks you in writing to repay commission (KOL Affiliate Agreement, Section 2.10), the request: the amount, the payments it comes from, when it was sent and when we reminded you, its deadline and how it ended. When you delete your account, your account identifier is removed from it.

We use this information to run the affiliate program: to review your application, to calculate and pay what you are owed, to keep a record of your agreement, to protect your partner console and payouts, and to meet our tax obligations. Your channels and your application are seen only by OpScout staff who review them.

1.14 Connected apps

You can connect OpScout to an AI assistant you use, such as Anthropic's Claude, so that it can see and manage your Monitors when you ask it to. You make the connection yourself, in that app, and approve it on an OpScout page that shows your account and what the app will be able to do. If you connect an app, we keep:

• the connection: which app it is, the permissions you approved, when you connected it, how you signed in to approve it (Google, Apple, or a sign-in code from the OpScout app), whether you have paused it in OpScout, when it was last used, when the app last made a request to us and when we last refused one, when it will end if the app stops using it, and, if it has ended, why. We keep only one-way fingerprints of the codes and tokens that let the app act for you, never the codes or tokens themselves;
• sign-in codes: if you make a one-time sign-in code in the OpScout app, a one-way fingerprint of it, for the 10 minutes it is valid;
• an activity record: each time a connected app creates, changes or removes a Monitor for you, which action it was, whether it succeeded, which Monitor, and when.

Disconnect in OpScout pauses the connection: the app stays connected but cannot see or change your Monitors until you tap Connect in OpScout, which turns it back on with access to all Monitor types; a connection ends when you remove it in the app, or after 90 days without use.

We do not receive or keep your conversations with the app, or what you asked it.

1.15 Your profile

If you set up a profile, we store what you enter: your display name, a short bio, the avatar you choose from OpScout's library, your location as you give it (a country, with a region or city if you add one), your investing focus, your industry and occupation, your university, your hobbies and a personality type, and, if you give them, your birthday, a phone number, your education level and the year you started investing.

• Until you first save your profile, other users do not see your name. After that, other signed-in users see your display name and avatar with your posts, comments, follows and Club memberships. Each avatar in the library belongs to a style of portrait and a personality type, and other users' apps receive which avatar you chose, so they can tell its style and type.
• Your birthday, phone number, education level and the year you started investing are not shown to other users. If a Club's admission test asks for them, you can choose to share some of these facts with the Club's managers (Section 1.17).
• If you share your profile, the share page shows your display name, bio, avatar, the month you joined, your location, investing focus, industry, occupation, university and hobbies and, unless you turn off "Show my watched tickers" in Settings → Sharing, the tickers you monitor with the number of your Monitors and Alerts. It never shows your birthday, phone number or personality type in words. You can take the page down in Settings → Sharing; its link then shows only that the profile isn't shared, until you put it back.

1.16 Posts, comments and other community activity

When you use OpScout's community, we store:

• posts: the title, text and any link, the preview we make of the link, any ticker, the position you disclose and whether the post is paid promotion, the audience you choose, the Club it is in, and when it was posted or edited. To make a link preview, our servers fetch the linked page or the site's preview service, so the site sees OpScout's request, not yours;
• comments and replies;
• likes and dislikes. Other users see the number of likes; the number of dislikes is never shown and is used for moderation;
• posts you save, which only you can see;
• posts you forward to a Club;
• who you follow and who follows you;
• who you block, which only you can see;
• posts you mark "Not interested", which we then leave out of what you see;
• reports you make: the reason, any details you write, and a copy of the reported content as it was when it was first reported, including the account that posted it;
• a safety record: each report, block, unblock and "Not interested", with when and where in the app it happened and, where it concerns a post or comment, a copy of it as it was then. We use this record to keep the community safe and to improve how we rank and moderate content.

Videos. When you play a YouTube video inside a post, the player is loaded from YouTube in its privacy-enhanced mode, and YouTube (Google) receives the video's identifier, your device's IP address and browser details under Google's own privacy policy. We do not send YouTube your account information.

Images. Posts show images from the pages they link to. For posts that everyone signed in can see, our network provider may keep a copy of the image for up to a day.

Deleting. When you delete a post or comment, it is removed from the Service. We keep its text in our systems, not shown to anyone, until you delete your account, and in moderation records as Section 4.4 describes. If you delete your account, a post or comment of yours that other people commented on or replied to stays in its place as "[deleted]", without your name, words, link or picture, so their comments and replies remain.

Explore's lists. Explore's Top Today and Top This Week are counted from likes, comments and forwards. We store the lists with counts only, never who liked, commented or forwarded.

1.17 Clubs

If you create or join a Club, we store:

• Clubs you create: the name, description, topic, tags, picture, rules and settings;
• membership: your role, your status (member, left, removed or banned), how you joined and which link you used, who invited you, when you joined and left, the version of the rules you accepted, and any approval, mute, removal or ban, with its reason;
• join requests: your message and the managers' decision;
• admission tests: the questions you were given, your answers (including answers in your own words), your score, signals noted while you answered (for example answering very quickly or leaving the app during the test), and the facts you chose to share with the managers, such as an age band worked out from your birthday (never the birthday itself), your university, education level and years of investing. A birthday, education level or year you started investing that you enter for a test is also saved to your profile, where only you can see it. A university you enter for a test is kept only with that test and is not added to your profile; your profile and profile page show a university only if you enter it in Edit profile;
• the founder test, if you take it to create a Club: your answers, your score, how long you took, whether you left the app during the test, and a one-way fingerprint of your IP address that changes every day and is deleted after 7 days;
• visits: which Clubs you open, by day. A Club's managers see only how many people visited;
• managers' records: notes a Club's managers write about members, which only they can see, and the Club's moderation log of what managers did and why, including messages they wrote to members;
• scheduled posts, until they are published.

Patreon. If you connect Patreon to open a Club to your patrons, or to join a Club that is open to a creator's patrons, we store your Patreon user identifier, the name on your Patreon account, the permissions you gave, encrypted copies of the access tokens Patreon issues, and your membership of the campaigns that open Clubs on OpScout: your status, your tiers, and the status and dates of your last and next charge. If you are a creator, we also store your campaign's name and address and its tiers and prices, and we read your campaign's member list to keep access up to date. Patreon sends us notices about memberships, which include the patron's Patreon identifier, including for patrons who have not connected OpScout. We do not ask Patreon for your email address or your postal address.

When you disconnect Patreon or delete your account, we delete our copies of the access tokens at once. Patreon does not offer apps a way to revoke their own access, so OpScout stays listed in your Patreon account until you remove it there (patreon.com: Settings → Connected apps). When a Club creator disconnects Patreon or deletes their OpScout account, OpScout deletes the webhook it registered on their Patreon campaign and erases its stored copy of that webhook's secret together with their Patreon tokens; if Patreon can't be reached, the secret is still erased and the webhook stops working, and the creator can remove OpScout's access at Patreon.

1.18 Automated review of posts

We use AI models provided by third parties to review posts on Explore, posts and forwards in Clubs, and Club names, tags and admission tests (Terms of Use, Section 29.5). For a post, we send the model the title and text (up to 2,000 characters of each), the post type, any ticker, the position disclosed and whether it is paid promotion, the linked page's site name, title and description (not the full link), and, in a Club, the Club's name, tags and rules. For an admission test, we send the Club's name and tags and the test's questions and marked answers, never anyone's answers. We do not send your name, email address or account identifier.

We ask our AI model provider to route each review only to model endpoints that keep no copy of what we send (zero data retention) and do not collect it. If none is available, the review does not run, and what was sent for review is treated as not reviewed: a post may be held until a person reviews it, and Club tags or an admission test are not saved until the review can run (Terms of Use, Section 29.5).

We keep the result with the post: the outcome, the labels and scores the model gave, the model used and when. We do not keep a separate copy of the text we sent.

1.19 Journal, Portfolio and your other records

If you use the Journal, the Portfolio, Virtual Performance or Strategy Review, we store what you enter and what we calculate from it:

• trades you record: the strategy, the contracts and shares, prices, quantities, dates, fees, collateral and any margin debit, and rolls, closes, expirations and assignments;
• accounts you add: a name, the kind of account, the name of the institution if you type one, the currency, when it opened, cash balances and any interest rate on cash;
• your holdings and other assets, such as bonds with their identifiers and issuers, and the values you give them;
• deposits, withdrawals, dividends, interest, fees, taxes, currency conversions and your notes;
• the values, returns and other figures we calculate from your records and market data, and the simulated positions of Virtual Performance.

These records are private to you: they are not shown to other users, to affiliates or to Club managers, and our administration tools do not display them. We do not connect to your brokerage or bank accounts and do not import these records from them. Do not enter account numbers or passwords.

1.20 Links you open and invitations

• Your invite link. We create an invite code for you, and any custom ending you choose. The page your invite link opens shows your display name.
• Joining through someone's link. When you open an OpScout invite link, share link or Club link and then sign in, we record who invited you, which kind of link you used and when. If the link belongs to an affiliate, we use this to work out their commission (Section 3.7).
• Counts. We count how many times each invite link and share page is opened each day, without recording who opened it.
• Club links. A Club's invite page shows the name of the person who invited you.

1.21 Information we do not collect

We do not ask for or collect:

• government identifiers, such as a Social Security number (an affiliate's taxpayer information goes to Stripe, not to us);
• brokerage-account or bank-account credentials;
• full payment-card or bank-account numbers;
• your device's location.

We do not connect to your brokerage or bank accounts. Holdings, balances and trades are in OpScout only if you enter them yourself (Section 1.19).

1.22 Copyright notices

If you send a copyright notice or counter-notice (Terms of Use, Section 29.9), we keep it and a record of it: who sent it and how to reach them, the work, where the material was, whether the notice had everything the law requires, and what we did. We use it to handle the notice, apply our repeat-infringer policy and establish or defend legal claims. We send a counter-notice, including its contact details, to the person who sent the notice, as 17 U.S.C. §512(g) requires, and we may give the person whose material a notice concerns a copy of that notice if they ask.

If your content is the subject of a notice, we record your account and the posts concerned with the notice, and material removed on a complete notice and not put back counts toward the repeat-infringer policy. When you delete your account, your account is removed from these records.

2. How We Use Information

We use information to:

• create, authenticate and maintain your account;
• run your Monitors, record Alerts and deliver Notifications through the channels you select;
• link and verify notification destinations, such as WhatsApp and Discord;
• determine and restore subscription entitlements;
• bill web subscriptions, resolve two subscriptions at once, and send the emails about them described in Section 1.6;
• keep proof of your consent to automatic renewal, as the law requires;
• keep the records of payments and refunds that tax and accounting law requires;
• tailor the onboarding experience to your answers;
• show your profile, posts, comments and Club activity to the people who may see them, and run follows, Clubs, share pages and Explore's lists;
• review and moderate content, including by automated review, reports and blocking, keep the community safe, and improve how we rank and moderate content;
• keep your Journal and Portfolio records and calculate the figures shown from them;
• let apps you connect see and manage your Monitors at your request, show you your connections, tell you when a new connection is made, and investigate problems and misuse of connections;
• provide customer support, and tell you when we reply;
• operate, maintain, troubleshoot, secure and improve the Service, and prevent fraud and abuse, including affiliates earning commission on their own purchases;
• record and enforce acceptance of our Terms;
• run our affiliate program, as described in Section 1.13;
• comply with legal obligations and establish, exercise or defend legal claims.

We do not sell your personal information.

3. How We Share Information

We share information only as described below.

3.1 Service providers

We use service providers to operate the Service. They process information on our behalf, as needed to provide their services to us. The categories are:

• cloud hosting and infrastructure;
• network security and content delivery, including keeping copies of public pages and images for a short time;
• authentication (Apple and Google, when you choose to sign in with them);
• push-notification delivery;
• messaging delivery (WhatsApp and Discord, when you link them);
• app distribution and subscription billing (Apple; Stripe for web subscriptions);
• payouts to affiliates (Stripe);
• transactional email delivery, for the emails described in Sections 1.6 and 1.13;
• AI model providers, for the automated review described in Section 1.18;
• independent time-stamping authorities, which receive only a fingerprint of a signed affiliate agreement;
• app measurement (Section 1.11).

3.2 Messaging platforms

When you use WhatsApp delivery, Meta Platforms and WhatsApp process your phone number and the messages we send you, under their own terms and privacy policies. Likewise, Discord processes Discord messages under its own terms.

We do not sell or rent your WhatsApp or Discord contact information.

Mobile information, text messaging originator opt-in data, and consent will not be sold or shared with third parties or affiliates for their marketing or promotional purposes.

3.3 Market data providers

OpScout obtains market data from third-party market data providers and other licensed data sources. To get that data, we send them the security symbols and option-contract identifiers we need. We do not send them your name, email address, phone number or account identifiers.

We do not name these providers publicly, except where law, regulation, contract or a mandatory license attribution requires it.

3.4 Legal and safety reasons

We may disclose information where we reasonably believe it is necessary to:

• comply with law, regulation, legal process or a lawful government request;
• enforce our Terms;
• protect the rights, property or safety of OpScout, our users or others;
• detect and prevent fraud or security incidents;
• handle copyright notices and counter-notices, as Section 1.22 describes.

3.5 Business transfers

If OpScout is involved in a merger, acquisition, financing or sale of assets, information may be transferred as part of that transaction, subject to this Privacy Policy's protections.

3.6 With your direction, and with other users

We share information when you direct us to. For example:

• other users see what you post, comment and do in Clubs, with your display name and avatar, according to the audience and Club settings that apply (Terms of Use, Section 29.2);
• anyone with a share link you create can see what it shares, and anyone can see a page you publish;
• a Club's managers see what Section 3.9 describes;
• an app you connect receives what Section 3.8 describes.

3.7 People who invited you

If you joined OpScout through someone's invite link, share link or Club invitation, and that person takes part in OpScout's affiliate program, they can see a de-identified record of your account, so they can understand how their links perform and check the commission they are owed:

• a member code that stands for you in their records (you can see yours in the app, under Profile, More, Your member code);
• your email address in masked form: the first two characters and the last character before the @, and the domain only when it is a large public email provider (for example, fa•••n@gmail.com; any other domain is masked as well, and an address hidden by Apple is shown only as hidden); and whether you signed in with Google or Apple;
• when you joined, to the hour, and which kind of link you joined through;
• whether you finished setting up the app and whether you viewed the subscription plans;
• each of your subscription payments, with its date and hour, plan, price and any introductory offer, and whether it was made in the App Store or on our website; and each renewal, plan change, change to auto-renewal, failed payment, end of your subscription and refund;
• what each of your payments earned them in commission;
• whether you have opened the app this week, this month, or not since joining.

If they choose to, they receive this information as messages on Discord, as it happens, hourly or daily; those messages name you only by your member code, never by your email. They may mention your member code in their own community, so you can recognise it.

They never see your name, your full email address, your phone number, your payment details, or your Monitors, Alerts, Journal, Portfolio, Clubs or anything else you do in OpScout, and they cannot contact you through this information. Affiliates agree to use it only to understand how their links perform and what they are owed; never to identify or contact you; and never to publish anything from it other than your member code.

This section is about the record an affiliate sees because you joined through their link. If you also follow them, or join a Club they manage, they see what any other user or Club manager would (Sections 3.6 and 3.9).

3.8 Apps you connect

When you connect an app to OpScout, we send it information only when it asks on your behalf, and only what it needs to answer: your Monitors' tickers, company names, rules, status and schedules, your delivery settings for them, whether each was created in the app or in OpScout, and what we recorded about your recent Alerts. If you ask it to check a Target Entry once, we send it the option data our market data provider returns for that check. We never send it your email address, phone number, payment information, notification destinations, or anything about other people.

The app's provider (for Claude, Anthropic) handles what it receives under its own terms and privacy policy, not this one. What the app does with your information, and anything it tells you, is that provider's responsibility.

3.9 Club managers

A Club's Leader and admins see, for their Club:

• its members' display names and avatars, how and when each joined, which link they used and who invited them;
• join requests and their messages;
• admission-test answers and the facts a person chose to share with the Club (Section 1.17);
• reports about posts in their Club, but not who made them;
• how many people visited, but not who;
• their own notes and the Club's moderation log.

3.10 Websites you link to, YouTube and Patreon

• When you post a link, our servers fetch a preview from the linked site (Section 1.16).
• When you play a YouTube video, YouTube receives what Section 1.16 describes.
• When you connect Patreon, we exchange information with Patreon to check memberships (Section 1.17). Patreon handles your information under its own terms and privacy policy.

3.11 Stripe and tax authorities, for affiliates

If you are an affiliate, you open your payout account with Stripe and give Stripe your identity, taxpayer information and bank account under Stripe's own terms and privacy policy. When we start your payout account, we send Stripe your OpScout email address and account identifier. We report what we pay you to tax authorities as the law requires, for example on Form 1099-NEC; Stripe prepares and files these forms for us with the taxpayer information it holds.

4. Data Retention

We keep personal information only as long as the purposes described below require. Different kinds of information are kept for different periods: not everything is deleted after the same time.

4.1 Information needed for an active account or feature

Some information remains for as long as it is needed to provide your account or a feature you are using. This includes:

• your account identity;
• your active Monitor configurations and watchlists;
• your preferences;
• your notification configuration and linked destinations;
• your current subscription state and your subscription history (Section 1.6);
• share links you keep active;
• Alerts you choose to keep, for example by bookmarking or sharing them;
• your profile, posts, comments, likes, saves, follows and blocks;
• your Clubs and Club memberships, including the history of Clubs you have left;
• your Journal, Portfolio and other records (Section 1.19), until you delete them;
• your connections to other apps (Section 1.14), including when the app last made a request and when we last refused one: the record of a connection that has ended is kept, and shown in the app, until you delete your account;
• your Patreon connection, until you disconnect it (our copies of its access tokens are then deleted at once);
• if you are an affiliate, your channels until you remove them, your application for complimentary Pro while it is open or in effect, and your two-step sign-in and browser records while you are an affiliate (Section 1.13); a browser you have not used for 400 days is removed sooner, except the one you used most recently.

Your affiliate agreement, the evidence of your signature, and your commission, payout and repayment-request records are kept for as long as the agreement and any claims under it require, and at least as long as tax law requires, including after the agreement ends.

Records of your acceptance of our Terms and disclosures are kept while your account exists, and after you delete it as Section 4.4 describes.

Cancelling your subscription does not delete any of this. Your OpScout account and its data remain until you delete the account.

4.2 Historical records

Historical service and operational records that are no longer needed for your active account are generally retained for no longer than 90 days. Shorter periods apply where stated. This includes:

• Notification delivery records: 30 days.
• Detailed Alert history: 90 days. After the detailed records are deleted, we may keep summary counts, such as the number of Alerts per month, while your account remains active.
• The history of subscription notifications we receive from Apple and Stripe: 90 days. Your current subscription state is kept, as described in Section 4.1.
• Support communications: kept while your request is unresolved, then deleted, with our replies, 90 days after it is resolved.
• Sign-in codes for connecting an app: deleted one day after they expire (each is valid for 10 minutes).
• The record of what connected apps did for you: 90 days.
• Club visits: 90 days.
• Admission tests: deleted 90 days after you fail a test or it expires, or 90 days after you leave a Club you joined by passing it.
• Patreon's notices about memberships: 30 days.
• Explore's lists: 30 days.

4.3 When you delete your account

Deleting your account removes the personal information under our control from our primary systems. Where our deletion process does so, this happens as soon as you confirm the deletion, and in all cases within 30 days. If you used Sign in with Apple, we also revoke OpScout's authorization with Apple.

• If you have a web subscription, we cancel it with Stripe before your account is deleted.
• Your posts and comments are deleted. Where other people commented on your post or replied to your comment, it stays in its place as "[deleted]", with nothing of yours in it, and their comments and replies remain.
• Your Patreon connection, including our copies of its access tokens, is deleted. Patreon does not let apps revoke their own access; to remove OpScout from your Patreon account, go to Settings → Connected apps on patreon.com.
• A Club you lead passes to another of its managers or members, or is archived if it has none. Clubs you created remain with their members, without your name.
• Forwards you made of other people's posts remain in those Clubs without your name, and moderation actions you took as a Club manager remain in the Club's log without your account.
• Your connections to other apps are deleted, and the apps can no longer reach your account.
• Records of your acceptance of our Terms and disclosures are kept without your account, as Section 4.4 describes.

The exceptions are the information we keep under Section 4.4, and, if you were an affiliate, your affiliate agreement, the evidence of your signature, and your commission, payout, repayment-request, tax and security records, which we keep as described in Sections 4.1 and 4.4. Your channels, your application for complimentary Pro, your two-step sign-in and your browser records are deleted with your account.

If your account is subject to a legal hold, for example because of an investigation or a legal claim, it cannot be deleted until the hold ends.

4.4 Security records and necessary exceptions

We keep security records about access to, and actions taken in, our internal administration tools for 365 days. These records can include information about your account where an action concerned it. Expired or ended administrative sessions are deleted 90 days after they end.

Records subject to an active security, fraud, legal or incident investigation are kept until that investigation no longer requires them. They are then deleted under the ordinary rules above.

We may keep other specific information for longer than described above, but only to the minimum extent, and for the minimum period, reasonably necessary to:

• comply with applicable law;
• meet tax or accounting obligations;
• maintain security;
• prevent or investigate fraud;
• establish, exercise or enforce our legal rights;
• resolve or defend an active legal dispute.

In particular:

• Records of your acceptance of our Terms and disclosures (Section 1.9) are kept for seven years after you delete your account, without your account identifier, so we can show which terms applied, including the arbitration agreement and class-action waiver. They are then deleted.
• Proof of consent to automatic renewal (Section 1.6) is kept for at least three years after you consent, and at least one year after the subscription ends, whichever is later, as California law requires. We keep it for that period even if you delete your account, and then delete it.
• Payment and tax records (Section 1.6) are kept for seven years after the transaction, as tax and accounting law requires, and then deleted. Tax reports, which can include an affiliate's legal name and the amounts paid, are deleted seven years after the period they cover. When you delete your account, your account identifier is removed from these records.
• The payment records of affiliates (Section 1.13), including repayment requests, are kept for at least seven years after the transaction, as tax and accounting law requires. When an affiliate deletes their account, their account identifier is removed from them.
• Moderation and safety records: a report, with the copy of content it holds (which can include the account that posted it), is kept for one year after it is closed; an open report, until it is closed. The safety record (Section 1.16) is kept for one year; after that, for a post you marked "Not interested", we keep only which post it was, while the post exists, so we keep leaving it out. A Club's moderation log is kept for two years. These periods apply after an account is deleted too; records under a legal hold are kept until it ends.
• Affiliate security records (Section 1.13) are kept for one year after each event, including after the affiliate's account is deleted; a record that a notice was sent once is kept while the account exists.
• The founder test (Section 1.17) is kept for one year after it ends, or until you delete your account if sooner. Whether you passed it is kept while your account exists.
• Copyright notices and counter-notices (Section 1.22) are kept for as long as we need them to handle the notice, apply our repeat-infringer policy and establish or defend legal claims.

4.5 Third parties and backups

Information we have already sent to independent third parties remains subject to their own legal and technical retention practices. Examples include:

• Apple, when you sign in or purchase;
• Stripe, when you subscribe on the web or receive payouts as an affiliate;
• Meta and WhatsApp, or Discord, when you use those channels;
• Patreon and YouTube (Google), when you use them through OpScout;
• the provider of an app you connect;
• our email and measurement providers, and our AI model providers (which we ask to keep no copy, Section 1.18).

We cannot control how long they keep it.

Copies of information in backups and system logs may persist temporarily, until they are overwritten through normal secure rotation, where immediate deletion is technically impracticable. While they persist, we protect them and do not use them for any other purpose.

5. Security

We use reasonable administrative, technical and organizational measures to protect information. These include:

• encrypted connections;
• restricted access to production systems;
• storing sensitive values, such as verification codes, sign-in codes and recovery codes, as one-way fingerprints where practical;
• encrypting stored secrets, such as Patreon access tokens and affiliates' authenticator secrets.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

6. Your Choices and Rights

You can:

• view, edit and delete your Monitors and watchlists in the app;
• change your notification channels and frequency;
• manage your linked WhatsApp and Discord destinations;
• turn off push notifications in your device settings;
• edit your profile, and leave out anything you do not want to give;
• choose who can see each post, and edit or delete your posts and comments;
• block other users, and report content and users;
• leave Clubs, and disconnect Patreon (then remove OpScout in Patreon's Settings → Connected apps);
• see the apps you have connected and disconnect them in the app (from then on a disconnected app cannot see or change your Monitors until you tap Connect, Section 1.14); Monitors a connected app created for you stay in your Watchlist until you remove them;
• edit and delete your Journal and Portfolio records;
• take down a share page you published, take down or put back your profile page, and choose whether it lists the tickers you monitor;
• delete your account in the app, under Settings.

Deleting your account does not cancel an App Store subscription. To stop renewal, cancel in your Apple Account subscription settings.

Depending on where you live, you may have the right to ask us to:

• tell you what personal information we hold about you;
• give you access to it;
• correct it;
• delete it.

You may also have the right not to be treated differently for exercising these rights. To make a request, contact support@opscout.us. We may need to confirm your identity first, and we will respond as applicable law requires.

7. Children

You must be at least 13 years old to use OpScout. The Service is not intended for children under 13, and we do not knowingly collect personal information from children under 13.

If you believe a child under 13 has given us personal information, contact support@opscout.us, and we will take steps to delete it.

8. Where Information Is Processed

OpScout is operated by a company based in the United States. Your information may be processed in the United States and in other countries where our service providers operate, which may have different data-protection laws from those where you live.

9. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the version and effective date above. If a change is material, we will give you notice in the Service or by another reasonable method before it takes effect.

Version 1.1 added Section 3.7 (what an affiliate who invited you can see) and the day you last opened the app (Section 1.10).

Version 1.2 added your subscription history (Section 1.6) and subscriptions bought on our website through Stripe (Sections 1.6 and 3.1). In Section 3.7 it added your member code, a masked email that shows more so you can recognise it, each payment and change to your subscription, and the affiliate's Discord messages.

Version 1.3 describes web subscriptions in full (Section 1.6): what we store and send Stripe, two subscriptions at once, proof of your consent to automatic renewal, the emails we send, and payment and tax records. It adds what we keep if you take part in our affiliate program, including payouts and partner console security (Sections 1.13 and 3.11); connected apps (Sections 1.14 and 3.8); your profile, posts, comments, Clubs, automated review and Patreon (Sections 1.15 to 1.18, 3.9 and 3.10); your Journal and Portfolio records (Section 1.19); links and invitations (Section 1.20); support details (Section 1.7); and the retention of each (Section 4). Your birthday and your holdings are no longer listed as information we do not collect, because the profile and the Portfolio let you enter them.

Version 1.3 was amended before publication on 2026-10-16: it adds taking down your profile page and leaving out your tickers (Sections 1.8, 1.15 and 6), how a test's university, Patreon access, the founder test's fingerprint and AI review providers are handled (Sections 1.17 and 1.18), that disconnecting an app in OpScout pauses the connection, when a connection ends, and the record of an app's last request and our last refusal (Sections 1.14, 4.1 and 6), repayment requests (Section 1.13), copyright notices (Section 1.22), "[deleted]" placeholders and acceptance records kept after you delete your account (Sections 1.9, 1.16 and 4.3), and the retention of moderation, tax, affiliate security and founder test records (Section 4.4).

Version 1.3 was amended on 2026-10-18: Section 3.2 adds that mobile information, text messaging opt-in data and consent are never sold or shared with third parties or affiliates for their marketing or promotional purposes.

10. Contact

OSHER MEVIN, INC.
Email: support@opscout.us