Owlets Terms of Service and Acceptable Use Policy

Effective 2026-11-20. Last updated 2026-11-20.

Part A. Owlets Terms of Service

A1. Agreement

  • These Owlets Terms ("Terms") are an agreement between you and Owls Insight LLC ("Owls", "we", "us").
  • They cover Owlets: the hosting service at owlets.app, the Owlets console, Owlet servers, the data relay, the notification relay, the credential broker, the app hub and the Owlets marketplace (together, "Owlets").
  • The Owls Insight Terms of Service (owlsinsight.com/terms) still govern your Owls Insight account, plan and data. If the two conflict on anything about Owlets, these Terms win.
  • The Acceptable Use Policy (Part B), the Builder terms (Part C) when you build an app for the hub, and the Subscription terms (Part D) when you subscribe to a paid app, are part of these Terms.
  • You accept these Terms by ticking the box when you order an Owlet, start an app on the hub or subscribe to one. The page shows the version you accept, and we record it. If you use Owlets for an organization, you confirm you can bind it.

A2. What Owlets is

  • An Owlet is a virtual server we create for you on DigitalOcean, in the region you choose, after you pay.
  • There are two kinds:
    • Sealed Owlet: runs first-party Owls tools (marketplace tools from other developers come later). It has no internet access and holds no secrets. It can reach only Owls-run services: the data relay and the notification relay, and the credential broker once trading is available.
    • Private Owlet: runs your own code, with normal internet access, under Part B. It is never listed in the marketplace and never runs anyone else's marketplace tool.
  • Apps on the hub: apps made by independent developers ("builders") and reviewed by us before they are listed. They run on Owlets' shared servers, sealed like a Sealed Owlet: no internet access, no secrets inside. One copy of each app runs, started by its builder. You subscribe to an app on its page on owlets.app, see its messages in Your alerts, may also have it post to your Discord, and unsubscribe from "Your subscriptions". We sell every app on the hub (A9a, Parts C and D).
  • Credential broker: the Owls service that places and cancels orders in your exchange account for tools in your Sealed Owlets, within the limits you set. Tools never see your exchange credentials.
  • Data relay: fetches Owls Insight data for tools in your Owlets, using a read-only data key linked to your own Owls Insight account.
  • Notification relay: sends tool alerts only to destinations you registered.
  • Marketplace: tools written by other developers for your own Sealed Owlets. Not available yet; we will add their terms before it opens.
  • We may change, add or remove features, regions and venues. Where a change removes something you paid for, A4.7 applies.

A3. Eligibility and your account

  • You must be 18 or older, and at least the minimum age each venue you trade on requires.
  • You need an Owls Insight account. A free one is enough to subscribe to an app on the hub (A9a). A paid Owls Insight plan is required only for tools and apps you run that declare they use Owls data (A9), including an app you build (Part C).
  • One person per Owlets account. Do not share your login.
  • Every exchange or prediction-market account you connect must be yours, in your own name, funded with your own money. You may not connect, manage or trade anyone else's account, and you may not pool money with others (Part B).
  • You may not use Owlets if you are on a U.S. sanctions list, or if you are in, or ordinarily resident in, a country or region under comprehensive U.S. sanctions (A6).
  • Keep your login secure. Use a passkey or two-factor sign-in.

A4. Billing, on-demand creation and destroy-on-cancel

A4.1 Prepaid, monthly. Owlets are billed monthly, in advance, in US dollars, through Stripe. Prices are shown on owlets.app. Tax is added where we are required to collect it. Charges appear as OWLETS BY OWLS.

A4.2 Created only after payment. We create an Owlet only after your first payment for it succeeds. You pick the region from the list we offer. Creation usually takes minutes, but we do not promise a time or that a region has capacity. If we cannot create your Owlet within 24 hours, we refund that payment in full.

A4.3 Renewal. Each Owlet renews automatically every month until you cancel. You authorize us to charge your payment method on each renewal. You can cancel online at any time in the Owlets console.

A4.4 Failed payment. If a renewal fails, we retry it and your Owlets dashboard says so. The Owlet keeps running for up to 72 hours. If payment still fails, we destroy the Owlet (A4.6).

A4.5 Cancelling. If you cancel, the Owlet runs to the end of the period you paid for, and then we destroy it. There is no refund for the rest of the period.

A4.6 Destroyed means deleted. When an Owlet ends for any reason, we destroy it. We do not stop or pause it. Its disk, files, code, logs and state are permanently deleted. We keep no backups of Owlets. Export anything you need before the period ends. Before we destroy an Owlet, the credential broker cancels open orders that tools in that Owlet placed. We do not close your positions. Our own records (A18) are kept separately.

A4.7 Refunds. Owlets fees are non-refundable, with these exceptions:

  • duplicate charges and billing errors we confirm;
  • an Owlet we could not create (A4.2);
  • subscriptions to apps on the hub, for the unused part of the period, pro rata, when an app is not running, or gets no data, for more than 72 hours in a row, or we remove it, for a reason that is not your fault (A9a.6 and Part D);
  • the platform-fault remedy (A13);
  • where the law requires a refund.

If an outage caused by Owls takes an Owlet down for more than 24 hours, we give you a pro-rata hosting credit for the time it was down.

We never refund trading losses. Losses on orders a tool placed within your limits are yours.

Contact support@owlsinsight.com about any charge within 14 days, and before you file a chargeback.

If you are a consumer in the EU or UK: you have 14 days to withdraw from an Owlets subscription. If you ask us to start your Owlet within those 14 days, you agree that it starts at once, and if you withdraw you pay for the days used. The same applies to a subscription to an app on the hub: you ask us, when you subscribe, to start it at once; to withdraw within 14 days, email support@owlsinsight.com, and we refund what you paid less the days it ran (days of a free trial are not counted).

A4.8 Price changes. We give at least 30 days' notice by email before a price increase affects a renewal.

A4.9 Apps on the hub: what you pay.

  • Subscribing to a free app costs nothing.
  • A paid app costs its monthly price, set by its builder and shown on its page, plus tax where it applies (A4.11).
  • There is no other charge for a subscription. You need no Owls Insight plan to subscribe.
  • A builder's own app reads data under the builder's own Owls Insight plan (C13) and pays no hosting until hosting charges begin (C15).

A4.10 Billing for paid apps.

  • Each subscription to a paid app is its own monthly subscription. It is billed in advance, in US dollars, through Stripe, from the day you subscribe (or from the end of its free trial, if it has one), and renews every month until you cancel. You authorize us to charge your payment method on each renewal.
  • Free trials. Some paid apps start with a free trial, shown on the app's page and at checkout before you subscribe. You give a payment method at checkout, but nothing is charged during the trial. If you cancel before it ends, you pay nothing and the app stops posting to you when the trial ends. If you do not, the first month is charged when the trial ends. One trial per app for each account: subscribing to the same app again is charged from the day you subscribe.
  • You see the price, with tax, before you pay. Charges appear as OWLETS BY OWLS.
  • Your price, before tax, is fixed for your subscription. If a builder changes an app's price, the new price applies only to people who subscribe afterwards.
  • Owls Insight LLC sells every app on the hub, including apps made by independent builders, and is the seller of record (Part D).

A4.11 Tax. Sales tax, VAT and similar taxes are added on top of the price where we are required to collect them, based on the billing address you give at checkout. If we must start collecting a tax where you are during your subscription, we tell you by email before it is added to a renewal.

A4.12 Failed renewal. If a renewal fails, we retry it and "Your subscriptions" says so. The app keeps posting to you for up to 72 hours after the period you paid for. If payment still fails, the subscription ends and the app stops posting to you. If the first charge after a free trial fails, the app stops posting to you within 12 hours of the trial's end, and starts again if the charge goes through.

A4.13 Unsubscribing. You can unsubscribe from an app at any time in "Your subscriptions", or cancel a paid one through Manage billing.

  • A free app stops posting to you at once.
  • A paid app keeps posting to you to the end of the period you paid for, then stops, and is not renewed. There is no refund for the rest of the period, except under A4.7.
  • In a free trial, a paid app keeps posting to you to the end of the trial, then stops, and you are not charged.
  • If its payment is overdue when you unsubscribe, or you never completed payment, the subscription ends at once and you are not charged again.

A5. Trading through Owlets: the credential broker

Trading through Owlets is not available yet. This section applies once it is.

A5.1 Your account, your orders. Orders placed through Owlets go to your own account at the venue. They are your orders, at your risk. Venue rules make you liable for every order under your account (for example Polymarket US Rulebook 5.2(e) and Kalshi Developer Agreement 4.2).

A5.2 Owls never holds withdrawal rights. We never ask for, accept or store a credential that can withdraw or transfer money out of your venue account. If a credential you give us has those rights, the broker refuses it.

A5.3 Kalshi.

  • You create a Kalshi subaccount, fund it, and create an API key limited to read and trade (read, write::trade) on that one subaccount. You do this on your own computer with our open-source helper. Your full Kalshi key never leaves your computer, and the restricted key is sealed on your computer before upload.
  • Kalshi requires its Advanced API tier for subaccounts. Kalshi grants Advanced only after at least one recent order was placed through the API, so the helper walks you through one.
  • The broker checks the key's scopes with Kalshi and refuses any key with transfer rights or wider access.
  • Kalshi documents that such a key may only read and trade on that subaccount and cannot transfer funds between subaccounts. It can still trade, so you can lose the whole subaccount balance. Fund the subaccount only with money you can afford to lose.
  • Kalshi has not approved or endorsed Owlets. Kalshi's Developer Agreement limits API use to a member's own trading, and Kalshi may restrict or close accounts at its discretion. By connecting Kalshi to Owlets you accept that Kalshi may treat this as third-party access and restrict your account.

A5.4 Polymarket US. Live only after Polymarket US accepts Owls as a partner.

  • You authorize Owls, through Polymarket US's partner access, to place and cancel orders for your Polymarket US account. That access includes order rights and no funding rights (write:orders, never write:funding).
  • If Polymarket US requires its own authorization form under its Rulebook, you sign it before trading there.

A5.5 Polymarket international.

  • You authorize a session key from your Polymarket Deposit Wallet, for order placement only. Polymarket documents that a session key cannot withdraw funds from the Deposit Wallet.
  • A session key expires after 180 days. Only you can revoke it, by signing a revocation from your wallet. Revocation takes several minutes and cancels that key's open orders. We give you a one-click page to do it.
  • Your own Polymarket account view does not show orders placed with a session key. Our order log does (A5.9).
  • Orders carry Owls' builder code for attribution. The builder fee is zero. We will give 30 days' notice before any change.

A5.6 Your limits. You set the limits for each Owlet and each tool: notional caps, loss stops, market allowlists and order sizes. The broker refuses any order outside them. Raising a limit needs a fresh passkey confirmation. Lowering one takes effect at once.

A5.7 Our limits. The broker also applies its own protections, for example price collars, refusing very new liquidity, probation caps on new tools and versions, state gating and automatic halts on bad fill quality. They may block, shrink or delay orders a tool wants to place. They exist to protect you, but we do not promise they will catch every bad trade, and we are not liable for orders they block or miss.

A5.8 Stop everything. The console has a stop button. It cancels the open orders your tools placed through the broker and stops new ones. We aim to finish within 10 seconds while the venue is reachable, but we do not guarantee it. It does not close positions.

A5.9 Order log. The broker keeps a tamper-evident log of every order, cancel, fill and limit decision for your account. You can view and export your own log.

A5.10 Prices. Execution prices come from the venue through the broker. Owls Insight data, including market and fair-value data, is for signals. It can be delayed and is never an executable price.

A6. Venue eligibility

  • You may trade a contract through Owlets only if the venue allows it for you, where you physically are when the order is placed, and where you live.
  • Physical location decides. When trading through Owlets is available, you will state your country, state or province, and residence before you can trade, and we will check your IP address when you buy, at each Owlet launch and at each console sign-in.
  • The Owlet region never changes eligibility. Choosing a region only changes the network path from your Owlet to our broker. We never place or move a bot anywhere to get around a venue's location rules.
  • United States. If you are in the United States, you may trade Polymarket only through Polymarket US. You may not use Polymarket international.
  • Polymarket international presence check. Opening a new position needs a check-in from an eligible location in the previous 24 hours. Without one, your Owlet can only reduce positions on that venue, and we notify you.
  • State restrictions. Some U.S. states bar some contracts, especially sports contracts, on Kalshi or Polymarket US. The broker blocks orders where our state table says the venue does not offer the contract or a court or regulator has barred it. We update the table weekly from public sources, so it can lag. You remain responsible for following the law where you are.
  • No VPNs. Do not use a VPN, proxy, Tor, remote desktop, or any other tool to appear to be somewhere else, for Owlets or for any venue. Our support will never suggest one.
  • Sanctions. Owlets is not available in, or to residents of, countries and regions under comprehensive U.S. sanctions (as of 2026-10-21: Cuba, Iran, North Korea, and the Crimea, so-called Donetsk People's Republic and so-called Luhansk People's Republic regions of Ukraine), or in any country a venue blocks. When trading through Owlets is available, we will also screen names against U.S. sanctions lists.
  • If we have reason to believe you are not eligible, we may switch your Owlets to reduce-only, stop them, or close your Owlets account.
  • Venues are independent. No venue sponsors, endorses or is affiliated with Owlets unless it says so in writing.

A7. No advice. No guarantee of results.

  • Owls does not give investment, trading, financial, tax or legal advice. We do not recommend contracts, choose trades or decide what any tool does.
  • You choose each tool, its settings and its limits. Tools are software. They can be wrong, lose money and stop working.
  • Event contracts are risky. You can lose everything in a funded subaccount or wallet.
  • Past results, including results Owls displays (A8), do not predict future results.
  • Laws and venue rules on event contracts are changing. A change may force us to restrict or stop a feature, a venue or a tool, sometimes without notice.

A8. Performance display rules

  • We show trading results only from fills the broker recorded and settlement data from the venue. Builders and users cannot submit results.
  • Your own results are shown to you for your own account.
  • Public results for a tool version are computed across all active, unaffiliated buyers of that version. They are never the best single account. They show: the number of buyers, the median return after venue fees, the share of buyers losing money, the maximum drawdown, the number of fills and events, and the period.
  • No public verdict until at least 20 unaffiliated buyers have run the version for at least 30 days.
  • Buyers linked to the seller (same card, same billing identity, or a venue account the seller declared) are excluded.
  • Paper-mode results are labelled as simulated, kept apart, and never mixed into live results.
  • No backtests, earnings claims or testimonials appear on listings.
  • You may share your own results. You may not say or imply that Owls endorses a tool or verified your personal results, except by linking to Owls' own public page for that tool.

A9. Owls data inside Owlets

  • A paid Owls Insight plan is needed only for tools and apps you run that declare they use Owls data. Their page shows the minimum plan. Subscribing to an app on the hub needs no plan (A9a).
  • When you connect Owlets to your Owls Insight account, we create a read-only data key for it. It can fetch data. It cannot create webhooks or use the bet-slip features. The data relay holds it sealed. Tools never see it.
  • The data key is one of your account's API keys and has your plan's limits, like any other key. One data key serves all of your Owlets.
  • Owls data reaches the tools and apps you run under your own plan and the Owls Insight Terms. You may not redistribute it, except as A9a and Part C allow. What an app you subscribe to sends you is made from its builder's data, under Part C.
  • Notifications go only to destinations you set up yourself, and an app's messages also to Your alerts (A9a.4). A9a.9 says when an app may post where other people can read it.
  • If your Owls plan lapses or drops below the minimum of a tool or app you run, it stops getting Owls data. Apps you subscribe to do not use your plan; A9a.6 says what happens when one stops.

A9a. Apps on the hub

  1. How an app on the hub runs. One copy of each app runs on Owlets' shared servers, started by its builder. It fetches Owls Insight data through the data relay with its builder's read-only data key, under the builder's Owls Insight plan and its limits. The app never sees that key, and neither do you. It does not use your Owls Insight account, your plan or any key of yours.
  2. Who can subscribe. Anyone who may use Owlets (A3) and signs in with an Owls Insight account. A free account is enough. You accept these Terms when you subscribe.
  3. Price. A free app costs nothing. A paid app costs only its monthly price, shown on its page, plus tax where it applies. You see every charge before you pay. A4.9 to A4.13 say how billing works, and Part D applies to paid apps.
  4. Where it posts. While you subscribe, an app's messages show in Your alerts on owlets.app, each for up to 7 days. Your alerts shows each app's newest messages, so a busy app's older ones leave sooner. Your alerts is always one of your destinations, and in these Terms an app "posts to you" there too, so when it stops posting to you (A4.12, A4.13) its messages leave Your alerts. You can also have it post to Discord channels you choose (Telegram later), when you subscribe or later on the app's page while it is listed, and change or turn that off there. A channel a subscription uses cannot be removed until you move it, turn Discord off or the subscription ends. Its messages in Discord end with a line naming the app and owlets.app.
  5. Limits. We may limit how many people can subscribe to an app, so an app can be full. We may also limit how often an app may post. A message over a limit may be delayed or not delivered.
  6. If an app stops. An app can stop for all its subscribers: its builder stops it, its builder's Owls Insight plan lapses, or we pause or remove it (A12). A short gap while its builder restarts it is normal. If its builder stops it, free subscriptions end at once and paid ones are not renewed. If an app is not running, or gets no data, for more than 72 hours in a row, or we remove it, for a reason that is not your fault, every paid subscription to it ends and we refund the unused part of the period, pro rata, from when it stopped.
  7. Unsubscribing. You can unsubscribe at any time from "Your subscriptions" (A4.13). We keep a record of your subscriptions, when you started and ended them, and the Discord channels each one posts to (only your latest choice), for your account history (Privacy Notice).
  8. Apps belong to their builders. An app made by an independent developer (its "builder") belongs to that builder. We sell your subscription under these Terms and, for a paid app, Part D. We review every app and every version before it is listed or updated: that it runs sealed, holds no keys, reads only the data it declares and follows our listing and data rules (Part C). We do not review it for accuracy or results, and A7 applies to it as to our own tools. The builder never receives your personal data, your destinations or your Owls Insight account details: they see how many people subscribe, how many ratings are new or changed, and the money, never who; if you rate or review the app, they see what is public (A9a.12). We may pause or remove any app at any time (A12).
  9. What you may do with its messages. You may point an app at a Discord server you run that other people can read, as long as its messages arrive there as the app sent them, with the line Owlets adds. Not into a server or channel people pay to join. Do not remove that line, and do not copy, resell or republish the messages anywhere else.
  10. What apps never do. Apps on the hub are tools: they watch data and post alerts, digests or numbers. They never place bets, never tell you what to bet (picks), and never offer prizes, contests, leaderboards with prizes or entry fees. A pick names a bet to place. A price, a line move or a number worked out from the data is not a pick. Their listings and messages make no earnings, profit, ROI or win-rate claims. If you see an app that does, tell us at support@owlsinsight.com.
  11. Apps made by Owls Insight. If we list an app of our own, its page says how it runs and what it costs before you start it. If it runs as your own copy, it reads data with your own read-only data key, under your own plan, and its requests count toward your plan's limits.
  12. Ratings and reviews. If you subscribe to an app, you can rate it from 1 to 5 stars and write a review of it. Only subscribers can, and never the app's builder. You get one rating for each app. You can change it while you subscribe and rating is open, and delete it at any time from the app's page. What is public on the app's page and its reviews page:
    • your rating and review;
    • the name you choose, never your email;
    • when you posted it;
    • how long you had subscribed.

    Write about your own use of the app. Do not post any of these:

    • anything false or misleading;
    • someone else's personal information;
    • links or advertising;
    • abuse, or anything unlawful;
    • a rating or review you were paid or given something for.

    We show every rating and every written review, whatever its score. We remove one only when it breaks these rules or the law, and then we tell you why. If we remove yours, you cannot rate that app again. You can still delete its words, but we keep a record that we removed it: the stars and the dates. Do not take a name that could be mistaken for Owlets or for the app's builder.

    The builder may answer each written review in public under it. An answer follows the same rules and makes no earnings, profit, ROI or win-rate claims. A builder must never:

    • rate their own app;
    • post as a subscriber;
    • offer anyone anything for a rating or review.

    A review is its writer's opinion, not ours. Reviews we write ourselves are marked "Our review" and say that we earn a share of app sales. You give us a non-exclusive, worldwide, royalty-free licence to show your rating and review on Owlets for as long as you leave it there.

  13. The record. An app can attach to an alert up to eight prices the alert is about. Each names the game, the selection (for a player prop, the player, the stat and over or under), the line if it has one, the book and the price, and optionally the app's fair price. For each one we keep:
    • the app, the copy and channel it posted from, which alert it came in and its place in that alert, and when we received and stored it;
    • the game and the start time the app gave, the market, the selection, the line, the book, the price and the fair price, and for a pick'em line its multiplier;
    • after the game, the last price we have from that book for the same selection and line before the game started (the closing price), and for a price with a line, that book's main line for the same selection then (the closing line). If we have no closing price, the price does not count in the price figures.

    A price an app sends again within 10 minutes, the same in every field, is kept once, with the alert that first carried it. If our service fails before a price is stored, that price is lost; nothing is removed once stored.

    The app's page shows its record: how many prices it holds, how often a price that counts was better than its closing price, and by how much on average; and, for prices with a line that pass the two checks below and have a closing line (pick'em lines aside), by how many points on average their line was better or worse than the closing line, even when the price has no closing price. We keep the record ourselves. We only add to it: nobody changes or removes what it holds, the builder and we included. A price counts only if it was offered at that book in the two minutes before we received the alert. Prices received after a game started do not count. When one alert names the same selection and line at several books, those prices count once in each figure: the best of them that counts under this section, against its own book's close.

    A pick'em line's price is the app's own break-even, never one the board offered, so it never counts in the price figures. The record shows, apart from them, how often a pick'em line was better for its side (lower for over, higher for under) than the last line we have from the board for the same player, stat and side before the game started, and by how many points on average. A line counts only if the board showed it in the two minutes before we received the alert, we received it before the game started, and we have that last line.

    The record compares prices with closing prices, and lines with closing lines. It is not a profit, ROI or win-rate figure, it does not say anyone will win, and past prices do not predict future ones. A builder may link to it but may not restate it as an earnings claim (C5.3).

A10. Your content and Private Owlets

  • You own the code and data you put on a Private Owlet. You are responsible for it, including its security, licences and any keys you store there.
  • You give us a licence to store, run, scan and transmit it as needed to provide Owlets, keep it secure and enforce Part B.
  • Credentials you store on a Private Owlet are not protected by the credential broker. If you trade from a Private Owlet, use credentials that cannot withdraw.
  • We keep no backups (A4.6).

A11. Acceptable use

Part B applies to every Owlet. Breaking it can lead to quarantine, suspension or termination without refund.

A12. Suspension, quarantine and kill switch

  • We may, at once and without notice where needed, do any of these:
    • pause, stop or remove an app on the hub, or one of its versions everywhere;
    • stop or remove a tool from your Owlets, or stop a tool version everywhere (the "kill switch");
    • cancel open orders the broker placed, or switch an Owlet to reduce-only;
    • quarantine an Owlet (cut its network access, stop it, or both);
    • destroy an Owlet, or suspend or close your Owlets account.
  • We do this for security, a suspected breach of these Terms, a venue's instruction or rules, a legal or regulatory reason, a sanctions match, eligibility doubts, a DigitalOcean request, fraud or payment risk, or to protect other users.
  • We tell you what we did and why as soon as we safely can.
  • If the cause is not your fault (for example we remove an app from the hub), we refund subscriptions as A9a.6 says and unused hosting days pro rata. If the cause is your breach, no refund.
  • A kill switch cancels orders. It does not close positions.

A13. Platform-fault remedy

  • Platform fault means one of these, shown by our order log:
    • the broker sent an order that broke a limit you had set and confirmed;
    • after we acknowledged your stop request, the broker sent a new order for that Owlet;
    • the broker sent an order for an Owlet that had already been destroyed or for a tool you had removed.
  • Not a platform fault: losses on orders within your limits; a tool's strategy or bugs; market moves; venue outages, delays or rejections; delayed Owls data; your own settings or mistakes; anything a venue did.
  • Remedy: we pay you the net realized loss on the faulty orders, after any gains on them, from venue fills and settlement. The most we pay is the Owlets fees you paid for the month in which the fault happened.
  • Claim at support@owlsinsight.com within 30 days, with the order IDs. We answer within 15 business days and pay by refund or credit.
  • This is your only remedy for a platform fault. It counts toward the cap in A15.

A14. Disclaimers

Owlets, all tools and apps (ours and builders'), the delivery of their messages, the broker and all data are provided "as is" and "as available". To the extent the law allows, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement. We do not promise that Owlets will be uninterrupted, secure or error-free, that any order will be placed, cancelled or filled, or that any tool will make money.

A15. Limitation of liability

  • We are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, trading losses, missed trades, lost data or lost opportunity, however caused, except under A13.
  • Our total liability for all claims relating to Owlets is limited to the Owlets fees you paid us in the one month before the event giving rise to the claim, or US$100, whichever is greater.
  • Some places do not allow these limits. There, our liability is limited as far as the law allows.

A16. Indemnity

You will indemnify and defend us against claims, losses and costs (including reasonable lawyers' fees) arising from your Private Owlets, your code, your trading, your breach of these Terms or of a venue's rules, or your violation of law or of anyone's rights.

A17. DigitalOcean pass-through

  • Owlets runs on DigitalOcean. For DigitalOcean's purposes you are an "End User" of our account.
  • You must follow DigitalOcean's Terms of Service as they apply to End Users and DigitalOcean's Acceptable Use Policy, as each is updated. Part B includes the main AUP rules, but the DigitalOcean texts also bind you.
  • We are responsible to DigitalOcean for your conduct, and DigitalOcean may suspend services even for a violation committed unintentionally. So we may act on any DigitalOcean notice or request about your Owlet at once (A12).
  • Tell us at support@owlsinsight.com at once if you learn of a security incident on or involving an Owlet. We must notify DigitalOcean and help any investigation. You must help us.
  • Answer any abuse notice we forward to you within 24 hours.
  • Use only the IP addresses we assign to your Owlet. Do not probe, scan or test DigitalOcean's systems.
  • We are not liable if DigitalOcean suspends, limits or ends a service. If that happens through no fault of yours, we refund unused prepaid hosting pro rata.
  • Your Owlet's data is stored in the DigitalOcean region you chose.

A18. Privacy and records

  • For Owlets we collect what the Owlets Privacy Notice lists, and use it as that notice says. When trading through Owlets is available, we will also collect your location statements, venue account identifiers, your limits, the order log and sanctions-screening results, and we will update the Privacy Notice before we do.
  • We use them to provide Owlets, keep Owlets secure, and answer support and legal requests; once trading is available, also to check eligibility and sanctions and to compute the results in A8.
  • Builders never see your personal data, orders, fills, balances or logs (Part C).
  • We keep: the order log for 5 years (when trading exists); billing records for 7 years; tool and security logs for 30 days, longer for an open investigation. Owlet disks are deleted when destroyed (A4.6).
  • The Owlets Privacy Notice at owlets.app/privacy gives the details.

A19. Changes and termination

  • We may change these Terms. For a material change we give at least 15 days' notice by email or a clear notice in the console. If you do not agree, cancel before the change takes effect.
  • You may close your Owlets account at any time. If you close your account, your subscriptions end (paid ones without refund, A4.7 aside); a builder's app stops (A9a.6). We may end Owlets for you under A12, or end the Owlets service with 30 days' notice and pro-rata refunds of unused fees.
  • When your account ends, all your Owlets are destroyed (A4.6). A5.1, A5.9, A7, A13 to A16, A18 and A20 survive.

A20. Governing law and disputes

  • California law governs these Terms, without regard to conflict-of-law rules.
  • First try to resolve any dispute with us in good faith. If it is not resolved within 30 days, either side may go to the state or federal courts located in California, which have exclusive jurisdiction.
  • Mandatory consumer protections where you live still apply.

A21. General

Entire agreement (these Terms with the Acceptable Use Policy, Parts C and D when they apply, and the Privacy Notice), severability, no waiver, and assignment follow Owls Terms 18.2 to 18.5. Contact: Owls Insight LLC, support@owlsinsight.com.

Part B. Owlets Acceptable Use Policy

B1. Scope

  • This policy applies to every Owlet, Sealed and Private, to the Owlets console, and to anyone who uses them.
  • You are responsible for everything that runs on your Owlets, including code you did not write.
  • It adds to the DigitalOcean Acceptable Use Policy, which also binds you (A17).

B2. Banned on every Owlet

Crypto mining and mining-adjacent work. No:

  • mining any cryptocurrency, by CPU or any other means;
  • proof-of-space or storage farming, plotting, or "proof of work" solving for others;
  • mining pools, mining proxies, or stratum connections;
  • blockchain validator, staking or full-node operation (a light client that only reads what your own trading needs is allowed);
  • bandwidth-sharing, "earn by sharing your connection" or proxyware apps;
  • anything that hides or throttles itself to avoid CPU detection.

Network attacks and scanning. No:

  • port, vulnerability or network scanning of any system you do not own (and none of DigitalOcean's at all);
  • denial-of-service traffic, floods, stress tests or amplification;
  • unauthorized access, credential stuffing, brute force, or exploit delivery;
  • crawling that impairs a system, or that gets around rate limits, IP blocks, CAPTCHAs or other access limits.

Spoofing and impersonation. No:

  • forged packet, email or message headers, or traffic that hides its origin;
  • impersonating a person, company, venue or Owls;
  • phishing pages or forms that collect credentials or payment details.

Spam and mail.

  • Outbound mail ports 25, 465 and 587 are blocked on every Owlet. Do not try to send mail over SMTP or get around the block.
  • No unsolicited bulk messages by any channel, including email APIs, Discord, Telegram or SMS.
  • No action that gets Owlets IP addresses on a blocklist.

Malware. No viruses, worms, ransomware, stealers, botnet agents, command-and-control servers, or code that hides what it does.

Anonymity and relay services. No open proxies, open mail relays, open DNS resolvers, VPN servers, Tor relays or exit nodes, or proxy services for others.

Getting around venue geoblocks. No:

  • using an Owlet, or its region, to make you appear to be somewhere you are not, for any venue, sportsbook or service;
  • tools that help anyone else do that;
  • routing trading traffic through VPNs, proxies or another person's location.

Wagering operations. No:

  • running a sportsbook, betting exchange, casino, lottery, pool, or a contest with entry fees and prizes;
  • accepting bets or trades from others, or taking the other side of others' bets;
  • placing bets at sportsbooks by automated means;
  • selling picks or tips as a service from an Owlet.

Managing others' money. No pooled funds, shared bankrolls, staking, copy trading or mirror trading, trading another person's account, or "follow this wallet" or insider-tracking tools.

Market abuse. No spoofing or layering of orders, wash trades, self-trades, manipulation, coordinated trading to move a market, or trading on material non-public information. Follow every venue's rules.

Sanctions. No use by, for or on behalf of a sanctioned person, and no use from or for a comprehensively sanctioned country or region (A6).

Unlawful content. No illegal content, child sexual abuse material, content that infringes intellectual property, or content that threatens or incites violence.

Resource abuse. No use that degrades other users or shared systems. No use of IP addresses not assigned to your Owlet.

Security research. No probing, testing or security research on Owlets, Owls Insight or DigitalOcean, except under a written disclosure programme we publish.

B3. Sealed Owlet rules

  • Do not try to reach the internet, the cloud metadata service, raw sockets, DNS, or anything other than the local gate.
  • Do not try to break out of the tool container, read other tools' data, or tamper with the Owls agent.
  • Do not use market orders, order books or timing to pass signals into or out of a tool.
  • Do not try to extract, copy or decompile an app or a marketplace tool, or to obtain an app's builder's key.
  • The same rules apply to apps on the hub. Do not use an app to get around an Owls Insight plan's limits or to share Owls Insight data beyond what A9a and Part C allow.

B4. Private Owlet rules

  • Private Owlets run your own code only. You may not list, sell, rent, resell or share them, or run services for other people on them.
  • Only you use a Private Owlet. Do not give others shell access.
  • Inbound, only SSH (port 22) is open, and only your own SSH key can log in. You may narrow it further with your own firewall rules. Outbound mail ports 25, 465 and 587 are closed.
  • If you trade from a Private Owlet with your own credentials, A6 still applies in full: the Owlet's region never makes you eligible.
  • Compute-heavy work (for example model training) is allowed if you choose a size that fits it. Near-full CPU for several hours in a row (6 hours by default) cuts the Owlet's internet access automatically until a person reviews it (B5, B6).

B5. Monitoring

  • We watch Owlets for abuse signals: sustained high CPU, outbound bandwidth, the rate of new outbound connections (the Owlet's firewall limits it, and repeated hits count as a signal), and abuse reports. Mail ports are closed, not watched.
  • We use network and resource metadata. We do not read your files or traffic content unless an investigation needs it.
  • Sealed Owlets are also checked by the app review (Part C).

B6. Enforcement ladder and quarantine

  1. Automatic quarantine (minutes). A strong abuse signal or a DigitalOcean notice cuts the Owlet's network access or stops it. A quarantined Private Owlet keeps running and can still reach Owls' control servers, but not the internet, and SSH closes with it. Trading tools on a Sealed Owlet go reduce-only. Your Owlets dashboard shows the quarantine at once, and we email you when a person reviews it.
  2. Review (within 24 hours). A person reviews it. A false alarm is released, with a pro-rata hosting credit.
  3. First minor breach. Written warning. Fix it within 24 hours and we release the Owlet.
  4. Second breach within 90 days, or no fix. Suspension: no new Owlets, the affected Owlet stays quarantined, and we destroy it after 7 days if not fixed.
  5. Severe breach, or a third breach. We destroy all your Owlets and close your Owlets account, without refund. We may report to DigitalOcean, venues and authorities, and suspend your Owls Insight account under Owls Terms 7.
  • Severe breaches include: mining, malware, attacks, sanctions breaches, geoblock evasion, market abuse, child sexual abuse material, and any breach that puts the Owlets DigitalOcean account at risk. They skip straight to step 5.
  • Before destroying an Owlet for a severe breach, we may keep a disk snapshot as evidence for up to 90 days.

B7. Reporting and appeals

Part C. Builder terms (apps on the hub)

C1. Agreement

  1. Part C is part of the Owlets Terms. It applies to you as a builder: when you submit an app to the hub, start it, list it, or open a payout account. Parts A and B also apply to you.
  2. You accept Part C when you first start an app on the hub, and each new version when you next start it. The page shows the version, and we record it.
  3. If you build for a business, you confirm you can bind it.
  4. Founding builders. Up to 15 builders, each confirmed by us in writing. The terms we confirmed to you in writing are part of your agreement. Where they give you more than Part C, they win.

C2. Who sells and who is paid

  1. Owls Insight LLC ("we") sells subscriptions to every app on the hub, in its own name. We are the seller of record: we run checkout, issue receipts, collect tax, decide refunds, handle chargebacks and answer subscribers.
  2. We pay you a share of what subscribers pay for your app (C7), as a licence fee for it. You are not our employee, agent or partner.
  3. A share we hold is not money held for you in trust. It is not escrow and earns no interest.

C3. Eligibility

  1. You must be 18 or older and must not be on a U.S. sanctions list (A3, A6).
  2. To sell, you need a payout account (C8). At launch, payout accounts are open only to people and businesses in the United States, with a U.S. bank account and a U.S. taxpayer ID.
  3. Anyone who may use Owlets may list a free app, after review (C4).
  4. One payout account per person or business.
  5. Your app runs on your own Owls Insight plan (C13). Using Owls data outside Owlets stays under your plan and the Owls Insight Terms.

C4. We review every app and every version

  1. We review every app, and every new version of it, before it is listed or updated. Nothing reaches subscribers until we approve it.
  2. We check that the app runs sealed and reaches nothing but the hub's gateway; holds no keys and asks no one for keys, passwords or personal data; reads only the data it declares, and none that C12.3 forbids; and is a tool under C5. We check that its listing and its messages follow C5 and C12.
  3. We may refuse any version. Where it is safe to, we say why. A refused version never runs; the last approved version keeps running.
  4. We do not review apps for accuracy or results.
  5. Why we review. Card networks and payment processors do not allow sports forecasting or odds-making with a prize, or entry fees that promise a prize. Reviewing every app and every version before it is listed is how we make sure nothing like that is sold on Owlets.

C5. What an app may be (listing rules)

  1. Apps are tools. They watch data and post alerts, digests or numbers to their subscribers' destinations.
  2. An app must never place bets, tell anyone what to bet (picks or tips), or offer prizes, contests, leaderboards with prizes or entry fees. It must never ask subscribers for keys, passwords or personal data. A pick names a bet to place. A price, a line move or a number worked out from the data is not a pick.
  3. No earnings claims. No earnings, profit, ROI or win-rate claims and no guarantees, in your listing or in your app's messages. No backtests or testimonials in a listing.
  4. Your listing (title, summary and setting labels) says in plain text what the app does, what it sends and how often, and how many data calls it makes. The builder kit's listing rules give examples and are part of Part C; where they differ, Part C wins.
  5. Your app's messages carry its output only: no advertising, no links except to the app's page on owlets.app, and no asking subscribers to pay, sign up or contact you outside Owlets.
  6. Do not copy another builder's app.
  7. Models. A model publishes numbers (win probabilities, fair prices, projected lines), never picks. It can have a price once we have kept at least 30 days of its forward record, which nobody can edit. Until we keep records for models, a model is free.

C6. Your price

  1. Your app is free, or has a monthly price in whole US dollars from $1 to $499. You set it on your builder page.
  2. A price change applies only to people who subscribe after it. People already subscribed keep the price they subscribed at, free included, for as long as their subscription lasts.
  3. Subscribers pay only your price, plus tax where it applies. There is no other fee for subscribing.
  4. A free app earns you nothing.
  5. A paid app is on sale only while your payout account can receive transfers (C8).

C7. Your share

  1. For each payment a subscriber makes for your app (a "sale"), your share is: (what the subscriber paid for your app, excluding tax, minus the card processing fee on it) x your rate.
  2. The card processing fee is the fee our payment processor charged on that payment. When the payment also carries tax, your app bears only the part of the fee that matches the price's part of the payment; the part on the tax is ours.
  3. Your rate:
    • Founding builders: 90% on sales paid within 12 months after your first paid sale, then 85%.
    • Everyone else: 80%.

    Your first paid sale is the first successful payment for any of your apps.

  4. Nothing else comes off your share. We pay every other cost of selling your app and paying you, including our payment processor's fees for payout accounts, payouts and tax forms, its tax-calculation fee, and any tax we pay ourselves under C10.5. Hosting (C15) is not part of this calculation.
  5. Refunds and chargebacks reduce your share (C9).
  6. Example (a card fee of 2.9% plus 30 cents, no tax): a subscriber pays $10.00 for your app. The card fee is $0.59. Your share is ($10.00 - $0.59) x 90% = $8.46 as a founding builder in your first 12 months, or x 80% = $7.52. Card fees vary; we use the real fee on each payment.
  7. We work out each share per sale, to the cent, rounding down. Nothing in Part C promises any subscriber, sale or earnings.

C8. Holds and transfers

  1. We hold each sale's share for 14 days after the subscriber's payment succeeds, in case of a refund. Then we transfer it to your payout account.
  2. Your payout account is a Stripe account you open from your builder page. You give your identity, bank and tax details to Stripe, on Stripe's own pages. We never receive your bank account number or your full taxpayer ID. Stripe's Connected Account Agreement, which you accept there, applies between you and Stripe.
  3. We set your payout account to pay out weekly, on Mondays: Stripe sends your available balance to your bank, which usually shows it within a few business days. Bank holidays, Stripe's own checks or a balance below zero (C9.4) can delay or reduce a payout. Your Stripe dashboard shows each payout. We may change the payout schedule with 30 days' notice.
  4. Until your payout account can receive transfers, your shares wait. We send them once it can.
  5. While a payment is disputed, its share waits until the dispute closes.

C9. Refunds and chargebacks

  1. As the seller, we decide refunds.
  2. A refund is shared over the payment's price and tax in proportion to their amounts, and reduces your share by your rate times the price's part of the refund; the card fee stays deducted. If we have not yet transferred the share, we transfer the reduced share. If we have, we reverse that part of the transfer. A refund never takes more than that sale's share.
  3. A chargeback works the same way: we reverse your share in proportion to the part of the payment the subscriber's bank takes back. If we win the chargeback, we pay that part of your share again.
  4. A reversal can leave your payout account's balance below zero. Stripe then recovers it from your later payouts, and the agreement you accept with Stripe applies.
  5. We reverse a transfer only for a refund, a chargeback or an error of ours. Never as a fine.
  6. Refunds we make because your app was not running, or got no data, for more than 72 hours, or was removed (A9a.6), reduce your share like any other refund.

C10. Taxes

  1. You are responsible for your own income taxes.
  2. You give Stripe your tax details (what a Form W-9 asks for: your legal name, address and SSN or EIN) when you open your payout account, or later when Stripe asks.
  3. Where the law requires, we file a Form 1099 for what we paid you. Stripe files it for us and sends you a copy, by email if you agree and otherwise by post.
  4. If the law requires us to withhold tax from your share (for example because your taxpayer ID is missing or wrong), we will.
  5. As the seller, we collect sales tax, VAT and similar taxes where we are required to, and pay them. Your share is worked out on the price without tax. Where we owe a tax on a sale that we did not add to its price (for example VAT owed before we are registered to collect it), we pay it from our part, and your share is worked out as if that tax did not apply.

C11. Your code and our licence

  1. Your app is yours. There is no exclusivity: you may sell or publish it anywhere else.
  2. You give Owls Insight LLC a non-exclusive, worldwide licence to build, review, host, run, list, describe and sell subscriptions to each version you submit, and to deliver its messages to subscribers, on Owlets. Your share (C7) is the only payment for this licence.
  3. The licence lasts while the app is listed, and after that until the last paid subscription to it ends.
  4. We keep a copy of every version we built, for security, audits and disputes.
  5. You confirm you have every right needed for what you submit, including under the licences of the code and packages you use.

C12. What your app may read and send, and our consent

  1. Our written consent. Owls Insight LLC consents in writing, for the purposes of the Owls Insight Terms (including their sections 5 and 7) and these Terms, to your app's messages, made from Owls Insight data fetched with your data key, reaching your app's subscribers' destinations, and to our selling subscriptions to your app, while it is listed on the hub and keeps to C12.2 to C12.4. Within these conditions your listed app is not a shared, multi-user or public deployment, selling subscriptions to it on Owlets is not reselling or sublicensing API data, and it is not, by itself, a product that replicates the core functionality of Owls Insight. This consent covers only what your app delivers through Owlets. It ends for an app when the last paid subscription to it ends after you delist it, or at once when we stop or remove it.
  2. What your app may send. Its own alerts, digests or numbers: what your code works out from the data or picks out of it. Never copies of API responses, full odds boards or data feeds. Every message keeps the line Owlets adds, naming the app and owlets.app; your app must not hide or imitate it.
  3. What your app may not read or send. Betting-splits data, or anything made from it. Data from prediction markets, or anything made from it. We may add a data source to this list when its terms require it, with notice under C20, or at once if the source requires it at once.
  4. Your app may not export or resell Owls Insight data, or keep it for any use other than working out its own messages.
  5. Your use of Owls Insight data outside Owlets, and anything done with your keys outside your app, stays under your plan and the Owls Insight Terms. C12.1 does not extend to it.

C13. Running your app, and your plan

  1. One copy of your app runs on the hub. You start it from your builder page, and it posts to the channels you pick and to each subscriber's. For now each builder may run one app on the hub; we may raise that.
  2. Your app fetches data with your read-only data key, under your Owls Insight plan. Its requests count toward your plan's per-minute limits and monthly requests, like any other use of your account. One copy runs however many people subscribe.
  3. Keep a plan that covers your app. You must keep an Owls Insight plan that includes the data your app reads for as long as your app is listed or anyone has a paid subscription to it. If your plan lapses, the app pauses for all its subscribers within about three days. If your plan drops below the data it reads, it keeps running without that data, and we may pause it. Past 72 hours, A9a.6 applies and C9 applies.
  4. When you start your app again, its subscribers move to the new copy. There is a short gap while it restarts. If the new copy fails to start, the app is down until you start it again.
  5. Subscribers never receive your key or your code.

C14. Subscribers' privacy

  1. You never receive subscribers' personal data. Your builder page shows counts and money: how many subscribers each app has, sales, refunds, chargebacks, your shares and transfers. Never who.
  2. Your app never learns where it posts. The notification relay delivers its messages to each destination.
  3. Your app may not try to identify subscribers or collect personal data.
  4. If a subscriber's question needs you, we pass it on without their name or contact details.

C15. Hosting

  1. Founding builders (C1.4): hosting is included until 2027-03-01. Nothing is billed for it before then, and we tell you its price by email at least 30 days before your first hosting charge. Other builders: hosting is charged from when your app is listed, at the price your builder page shows before you list it.
  2. Hosting covers running your app on Owlets' servers. It does not include Owls Insight data. Once hosting charges begin for you, each app you run on the hub costs the hosting price shown on your builder page, billed monthly in advance through Stripe, whether the app is free or paid. We tell you by email at least 30 days before any change to that price. You can stop your app before a change takes effect.
  3. Hosting is charged separately from your shares and is never taken out of them.
  4. If a hosting payment fails, we retry it for up to 72 hours. If it still fails, your app stops, and A9a.6 applies to its subscribers.
  5. Hosting fees are non-refundable, except as A4.7 says.

C16. Your responsibilities

  1. You are responsible for your app and your listing. A16 (indemnity) applies to them.
  2. Tell us at support@owlsinsight.com at once if you find a security problem in your app or lose control of one of your accounts.
  3. A14 and A15 apply to Part C, but nothing in A15 limits our duty to pay shares you earned under C7. We do not promise that any app will be approved, placed or subscribed to, except the placement promised in writing to founding builders (C1.4).

C17. Stopping, delisting and removal

  1. You may stop your app at any time. It stops posting at once: free subscriptions end, paid ones are not renewed, and A9a.6 applies. To stop selling or delist an app while it keeps running, ask us at support@owlsinsight.com: no one new can subscribe, and paid subscriptions keep posting to the end of their period and are not renewed. Shares for sales already made are paid as usual.
  2. Keep your app running until the last paid subscription to it ends. If it is not running, or gets no data, for more than 72 hours in a row before then, A9a.6 refunds its paid subscribers, and C9 applies.
  3. We may refuse, pause, delist or stop any app at any time if it breaks Part B, Part C or the law; for security; at the request of a payment processor or our hosting provider; or to protect subscribers (A12). We tell you what we did and why as soon as we safely can.
  4. If we stop or remove an app that subscribers have paid for, they get the refund in A9a.6, and C9 applies to your share of it.

C18. Ending Part C

  1. You may end Part C at any time by delisting all your apps and telling us at support@owlsinsight.com.
  2. We may end it with 30 days' notice, or at once for a serious breach, fraud, a legal reason or a sanctions match.
  3. After it ends, C17 applies to people subscribed to your apps, and we pay shares for sales already made after their hold, less refunds and chargebacks. C2.3, C7 to C12, C14 and C16.1 survive.

C19. Law

A20 applies to Part C.

C20. Changes to Part C

  1. We may change Part C with at least 30 days' notice by email. If you do not agree, you may stop selling before the change takes effect (C17.1).
  2. A change never applies to sales already made.
  3. A change never reduces the founding terms we confirmed to a founding builder in writing.
  4. A change to the hosting price follows C15.2.

Part D. Subscription terms (paid apps)

D1. Agreement

Part D applies when you subscribe to an app that has a price. Parts A and B, including A9a, also apply.

D2. Who is who

  1. The app's builder made it and owns it.
  2. Owls Insight LLC sells you the subscription and is the seller of record: we take your payment, collect tax, decide refunds and answer your questions.
  3. The builder never receives your personal data. They see how many people subscribe and the money, never who.

D3. What you get

While your subscription is paid and you follow these Terms, the app's messages show in Your alerts on owlets.app and are delivered to any destinations you choose, for your own use and the uses A9a.9 allows. This right is personal, non-exclusive and non-transferable. You get no copy of the app, its code or its builder's key, and there is nothing to download.

D4. What a price buys

  1. The app's messages, for each month you pay for, in Your alerts on owlets.app and at any destinations you choose.
  2. The updates its builder makes during your subscription, each reviewed by us before it reaches you. An update can change what the app sends and how often.
  3. The same price for as long as your subscription lasts (A4.10).
  4. It does not buy any result. Apps can be wrong, miss alerts, be limited (A9a.5) or stop (A9a.6, A7, A14).

D5. No plan needed

The app reads data under its builder's plan, not yours. Your Owls Insight account needs no plan, and your keys are never used. If the builder's plan lapses, A9a.6 applies.

D6. Cancelling

You can cancel at any time, in "Your subscriptions" or through Manage billing. The app keeps posting to the end of the period you paid for, then stops. There is no refund for the rest of the period, except under D7 (A4.13). Cancelled in a free trial, it posts to the end of the trial and you pay nothing (A4.10).

D7. Refunds

  1. If the app is not running, or gets no data, for more than 72 hours in a row, or we remove it, for a reason that is not your fault, your subscription ends and we refund the unused part of the period you paid for, pro rata, counted from when it stopped (A9a.6).
  2. We also refund duplicate charges, billing errors we confirm, and where the law requires.
  3. Contact us at support@owlsinsight.com about any charge within 14 days, and before you file a chargeback (A4.7).

D8. Changes to the app, and removal

  1. The builder may update the app. We review every update before it reaches you.
  2. If the builder stops the app, A9a.6 applies; if they stop selling it while it runs, it posts to the end of your period and is not renewed.
  3. We may pause or remove an app at any time (A12). If we remove it, D7.1 applies.

D9. No picks, no bets, no prizes

Apps on the hub are tools: they watch data and post alerts, digests or numbers. They never place bets, never tell you what to bet, and never offer prizes, contests, leaderboards with prizes or entry fees. An app's listing and messages make no earnings, profit, ROI or win-rate claims. If you see one that does, tell us at support@owlsinsight.com.

D10. What you may not do

Try to obtain an app's code or its builder's key; resell or share your subscription; or use its messages beyond A9a.9.