# Storm OS > Startup Omni Relationship Management: every customer, every investor, and every partner in one relationship graph, live on your phone in fifteen minutes, at $24 a month with 5 users included. Storm OS is a mobile-first, offline-capable relationship system for founders. Most teams end up running a sales CRM, a separate investor tracker, and a folder of partner emails; Storm OS keeps one record per person and company and layers the customer, investor, and partner roles on top, each with its own pipeline, engagement level, and scores. One plan, every feature, 5 users included, a 30-day trial to start. Canonical URL: https://storm-os.app/ Last updated: 2026-10-20 This file carries the full text of every public Storm OS page, extracted from the pages themselves at build time, so an answer engine can quote what the site actually says. Decorative product figures are omitted; nothing else is. --- ## Storm OS · The Relationship Operating System for Startups URL: https://storm-os.app/ Summary: Storm OS gives founders one set of records for every customer, investor, and partner, plus projects, proposals, invoices, and email. $24 a month. Startup Omni Relationship Management # The Relationship Graph Operating System for Startups Customers, investors and partners live on one set of records, and so does everything that follows them: the NDA, the proposal, the signature, the invoice, the project, and the room you share the files in. The tools that make a young company look established, at a price a young company can actually pay. Priced for bootstrapped founders starting at $19/mo with 5 users included. Built for founders who would rather be selling or raising than filing. The problem ## Your relationships are scattered across tools that never talk Your customer pipeline lives in a CRM or a spreadsheet, your raise lives in another tracker, and your partners live in email threads and memory. The spreadsheet got you here, but every relationship that falls between those tools is one you pay for. And the tools that make a young company look established, the proposal builders, the e-signatures, the client portals and the payment pages, have always been priced for companies much further along. ### Sales CRMs price you out Per-seat plans, feature gates, and startup discounts that expire into a renewal cliff. Tools built for enterprises start charging you the moment you grow. ### Investor tools sit in their own silo Your raise tracker knows nothing about the customer intro that same investor made last month, so warm paths go cold and you retype context you already had. ### Partner tools are built for later Dedicated partner platforms are priced for companies far past your stage, so your early partnerships end up in a doc somewhere, waiting to be forgotten. One graph, many roles ## One record can be a customer, an investor, and a partner at once In the real life of a startup it often is, so Storm OS keeps a single record for every person and company you work with, then layers customer, investor, and partner roles on top, each with its own engagement level, fit score, and activity score. - Customer Sales pipeline, deal amounts, weighted forecast, billing structures. - Investor Your raise, the way it actually runs: warm intros through wired funds. - Partner Partnerships move on agreement checklists, since a partner deal rarely has a dollar figure to forecast. The whole lifecycle ## Meet them, win the deal, deliver the work, and keep them well served Most tools take one slice of a relationship and hand you off for the rest, so the story of one customer ends up spread across five logins. Storm OS follows the whole arc on a single record, and every step opens already knowing what happened in the one before it. - Step 01 Meet someone Add the person once, and their record starts collecting the notes, files and history that everything later draws on. One record - Step 02 Work the deal The deal lives on their record, with line items, billing frequencies and a payment schedule that describe the contract you actually intend to sign. A real schedule - Step 03 Send the proposal The proposal is built on the deal, priced from the same lines, and signed by your client with a signature or a one-time code. Signed, sealed - Step 04 Invoice it Each invoice is raised from a milestone your client already agreed to, and the money lands in your own accounts. Paid on time - Step 05 Deliver the project Close the deal and start the project right there, carrying the customer, the stakeholders and the documents with it. Work underway - Step 06 Keep them well served Storm Service arrives in November and puts support cases on the same record as every step above. November Six steps, one record, and nothing retyped between them. Pipelines that fit in a pocket ## All three pipelines, ready the day you sign up Sales, investor, and partner pipelines arrive with sensible stages and weightings already in place, and every stage, probability, and staleness threshold is yours to change without writing code. Stages stack down the screen instead of sideways, so the whole pipeline fits on your phone. - Drag a card to move a deal, with stage requirements enforced on the way in. - Stale deals raise their hand: every card carries a health meter and a reason in plain words. - Add as many pipelines as you need, per product line, region, or experiment. The money on a deal ## A deal holds the whole billing structure, from line items to payment schedule Nearly every CRM gives a deal one amount field and leaves the real shape of the contract in a spreadsheet. Storm OS puts the shape on the deal: line items with a quantity and a unit price, a billing frequency on each line, a discount measured against your list price, and a payment schedule of dated milestones. - One time, monthly, quarterly, annually, on the line rather than the deal A real contract is usually a setup fee and a subscription sitting next to each other, so each line carries its own frequency instead of the whole deal having to pick one. - A schedule of milestones, split any way you actually sell A deposit on signature, a payment on acceptance, the balance on completion. Take one of the ready splits or build the schedule by hand, then edit any milestone’s date, amount and wording. The parts always add back to the exact total, down to the last cent. - Nobody ever types a total One-time, recurring, and total contract value are worked out from the line items every time you look, down to the exact cent. The same lines then fill the proposal your client signs and the invoices you send, so the number they are quoted, the number they sign, and the number they pay are always the same number. Proposals and invoices ## Write the proposal, get it signed, send the invoice, take the money Almost no CRM will let you write the document. You export a quote, rebuild it somewhere pretty, upload it to a signing service, then raise the invoice in a fourth place and reconcile all four by hand. Storm OS does the whole run on the deal itself. - A real document, in your branding A block builder on the deal: cover, headings, text, images, two columns, terms, the pricing table and the payment schedule. Your logo, your colors, your fonts, locked in when it goes out, so a rebrand next year cannot rewrite what somebody already signed. - PDF, Word and the web page, all from one original That way the three can never disagree with each other, and the tracked link tells you who opened it, when, and what they downloaded, which an emailed PDF cannot. - Signed with a code, sealed, and countersigned Your client signs with a one-time code emailed to them, and the moment they do, a sealed copy of exactly what was signed is kept: blocks, prices, terms. You countersign from your side and the deal moves. Already have a contract you like? The Proposal Agent reads it and hands it back as a proposal draft. Storm Finance Beta ## Invoices raised from the schedule they already agreed to An invoice starts from a milestone on the deal, so the line, the amount and the words your client already read come with it. - It goes out with its own payment page, at a link that carries nothing but that invoice. - The payment page takes cards through your own Stripe account, connected once, so the money moves straight from your client to you. - It also carries any other way you get paid, Zelle, Venmo, PayPal, your bank details, or a payment link you already use, dropped in once and offered on every invoice after that. - A card payment marks the invoice paid on its own, and a payment made any other way is marked by hand with the method recorded. - Every invoice and every payment sits on the deal and the customer record, so a year later the whole story is in one place. Storm Project ## Project management, on the deal it came from Storm Project is a real project manager: boards, tasks with owners and due dates, dependencies, and a calendar. What makes it different is where it lives. A project hangs off the deal, the company or the person it came from, so the rollout you promised sits on the record of the customer you promised it to, instead of in a separate tool that has never heard of them. - Start one from a deal, a company, or a person Close an opportunity and Storm OS offers to start the project right there, carrying the customer and the stakeholders with it. Anyone who can see a record can start a project from it, because the person delivering the work is often not the person who sold it. - A board, a list, and a calendar over the same tasks The board opens first, with columns you name and color and cards you drag. Every task has its own owner, status, start and due dates, priority, description, and the task it is waiting on. List and calendar are one tap away on the same project. - Health you can read across the whole portfolio Progress is counted from the tasks themselves, so it cannot flatter anybody. Every project carries a health meter you can read at a glance, and it never relies on color alone, and Tasks pulls your project tasks in beside your relationship tasks so there is one list of what needs you today. The project brief ## It reads the documents you give it, and keeps a brief that stays current Hand a project the statement of work, the kickoff transcript and the change request. It folds them into one standing brief: what is settled, what nobody has answered yet, who owes what and by when, and the client's own words for things. - Each new document is read against the brief instead of the whole pile, so the fortieth transcript costs what the first one did, and reads better because the brief knows more by then. - Because the brief knows what was agreed, it can flag what was not: a task nobody wrote down, a scope change buried in a call, a risk worth saying out loud. - All of it arrives as a proposal you accept or ignore. Nothing is written into the project until you say so. - Project tasks reach the same notifications, digest, and phone as everything else. - The Context Agent reads a project the way it reads a deal, then says where it stands. - Delivery people can be given the project without being given your pipeline. Storm Marketing Beta ## Email from your own domain, reported on the records it reached Design the email by dragging blocks onto the email itself, send it from your own domain to a segment that keeps itself current, and every delivery, open and click lands on the people and deals it touched. - The canvas is drawn by the same code that sends the message, so what you design is what arrives. - It goes out from an address on your own domain, with your footer and nothing of ours in it. - Delivered, opened and clicked, person by person, on the campaign and on every record. - First touch and last touch on every closed deal, so you can see which campaign opened the door. - Landing pages with the campaign's form built in, on your own domain when you connect one, and tickets and check-in for the events you host. - See Storm Marketing The agents ## Five agents, each with a job of its own These five read what you actually have, they tell you where they got it, and none of them can change a record on their own. They are on from the start, and an admin can switch them off at any time. ### Context Agent Summaries Opens a record and says where the relationship actually stands, in four sentences. It goes past the fields you can already see to what they add up to, what moved last, and what is still waiting on somebody. ### Research Agent Web research Fills the blanks on a contact or a company from business data providers and the web, and shows where every value came from. No field changes until you tick it. ### On-Task Agent Daily assistant Watches what is due and what has gone quiet, and sends one short email in the morning. On the days nothing needs you, it sends nothing at all. ### Project Context Agent Project context Reads the statements of work, transcripts and contracts you put on a project and keeps one standing brief. Ask it, and it finds the work they imply and offers it as tasks you accept or ignore. ### Proposal Agent Contract imports Reads a contract you already sell with and hands it back as a proposal draft you can edit, with the pricing taken from the deal instead of retyped. A PDF or text contract uses about 11 AI credits, and most Word files convert without using any. It gets better because you tell it to ## Every answer carries a thumbs up and a thumbs down Thumbs down and write one line about what it should have said, and the next answer takes it into account. That happens inside your workspace and stays there. Sharing anything at all with us is a separate switch that starts off, and even then it is which screen, which direction, and the line you wrote, with no record and no name attached. - It is on from the start, an admin can turn it off at any time, and nothing is sent anywhere while it is off. - Bring your own Anthropic key and the agents you move onto it run on your account. Background reading of documents already filed, and the lookups with data providers, stay on ours. - We never train a model on your records, and Anthropic’s terms forbid it from training on what we send. Context building ## It reads what you have already written, including inside your files An agent is only ever as good as what went into it, so the real work is the context. Attach a contract and Storm OS reads the words inside it. Type a note after a call and it counts. Link a person to a company and the connection is part of the picture. None of that needs tagging, indexing, or a second tool. - PDFs and Word files are read on upload. Search reaches the words inside the contract, so you can find a clause as easily as a filename. - Notes are searchable and readable. The thing somebody typed after the call is the most valuable text on a relationship record, and in most tools it is the least reachable. - The connections are context too. Who this person works for, which deals they are on, and what has happened around them. - Nobody sees what they should not. A search only ever returns what you already had permission to open. Context also moves between the modules: the deal's line items price the proposal, the proposal's schedule raises the invoice, and a won deal starts the project with the account, the stakeholders and the documents already on it, so no part of Storm OS ever opens on a blank page about a customer the rest of it knows well. It compounds on the record too, since one with a single note and no files gets a short answer that says so, and the same record six months later, with the contract, the meeting history and four people attached, gets an answer worth reading before you walk in. Private Rooms Beta ## Send one page that holds everything they need A Private Room is a page with your name and your logo on it, holding the documents one person or one company should see. They sign in with their own email and a password they choose, and you find out what they actually opened. There is no shared drive to manage, no seat in your workspace to pay for, and no link that keeps working after the deal is dead. - Deal Rooms for investors The model, the cohorts, the cap table and the incorporation documents in one place, with an expiry date. When you see that a partner read the financials twice and never opened the roadmap, you know what the next call is about. - Onboarding Rooms for customers A personalized room per account, holding the plan, the contract and the technical documents their team keeps asking you to resend. Everyone linked to the company gets in, and loses access the day they leave it. - Share Rooms for partners Co-marketing assets, brand files and the joint pipeline documents, in a room you can close without chasing anyone down. Nobody needs a seat in your workspace to read a PDF. - Grant one person or a whole company, and everyone connected to them follows along. - Every visit, every folder and every download is recorded against a name. - Close a room in one click and keep the record of what was shared with whom. Connected ## Four integrations are live today, and more are on the way You can connect them this afternoon, and the roadmap below says when the next pieces arrive. Mailchimp Send a campaign to a Storm segment and keep the audience in step, both ways. Sign in with Google One tap in, for you and everyone you invite. Claude The agents run on Claude, from Anthropic. Bring your own Anthropic key and the usage is yours. Stripe Card payments on your invoices, charged on the Stripe account you already have. Email goes out from Marketing Beta on its own, from your own domain. Connect Mailchimp and the same campaigns send through your Mailchimp account instead, with the audience kept in step both ways. Coming next - November Storm Service for its first group of beta customers, and API access in private beta - December The MCP server and the Workflow and Automation Studio, both in private beta - Early 2027 A Storm OS Zap, so Zapier can reach your relationship graph More email platforms, Slack, Notion, Google Drive and Dropbox are on the way, and the whole list is on the integrations page . Built for the founder's pocket ## Install it from the browser, with no app store, no download, and no IT ticket Open Storm OS on your phone or your laptop, choose install, and the icon lands on your home screen next to everything else. It opens full screen like any other app, because it is one. - It keeps working when the signal drops. Your working set lives on the device, so records open in a parking garage and at 30,000 feet. - Edits you make offline are kept safe on the device and sent the moment you are back, with a small counter showing how many are waiting. - If somebody changed the same record while you were away, you are shown the conflict instead of one version quietly winning. - It updates itself the next time you open it, so there is never a store review sitting between a fix and you. - Phone and desktop are the same app, designed for the phone first, so the phone version never feels cut down. 3 pipelines customers, investors, partners 1 record per relationship, however many roles it holds 30 days free trial, no credit card from $19/mo 5 users included, paid yearly Plain pricing ## One plan, priced for the size you are now For that you get the paperwork of a company ten times your size: proposals your clients sign, invoices they can pay on the spot, and a branded room your investors log into. $19 a month paid yearly, or $24 a month if you would rather pay monthly, with 5 users included and additional users from $4 a month. The full math is on the pricing page. --- ## Platform · Storm OS URL: https://storm-os.app/platform/ Summary: How Storm OS works: one relationship graph for every person and company, plus pipelines, proposals, projects, and reporting. Invoices and email are in beta. The platform # One relationship graph, with the work layered on top Storm OS maps what your company actually has, a web of people and companies, and lets each relationship play every role it really plays for you. On top of that sits the work: the pipeline, the billing structure on a deal, the proposal your client signs, the invoice they pay, and the project you deliver. Five agents read all of it, none of them can change a record on its own, and everything on this page is in the product today. What's inside ## Storm OS is the platform, and these are the products that run on it. Storm Eye is what the price buys, and the three beside it are separate offerings, free for early access members for at least a year. Storm Finance and Storm Marketing still carry a beta label. Storm Eye Every relationship you have Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them. See Storm Eye Storm Project The work after the win Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current. See Storm Project Storm Finance Beta Get paid for it Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid. See Storm Finance Storm Marketing Beta Reach them again Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on. See Storm Marketing Storm Service After the invoice clears The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers. What it will do The relationship graph ## One record per person, one per company Every person and company is one record carrying up to three roles, customer, investor, and partner, each with its own type, engagement level, and scores. Add a role with one tap and the record shows up in that pipeline, without a copy ever being made. - Seven engagement levels, from Not Yet Engaged to Re-Engaging, the same across all three pipelines. - Fit and activity scores built from scoring rules you control, with a panel that shows exactly why a score landed where it did. - Duplicate detection when you add or import records, with a side-by-side merge that keeps every link intact and can be undone for seven days. Pipelines ## Three pipelines on day one, each built for a different game Selling, raising, and partnering do not work the same way, so their pipelines should not pretend to. All three arrive with researched stages and thresholds, and every one of them is yours to change without writing code. ### Sales Deals carry amounts and stage probabilities, so the pipeline states a weighted forecast you can actually plan against. Line items, ramped pricing, and billing schedules live on the deal, ready for the contract. ### Investor The raise, modeled on how a raise actually moves: warm intros, first meetings, diligence, committed, wired. Check sizes roll up against your target so you always know how much is real and how much is conversation. ### Partner Partnerships carry no amounts, by design, because treating a reseller conversation like a deal ruins both. Progress is an agreement checklist moving toward live, and anything sitting too long gets flagged. Staleness thresholds flag anything sitting too long in a stage and feed the Needs Attention list on your home screen, and you can add as many pipelines as you need, per product line, region, or experiment. The money on a deal ## A billing structure that matches how the contract is actually written Most CRMs give a deal one amount box and hope you round in their favor. A deal in Storm OS carries line items instead, and every line says how much, how often, and when the money arrives. Twenty-five seats billed monthly, an implementation fee split across signature, acceptance and completion, and a migration quoted under list, all on the same deal, all adding up on their own. ### Every charge on its own line Quantity and unit amount on every line, a billing frequency of one time, monthly, quarterly or annually, and a discount measured against the catalog list price so a line says out loud what it gave away. Sell them ten more seats and you change one number in one place. ### A payment schedule you shape Pick a shape, everything up front, fifty fifty, fifty twenty-five twenty-five, or thirds, and the milestones are laid down with dates and amounts. Then edit any of them, because sometimes the deposit is really due on the first Monday of the quarter, and only a real date can say that. - Frequency lives on each line, because a real contract usually has a one-time fee and a subscription sitting next to each other. - A milestone carries its own words, and those words are what the client reads later on the invoice. - Split a total three ways and the parts still add back to the exact amount, down to the last cent. - Set a discount ceiling per catalog item, and a price below it is flagged before the proposal goes out, while there is still time to fix it. - Investor and partner deals carry no amounts at all, by design, so none of this is forced onto a pipeline that does not want it. - You never type a total, because the one-time amount, each recurring frequency, total contract value, and cost and margin if you are allowed to see them are all calculated from the lines every time you look. From there it leaves the deal screen, the proposal’s pricing table and payment schedule are built from these same lines, and every invoice is raised from a milestone in the same schedule. The number your client is quoted, the number they sign, and the number they are billed are one number, calculated once. Proposals ## Write it, send it, get it signed, all on the deal it came from Almost no CRM will let you write the document. You export a quote, rebuild it in a design tool, upload it to a signing service, and then hold three versions of the same price in your head and hope they match. Storm OS builds the proposal on the deal, so there is only ever one price and it belongs to the deal. ### What your client opens A document with your logo, your colors and your fonts on it, so the first thing your client sees is your brand. The pricing table and the schedule are the deal’s own line items, so a price you changed at four o’clock is right in the document at five. ### What you see back Every event the link recorded, against a name and a time. When you can see that finance opened it twice and nobody reached the terms, you know what the next call is about. - A block builder on the deal: cover, headings, text, images, two-column layouts, terms, the pricing table, the payment schedule, and one signature block. - Your branding is locked onto the proposal when it goes out, so a rebrand next year cannot quietly rewrite a document somebody already signed. - PDF, Word and the web page are all generated from the same document, so the three can never disagree, and the Word file is there for the client whose lawyer redlines in Word. - E-signature with a one-time code emailed to the signer, a typed name, versioned consent wording, and the time recorded. - The moment it is signed, a sealed copy of exactly what was signed is stored: blocks, prices and terms, so "that is not the version I agreed to" has an answer. - You countersign from your side and the deal moves. - Investor and partner proposals refuse the pricing blocks outright, because those pipelines carry no amounts. - Already have a contract you like? The Proposal Agent reads it and hands back a proposal draft you edit, with the live pricing block added straight from the deal, so no number is ever retyped by hand or by the AI. Storm Finance Beta ## The invoice comes from the schedule they already agreed to You do not raise an invoice in Storm OS by typing an amount into a blank form. You raise it from a milestone on the deal, and the line, the amount and the wording your client already read are all sitting there. Then it goes out with its own payment page. - Card payments run through your workspace’s own Stripe account. The money moves from your client to you, and it never touches ours. - Not everybody pays by card, so bank transfer details, Zelle, Venmo, PayPal and a plain payment link are all fully supported, and you choose which ones the page shows. - A card payment marks the invoice paid on its own. Anything paid another way you mark yourself, and the method is recorded against it. - Tax is a rate over the taxable items, rounded once over the base rather than once per line, which is the drift that leaves a total a cent out. - Every invoice, every payment, and every proposal event sits on the same deal and the same customer record, so a year later the whole story is in one place. Storm Project ## Project management, on the record the work came from Boards with columns you name and color, tasks with owners, start and due dates, priorities, statuses and dependencies, and a calendar across all of it. The feature list is what you would expect, the difference is where a project lives: it hangs off the opportunity, the company, or the person it came from, so the rollout you promised sits on the record of the customer you promised it to, and nobody has to keep two tools agreeing about the same account. ### The board Where a project opens. Columns you name and color, cards you drag between them, and the things that decide your day on the face of the card: who owns it, when it is due, how urgent it is, and what it is waiting on. ### The task Every task is a record of its own, with a status, an owner, a start and a due date, a priority, a description, and the task it is waiting for. Dependencies are advisory on purpose, so you get a heads-up while staying free to work in whatever order the day demands. ### The calendar The same tasks laid out by date, Monday first, with anything late in red. Drag one to a new day on a laptop or tap it on a phone, and the board and the list already agree. ### Every project at once The wall of what you owe and to whom. Each project is either attached to a record or marked internal, and progress is counted from the tasks rather than typed in, so nothing here can flatter anybody. The project brief ## A project that reads its own documents and keeps the brief current Give a project the statement of work, the kickoff transcript and the change request, and it folds each one into a standing brief: what is settled, what nobody has answered, who owes what and by when, who the stakeholders are, and the client's own words for things. - Each new document is read against the brief rather than against the whole pile, so the fortieth transcript costs what the first one did and reads better, because the brief has more in it by then. - The brief knows what was agreed, so it can tell you when something new is not in it: a task nobody has written down, a scope change buried in a call, a risk worth naming out loud. - Every one of those arrives as a proposal you accept or ignore. Nothing is written into the project until you say so. - The brief stays a readable length on purpose, dropping what stopped mattering instead of growing forever. - Close an opportunity and Storm OS offers to start the project there, carrying the customer and the stakeholders across. - Anyone who can see a record can start a project from it, because the person who delivers the work is often not the person who sold it, and delivery does not need edit rights on your pipeline. - Board, list and calendar are chosen per project, so each project can work the way the person running it prefers. - A project can belong to a customer, an investor or a partner record, or to nobody at all when the work is your own. - Project tasks join your relationship tasks in Tasks, the morning digest, and the notifications you already get, instead of forming a second inbox. - The Context Agent reads a project like it reads a deal: what is done, what is late, who is waiting, and on which record. The command center ## Home answers one question: what needs my attention right now? A founder with ninety seconds between meetings needs the whole picture fast. Home is a configurable widget grid, all pipelines at a glance, today's tasks, stale deals, and upcoming closes, and it loads instantly even when you are offline. - Widgets keyed to how you work: all-pipeline overview, needs attention, my tasks, recent records, KPI tiles. - Tasks with natural due dates, reminders, and one-tap completion from anywhere. - A unified timeline on every record: notes, calls, meetings, stage moves, and changes, in one stream. Reports and dashboards ## Answers without a data hire Every pipeline gets its own dashboard automatically, with a stage funnel, movements, forecast, and stale deals, and a report builder lets you ask questions across all your records, saved and shared with your team. - What's new, what's moved, and what's closed, the questions you ask every week, are answered without any setup. - Group by any field including the custom ones you add, with tables, bars, lines, funnels, and single-number tiles. - Every table exports to CSV whenever you want it. Private Rooms Beta ## A page with your name on it, for the people outside your company Investors, customers and partners need documents from you, and none of them should need a seat in your workspace to read one. A Private Room is a branded page holding exactly what one person or one company should see. They sign in with their own email and a password they choose, the room expires on a date you set, and you find out what they actually opened. - Deal Rooms for investors: the model, the cohorts and the cap table in one place, with an expiry date. - Onboarding Rooms for customers: a personalized room per account, holding the plan, the contract and the technical documents. - Share Rooms for partners: co-marketing assets and joint pipeline documents, in a room you can close in one click. - Grant a person or a whole company, and everyone linked to that company inherits access and loses it when they leave. - Every visit, folder and download is recorded against a name, so you know what they read before you call them. The agents ## Five agents, five jobs, and a hard limit on all of them None of these changes a field on its own. The Context Agent returns text and saves nothing to a field. The Research Agent hands back proposals a person accepts one at a time. The On-Task Agent reads your tasks and writes an email. The Project Context Agent offers tasks you accept or ignore, and the Proposal Agent hands back a draft you edit before anything is sent. We drew that line because an agent that reads the open web and writes to a relationship record will eventually write something false about a real person, and someone on your team should always agree before a field changes. ### Context Agent Where this relationship stands Four sentences at the top of any contact, company or deal: what it adds up to, what moved most recently, and what is unresolved or waiting on somebody. It reads the fields, the notes, the text inside attached documents, the linked records and the activity history, and it does arithmetic on dates so it can say a close is eleven days out with the last contact thirteen days stale. - It returns text, and it never writes to a field. - It tells you when a record is too thin to be worth summarizing, instead of padding out an answer. - It remembers what it already read, so opening a record twice only costs you once. ### Research Agent Fill the blanks, with receipts Fills in what a contact or company record is missing: website, industry, size, location, title, the things you would otherwise look up by hand. It asks business data providers first, then the open web, and it can find a contact from a name and a company. Every value arrives with its source, and when it is not certain it says so. - It proposes each field, and a person ticks it before it is written. - Every value names the provider or the page it came from. - Researching a company a teammate already researched costs you nothing. ### On-Task Agent What needs you today Keeps the running answer to what is overdue, what is due, and which deals have gone quiet, on the home screen when you look and in one short email in the morning if you want it. The email is skipped entirely on days when nothing needs you, because a daily message that is usually empty is a daily message people stop opening. - It runs off the same tasks and thresholds you can see and edit. - One email, at an hour you choose, or none at all. - It stays quiet on quiet days, on purpose. ### Project Context Agent The brief behind every project Reads the statements of work, call transcripts, notes and contracts you put on a project and keeps one standing brief: what is settled, what nobody has answered yet, who owes what and by when. Each new document is read against the brief rather than the whole pile, and when you ask, it finds the work the documents imply and offers it as tasks. - Every task it finds is a proposal, and nothing reaches the board until somebody accepts it. - The brief stays a readable length, dropping what stopped mattering. - Reading a document uses a few AI credits, and documents filed before the assistant could read them are read in the background at no cost to them. ### Proposal Agent Your contract, as a proposal Upload the Word or PDF agreement you already send and it rebuilds it as proposal blocks: cover, scope, pricing, terms and signature, and where a block quotes a PDF, it notes the page. The pricing table is the deal’s own, so no number is retyped by hand or by the model. - It hands back a draft, and you review every line before anything is sent. - Word and PDF agreements both import. - A PDF or text contract uses about 11 AI credits, and most Word files convert without using any. Context building ## The agents are only as good as what they read, so we made that the product Anybody can put a language model in front of a contact list, so the difference is what the model has to work with. Storm OS turns everything you were already doing into context: the note you typed after the call, the contract somebody attached, who works where, and what has actually happened, all of it reachable by search and readable by the agents without a single tag. - PDFs, Word files and text documents are read the moment they are uploaded, so search finds a clause inside a contract rather than a filename. - Notes are just as searchable, which matters, because the sentence somebody typed after a call is the most valuable text on a relationship record and usually the hardest to find. - Who this person works for, which deals they sit on, and who else is involved all count as context. - Search results respect permissions exactly. You are shown a match only if you could already open the thing it is in. - Scanned pages are named as scanned rather than reported as broken, because "there are no words in this" and "we could not read this" send you to two different places. Your model, or ours ## Yours to switch off, and yours to point somewhere else The assistant is on from the first day, an admin can switch it off during setup or at any time after, and nothing is sent anywhere while it is off. We never train a model on your records, and Anthropic’s terms forbid it from training on what we send. Connect your own Anthropic key and each agent you move onto it runs on your account instead of ours and stops using your workspace’s AI credits. Two things stay on our accounts either way: the background reading of documents already filed on your records, which uses no credits, and research’s lookups with the data providers, which do. - One switch under Settings turns every agent off for the whole workspace, and research has a switch of its own. - Every plan includes AI credits each month for the whole workspace. A summary uses about 1 and researching a contact about 360. - Bring your own key and the agents you move onto it stop using credits. OpenAI, Gemini and Grok are next. - Thumbs up and thumbs down on every answer, with corrections that shape the next one inside your workspace and stay there. - Sharing anything at all with us is a separate switch that starts off, and never includes a record, a name, or the text an agent produced. Install it ## Install it on your phone from the browser, with no app store Storm OS is a progressive web app. Open it in a browser on your phone or your laptop, choose install, and the icon lands on your home screen next to everything else. It then opens full screen like any other app, works when the signal drops, and updates itself. There is no app store, no download, no review queue, and nothing to ask an IT department for. - It opens full screen like any other app on iPhone, Android, Mac and Windows, and it is the same product everywhere, we built the phone version first and widened everything else from it. - It keeps working when the signal drops. Your recent records live on the device, so they open in a parking garage and on a plane as reliably as they do on office wifi. - Edits made offline are kept on the device and go up when you are back, with a small counter showing how many are waiting, and nothing is ever silently dropped. - If two people changed the same record while you were away, you are shown the conflict rather than having one version quietly win. - It updates itself the next time you open it, with no store review sitting between a fix and the person who needs it. Security ## Small team, serious security Your workspace is walled off inside the database itself, a layer deeper than our app code, so another customer's data can never reach yours. You can sign out any device, every administrative action is written to a log nobody can edit, and a full export of your workspace is one click away. Row-level security · rotating sessions · audit trail · full export One platform, growing by modules ## Relationships first, then the work around them Storm OS grows as one system on one bill, and each new module lands on the records you already keep, so a project, a campaign, an invoice or a support case attaches to what is already there. Beta means a module is live in your workspace and still improving. Storm Eye Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them. In the price Storm Project Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current. Included, no extra cost Storm Finance Beta Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid. Included, no extra cost Storm Marketing Beta Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on. Included, no extra cost Storm Service The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers. November Core is what you pay for. Everything marked included is a separate offering, and early access members get it at no additional cost for at least a full year. What is coming, and when - November Storm Service for its first group of beta customers, and API access in private beta - December The MCP server and the Workflow and Automation Studio, both in private beta - Early 2027 A Storm OS Zap, so Zapier can reach your relationship graph Mailchimp, Stripe, Sign in with Google and Claude are connected today, and the rest of the list is on the integrations page . ## Ready in fifteen minutes on your phone, we timed it. Sign up, let Storm OS read your website and propose your brand, and your pipelines are ready in minutes. You start with relationship management best practices built in, plusfive agents that each do one job well. $24 a month, 5 users included. No credit card to start · 30-day trial · Live and customized in 15 minutes --- ## Storm Eye · Storm OS URL: https://storm-os.app/platform/storm-eye/ Summary: Storm Eye is the core of Storm OS: one record per person and company, with customer, investor, and partner roles, pipelines, proposals, and private rooms. Storm Eye # Every relationship your company has, in one place Customers, investors and partners are all people and companies you have a history with, so Storm Eye keeps one record for each of them, lets that record hold more than one role at once, and connects the deal, the proposal and the private room to the relationship they belong to. The core of Storm OS, included on every plan. No credit card to start · 30-day trial · Live and customized in 15 minutes One record, many roles ## A contact can be a customer, an investor and a partner at once In a real startup they often are, so each role carries its own engagement level and its own history on the same record, and the intro an investor made last month stays visible from the deal it turned into. - Roles are added to the record you already have, so nobody maintains a second copy of the same person - Sub-types for each role: angel, seed fund, strategic, channel-sourced, whatever fits how you work - The Context Agent writes the overview at the top from everything on the record, and leaves your fields alone - Custom fields, layouts and saved views, all configured with clicks, and every list reopens on the view you used last Pipelines ## Three pipelines on day one, each built for a different game Sales, fundraising and partnerships move through different stages, and forcing them onto one board is how the real version ends up in a spreadsheet. Each pipeline here has its own stages, its own colors and its own math, and you can add as many more as you like. - Board or funnel view, weighted forecasting, and totals that update as cards move - Stage colors you choose, so the board reads at a glance - Stakeholders on every deal, so you always know who has to say yes - Unlimited custom pipelines beyond the three that come ready Inside a deal ## A deal carries its numbers, its people and its paperwork Open any card and you get the full picture: the amount, the weighted value, the close date, where it sits in the pipeline, and who is involved. The billing structure lives here too, so retainers, milestones and one-time charges are described once and reused everywhere the money matters. - Weighted forecasting from the stage probability, adjustable per deal - Retainers, milestone payments and one-time charges on the same deal - A next step and a date, so nothing drifts quietly - Win a deal and start the delivery project from it in one step, with the account and stakeholders carried across Proposals ## The proposal builds itself from the deal it belongs to Write the proposal right on the deal, and the pricing table fills from the line items you already entered. Send it as a tracked link, watch it get read, and collect the signature on the same page your client opened. - Drag-and-drop blocks: cover, scope, pricing, terms, signatures - The investment table and payment schedule come straight from the deal - A tracked link shows you when it was opened and what was read - E-signature on the page, plus PDF and Word downloads when somebody asks Lightning Vault ## Your client signs with their actual signature, in three steps Lightning Vault is how a proposal becomes an agreement. Your client draws their signature with a finger, types it in a real handwriting style, or uploads a picture of the one they already use, and a one-time code sent to their own inbox ties that signature to them. It takes about a minute and there is nothing for them to install or sign up for. And then it is done ### The agreement comes back carrying both signatures Your client sees the signed document on the same page they opened, and can download it as a PDF or a Word file. You get the same copy, with your countersignature beside theirs once you add it. - Draw, type or upload, on a phone as easily as a laptop - A one-time emailed code proves the signer is the person you sent it to - The signature lands on the document itself, where the terms it agrees to are - Storm keeps a sealed copy of exactly what was signed, down to the character - You countersign from your side and both signatures appear side by side Paperwork ## Agreements that name people rather than price a deal A mutual NDA before the first real conversation, an MSA, a statement of work. Paperwork starts from your own template or from a Word contract you already have, names both sides properly, and files itself on the person, the company and the deal it belongs to. - Start from a template, or bring a contract you already use and keep its wording - Both sides named from your records and your registered legal identity - The dates an agreement states about itself: issued, expected back, expires - One press sends it and emails the link, with your name on the message - They sign, you countersign, and the executed copy goes back to both of you - Withdraw one you have sent, with the trail of what happened left intact The companies behind them ## Organizations that know who works there and what is open A company record holds its own people, deals, documents and roles, so when you open an account you see everything your company and theirs have going together. - People linked to a company with their title, and one marked primary - Every deal, proposal, invoice and project on the account, in one place - Duplicate checks at import and at creation, and any merge can be undone for seven days - A full export of everything, whenever you want one, in a format you can open The account ## Open a company and see what it is to you A company can pay you, have invested in you and be closing a partnership all at once, and its record says so in one row of chips. Scores, the people you know there and the company facts sit above the deals and documents, so the first screen of an account is the one you would otherwise piece together from three places. - Customer, investor and partner roles on one company, each with its own sub-type and engagement level - Fit and activity scores at the top of the record, for the company as well as its people - Industry, headcount and revenue beside the website, LinkedIn and phone - The Context Agent reads the whole account and says where it stands Imports ## Bring the spreadsheet you already have Import people and their companies together from one CSV or Excel file, or deals, offerings and tasks on their own. Every field a record shows can be filled from a column, the company's address and phone included, and nothing is written until every value Storm OS would refuse has been decided. - One column can fill the person and their company at once, so an address in the file lands on both - Each picklist column lists the values your workspace allows, right under it while you map - Capitals, spaces and underscores are matched to the values you already have, and a value nobody set up is never created - Anything it would refuse is listed before the import starts, with a suggestion where one fits: pick a value, leave it empty or skip those rows - A large file goes in a stretch at a time, pauses if you close the page and resumes from Import history - Undo the import for a week after it runs Reporting ## Answers without hiring somebody to build them Build a report on any object, group it the way you think about it, and pin it to a dashboard the whole team sees the same way. There is no separate BI tool to buy and no export that goes stale by Thursday. - Reports on contacts, companies, deals, tasks, projects, campaigns and invoices - Dashboards you arrange yourself, shared or private - A starter library of ready-made reports you can clone and tweak - Filters saved as views, reusable anywhere a list appears Dashboards ## The quarter on one screen, for the whole team Pin the reports you keep opening to a dashboard, set the period once, and everyone who signs in sees the same numbers. The sales one here carries what is open, what it is realistically worth, what closed and what came in new. - Any report pins to a dashboard as a tile, in the layout you choose - One period picker at the top, so every tile reads the same quarter - Shared with the team or kept to yourself - A pinned report opens in full from its tile Home ## One screen that answers what needs attention right now Home gathers what is overdue, what moved, who is waiting on you, and the deals about to go quiet, arranged the way you want and consistent for everybody who signs in. - Arrange it yourself, and set what the team sees by default - Needs attention gathers stale deals, missing next steps and overdue tasks, and Upcoming closes shows what is expected to land in the next two weeks - Every tile opens the record behind it - Reads and writes offline, then syncs when you are back Private Rooms ## Share one branded page instead of a folder full of links A room is a private page for the people outside your workspace: a diligence room for an investor, a handover for a client, a partner brief. Visitors get a password of their own, and you get a record of who opened what. - Your logo and your colors, so the room looks like it came from you - Folders and files, with the text inside them searchable to your team - Per-visitor access you can revoke the moment a conversation cools - Statistics per room: who arrived, what they read, how long they stayed The rest of Storm OS ## Your customers, your work, and your money in one place Every part below works from the same relationships, so the deal you win becomes the project you deliver, the invoice you send, and the customer you keep, without re-entering any of it. Storm Project The work after the win Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current. See Storm Project Storm Finance Beta Get paid for it Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid. See Storm Finance Storm Marketing Beta Reach them again Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on. See Storm Marketing Storm Service After the invoice clears The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers. What it will do Included in the price of Storm OS. The whole platform --- ## Storm Project · Storm OS URL: https://storm-os.app/platform/storm-project/ Summary: Storm Project turns a won deal into delivery: boards, calendars, tasks with dependencies, status updates, and a brief that reads your contracts and transcripts. Storm Project # The work that follows the win, on the record it came from A closed deal becomes a project that already knows the account, the people and what was promised. You get boards, lists and calendars for the work, and a brief that reads your own contracts and transcripts so it stays current without anybody maintaining it. A separate offering, included with your plan for a year. No credit card to start · 30-day trial · Live and customized in 15 minutes Projects ## Client work and internal work, side by side and clearly labeled Client work hangs off the account it belongs to, so the project, the deal and the invoice all read as one relationship. Internal work gets its own label, and the wall of projects shows progress and health for all of it at a glance. - Kick off straight from a won deal, carrying the account and the stakeholders - Progress counted from the tasks themselves, so the number stays believable - A health dot per project, so a list of twelve is still readable - Every client project reachable from the company record it serves Boards, briefs and status ## The board, the brief and the latest word are one project Columns you name and color, tasks with dependencies and due dates, and a status update right in the project header, so anyone who opens it knows where it stands before they read a card. A Context tab keeps a brief written from what the project has actually read, and it keeps up as you add contracts and call transcripts. - Update status is one tap in the header: on track or not, and a line on why - The latest update shows on the project, with the last five a tap away - Add a contract, a transcript or a note and the project context compounds - Board, list or calendar per project, whichever fits the work The calendar ## When the date matters more than the stage, switch the view The same tasks appear on a month view, so deadlines and deliverables sit where you expect them, and anything late is flagged where you cannot miss it. - One click between list, board and calendar, per project - Late work flagged in red, right on the day it was due - Due dates set in plain language when you add the task - The month view reads well on a phone, like the rest of the app Tasks ## One list of what is actually yours Every task in one place, whatever it hangs off: a person, a company, a deal or a project board. Overdue, today, this week and later, on your own day rather than a server somewhere. The On-Task Agent keeps the same answer current and can mail it to you each morning. - Project tasks and follow-ups arrive in the same list, on the same day view - Mine, the team, or everything, from the same three views - Overdue and today separated, because they call for different mornings - Check off anything from the list; a project task still opens on its board The rest of Storm OS ## Your customers, your work, and your money in one place Every part below works from the same relationships, so the deal you win becomes the project you deliver, the invoice you send, and the customer you keep, without re-entering any of it. Storm Eye Every relationship you have Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them. See Storm Eye Storm Finance Beta Get paid for it Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid. See Storm Finance Storm Marketing Beta Reach them again Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on. See Storm Marketing Storm Service After the invoice clears The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers. What it will do A separate offering, included at no additional cost for early access members for at least a year. The whole platform --- ## Storm Finance · Storm OS URL: https://storm-os.app/platform/storm-finance/ Summary: Storm Finance, in beta, raises the invoice from the deal that promised it, sends it in your name, and takes card payment through your own Stripe account. Storm Finance Beta # The invoice comes from the deal that promised it You already described the money when you built the deal and the proposal, so Storm Finance raises the invoice from that same schedule, sends it in your name with replies coming straight back to you, and collects payment through whatever your customers already use. A separate offering, in beta, included with your plan for a year. No credit card to start · 30-day trial · Live and customized in 15 minutes Invoices ## Every invoice you have raised, and what happened to each one Draft it, send it, and record how it was paid. Generate the whole payment schedule from a signed proposal in one step, or raise a single invoice from scratch when you just need to bill somebody. - A full schedule generated from a won deal, or one invoice on its own - Draft, sent, paid and void, with the filters across the top - Attached to an account, a contact, or both - Your numbering, your terms and your logo, set once in templates An invoice ## Line items, taxes, terms and a memo, with the math done for you The invoice itself is a real document you shape: quantities, unit prices, tax handling and payment terms, with the totals worked out as you type. When it is right, send it: it arrives in your name, and when your customer replies, the reply comes straight to you. - Line items with quantities, unit prices and per-line tax - Issue and due dates, terms, and a memo your customer sees - Sent in your name, with your customer's replies coming straight to you - Mark it paid by hand when a wire arrives, with the method recorded Getting paid ## Take payment any way your customers already pay Every sent invoice carries a payment page, and you decide what appears on it. Connect your own Stripe account and the page carries a Pay Now button that opens Stripe's checkout, with the money going straight to you. Alongside cards, or instead of them, drop in the payment links you already use. - Card payments on Stripe's own checkout, charged on your Stripe account, so payouts and fees are between you and Stripe - Drop-in options for Zelle, Venmo, PayPal, bank transfer details, or any payment URL you already have - You choose the order they appear in, and switching one off hides it without losing what you wrote - No processor required to start: an invoice with only manual payment options still works The rest of Storm OS ## Your customers, your work, and your money in one place Every part below works from the same relationships, so the deal you win becomes the project you deliver, the invoice you send, and the customer you keep, without re-entering any of it. Storm Eye Every relationship you have Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them. See Storm Eye Storm Project The work after the win Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current. See Storm Project Storm Marketing Beta Reach them again Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on. See Storm Marketing Storm Service After the invoice clears The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers. What it will do A separate offering, included at no additional cost for early access members for at least a year. The whole platform --- ## Storm Marketing · Storm OS URL: https://storm-os.app/platform/storm-marketing/ Summary: Storm Marketing, in beta, sends email you design from your own domain to segments of your records, with landing pages, events, and forms on the same records. Storm Marketing Beta # Email your relationships from your own domain, and see what it turned into Design the email on a canvas that is the email, send it from your own domain to a segment that keeps itself current, and watch every delivery, open and click land on the same records your deals live on. A separate offering, in beta, included with your plan for a year. No credit card to start · 30-day trial · Live and customized in 15 minutes Campaigns ## A campaign is any push at a group of people A launch email, a conference, a sponsorship, the ads you are about to run. Storm OS keeps who was involved and what came of it, so the dinner you hosted in September stays connected to the deal it produced in November. - Types that match real work: email, events, sponsorships, paid, social - Planning, active and completed, with who responded counted on every row - Member statuses you configure, so responded means what you decide it means - Attach a campaign to a project when the push is a piece of work The email ## Drag blocks onto the email itself The canvas you design on is drawn by the same code that sends the message, so what you see is what lands in the inbox. Drag a heading, a picture, a button or a two-column row into any gap, set your colors and fonts once, and start from a template when you would rather not start from a blank page. - Ten blocks in a palette you drag from, or tap on a phone - Templates shown as pictures of the email they make - A full-size preview in a phone frame, and a test send marked as a test - Designed or plain text, with your address and an unsubscribe link on every send Sending ## From your own domain, in your own name Campaign email goes out from an address on your own domain. Type your domain once in Domain Management and Storm OS sets up three addresses on it, one for email, one for link tracking and one for landing pages, with one list of DNS records to add, each with a copy button, and one Check for all three. None of them touch the email your team already sends. The message carries your name, your words and your footer, and nothing of ours. - Subdomains by default, engage for email, io for tracking and go for pages, so your existing mail setup stays exactly as it is - Tracked links on your own domain too, so a click never passes through a stranger's address - A careful start for a new domain: each send reaches at most 1,000 people for the first two weeks - Only people who may be emailed are sent to, and you can record permission for a list you already have - Already on Mailchimp? Connect it and your campaigns send through your Mailchimp account instead Results ## Who it reached, and what it turned into Every send reports what was delivered, opened and clicked, person by person, on the campaign and on each record. Pick the figures you care about, and follow the campaign into the deals it touched. - Six key figures by default, or your own set from fifteen, including deals won and the money in them - Opens and clicks on the person's record, where the next conversation starts - First touch and last touch on every closed deal, won or lost, worked out for you - A bounce or a failed delivery says why, in words Segments ## Describe who you mean once, and the list keeps up A segment is a saved question about people, built from anything on your records: their role, their tags, the deals they are on. It counts again whenever you ask, so next month's campaign goes to whoever fits by then. - A live count, and who can be emailed, before you send anything - One segment feeding as many campaigns as you like, named on its card - Segments from forms and event walk-ups, made for you as people sign up - Its own page in Marketing, beside Campaigns, Events and Forms Landing pages ## A page for the campaign, with the form built in Give a campaign a page of its own: an event, an offer, a waitlist. It is built by dragging sections and blocks into place, reads well on a phone, and carries the campaign's form right on the page, so every answer lands on the campaign and the records it belongs to. - Published at your workspace's address, or on your own domain such as go.yourcompany.com once you connect it in Domain Management, with a link you can put anywhere - The form sits on the page, so nobody leaves to fill it in - Each submission lands on the campaign with the page it came from and the site or link that sent the visitor - No cookies and no third-party scripts, and a visitor is known only by the form they fill in The page builder ## One to three steps, built by dragging sections into place Start from a one, two or three step template, drop in sections of one, two or three columns, and set your colors and fonts once for the whole page. The canvas is the page, drawn by the same code that serves it. - Templates for a page, a page and a form, or a page, a form and a thank-you - The form created right there, or one you already have, matched to the page's design - Desktop, tablet and phone views, and a preview link with a code to scan on your phone, before anything is published - The campaign, the form and the address named across the top, so nothing is left unconnected Assets ## Every picture and file in one library Upload a picture or a file once and use it in any email or page. Each one knows where it is used, so you can see what a change will touch before you make it. - Search by name, with alt text stored alongside each picture - Where it is used, on every card: live pages, sent emails and drafts - Replace a file and your drafts and live pages pick up the new one - Video from YouTube or Vimeo, loaded only when a visitor presses play Events ## The dinner, from the invite to the door An event is a campaign with a date, a registration page and a way to check people in. Everyone who registers gets a ticket with a code, and on the night your phone becomes the door. - A registration page built here, or one you already have, bound to the event - A ticket for every registrant, with a code they can read out if their phone dies - Check in by scanning, by typing the code, or by looking someone up by name - Several people checking in at once, with every phone agreeing within seconds - Walk-ups captured properly, so the person who just turned up is a real record The night itself ## Who registered, who has a ticket, who walked in Open the event and the whole roster is there: name, company, how to reach them, and whether they have arrived. The counts at the top are the ones you keep refreshing on the day. - Registrants with their company and contact details, on one screen - Tickets sent, and who has been through the door, counted live - Check in from a phone at the door while somebody else works the list - Anyone who turns up without registering becomes a real record Forms ## A public page whose answers land as records Ask for what you need, on your own pages, with your own colors. Every answer becomes a person record, tagged, segmented, and joined to the campaign it came from. - Fields from your own records, including the custom fields you added - Multi-step pages, and questions that only appear when they are relevant - A thank-you message or your own redirect, and an automatic reply if you want one - Views, submissions and conversion on every form, with an export when you need it The rest of Storm OS ## Your customers, your work, and your money in one place Every part below works from the same relationships, so the deal you win becomes the project you deliver, the invoice you send, and the customer you keep, without re-entering any of it. Storm Eye Every relationship you have Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them. See Storm Eye Storm Project The work after the win Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current. See Storm Project Storm Finance Beta Get paid for it Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid. See Storm Finance Storm Service After the invoice clears The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers. What it will do A separate offering, included at no additional cost for early access members for at least a year. The whole platform --- ## Storm Service · Storm OS URL: https://storm-os.app/platform/storm-service/ Summary: Storm Service will bring support onto the same records as the deal, the project, and the invoice: a customer portal, ticketing, and routing, from November. Storm Service # The support side of the relationship, on the same records After the deal is signed, the project delivered and the invoice paid, the relationship keeps going. Storm Service handles what happens next, on the same record as everything that came before it, and gives your customers a real place to bring their questions. Licensed separately from Storm OS. The first beta group starts in November. Where it fits ## Support that already knows your customer Storm Service runs on the same records as your deals, projects and invoices, so a ticket arrives with its whole history attached and whoever answers is already caught up. Add it when support becomes a real part of your day; it is licensed on its own, so you only pay for it when you need it. - A ticket lands with the deal, the project and the invoice behind it - Whoever answers sees what was sold, built and billed, without asking around - The same people and companies you already keep, with no second system to maintain - Want it early? The first beta group starts in November The portal ## A public face for your support, on an address you choose Every Storm Service account gets a persistent customer-facing portal, and you choose part of its URL. Your customers open tickets, follow their status, and read your service library there, with embeddable forms for the places they already are. Custom domains and subdomains follow later. - A hosted portal your customers can actually visit - You pick part of the address; custom domains and subdomains come later - Embeddable ticket forms for your site and product - A service library your answers build over time Phase 1 · November ## Ticketing that knows who it is talking to The first release covers the working core: tickets through the portal and embedded forms, routed to the right person, answered faster with pre-written replies, and measured on dashboards, with the relationship context on every ticket. - Portal-based ticketing - Embeddable ticket creation forms - Ticket routing - Analytics and dashboards - Pre-written replies - On-time context from the record behind the ticket Phase 2 · December ## The knowledge base starts answering first December brings the self-serve layer: a knowledge base that learns from your answers, live conversation when a customer wants a person, and assistance that steps in before a ticket exists. - Intelligent knowledge base - Messaging and live chat - AI-powered proactive assist Phase 3 · January ## Automation, and an agent of its own January opens the new year with the automation layer: tickets born from email, workflows that route and respond on rules you set, and custom AI service agents that can chat, suggest replies, and answer on their own where you allow it. - Email-based ticket creation - Automations and workflows - Custom AI service agents: chat, suggested replies, and auto-response where you choose Have a say ## Tell us what your support flow needs This page will fill with real screens as the product comes together. If you want a say in what it does first, or a place in the beta group, the contact form goes to a person who reads it. - It will carry a beta label while it is one - Beta customers shape the roadmap ahead of each phase The rest of Storm OS ## Your customers, your work, and your money in one place Every part below works from the same relationships, so the deal you win becomes the project you deliver, the invoice you send, and the customer you keep, without re-entering any of it. Storm Eye Every relationship you have Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them. See Storm Eye Storm Project The work after the win Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current. See Storm Project Storm Finance Beta Get paid for it Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid. See Storm Finance Storm Marketing Beta Reach them again Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on. See Storm Marketing Not built yet. November. The whole platform --- ## Storm Context · Storm OS URL: https://storm-os.app/platform/storm-context/ Summary: Storm Context is the AI layer of Storm OS: five agents and the Bolt Graph, turning the notes, documents, and deals you already keep into working memory. Storm Context # A platform that learns your business as you use it Five agents read what you and your team already write, and the Bolt Graph they feed turns it into working memory: who this relationship is, what was promised, what was signed, and what needs doing today. Included with every plan, switchable, and private by construction. Part of Storm OS on every plan. You choose what runs. No credit card to start · 30-day trial · Live and customized in 15 minutes Five agents ## Each one has a job, and a name you will use They work from what is already on your records: notes, documents, the deal timeline, the signed agreement. Nothing runs on data you did not put there. Context Agent Summaries Reads everything on a record and keeps a current summary at the top of it, so nobody walks into a call cold. Research Agent Web research Fills in companies and contacts from business data providers and the open web, and every suggestion waits for your approval. On-Task Agent Daily assistant Keeps the running answer to what is overdue and what is due today, and mails it to you in the morning. Project Context Agent Project context Reads the contracts, transcripts and notes on a project into one standing brief, and finds the work they imply. Proposal Agent Contract imports Rebuilds an agreement you already send as proposal blocks, with the pricing taken from the deal. The Context Agent ## Walk into every conversation already caught up The summary at the top of a record is written from everything underneath it: the notes, the emails you logged, the documents, the deal history. It updates as the record grows and it cites where each point came from. - A current summary on people, companies, deals, and projects - Sources shown for every claim, so you can check it in one click - Your fields are never edited; the agent writes in its own panel - Thumbs up or down teaches it what you care about The On-Task Agent ## Your day, triaged before you open the laptop Overdue, due today, and coming up, gathered from every deal and project you own, and the morning email reaches your inbox at the hour you choose, on the days something needs you. - Tasks gathers your whole day across deals, projects, and follow-ups - Type a task with its date in words, like "Email Sarah in 2w", and the due date is set for you - The digest arrives by email, and push and in-app notifications are yours to switch - A proposal being read, a stage change, an overdue slip: you hear about it Context that reads the paperwork ## Upload the contract, and the project knows what was signed Drop the countersigned agreement on a project and the Project Context Agent reads it into the project's working memory. It drafts the tasks the document implies, corrects dates that moved between draft and signature, and flags work that appears nowhere in the signed scope. - Suggested tasks carry the clause they came from - Changes between draft and signed copy are called out - Scope creep gets flagged before it gets expensive - Nothing is added to the project until a person accepts it Bring what you already use ## An existing agreement becomes editable contract blocks Upload the MSA you already send and the Proposal Agent rebuilds it as Storm blocks: cover, scope, pricing with the figures intact, terms, signature. From there it is a living document you can send, track, sign, and countersign. - Word and PDF agreements both import - Each block notes the page it came from - Pricing arrives as a real table, ready to bind to a deal - You review every line before anything is sent The Research Agent ## Records that fill themselves in, with your approval Add a company and the Research Agent proposes the basics from business data providers and the web. Add a contact and it does the same, linked to the right company, even from just a name. No field changes until you accept it. - Company firmographics: industry, size, location, site - Contacts enriched in the context of the account they belong to - Every value names the provider or the page it came from - Partial matches are reported instead of guessed at - Enrichment runs on the capacity included with your plan, and an admin can see the meter The Bolt Graph ## Context that compounds across the whole relationship Every relationship in Storm builds its own graph of context points, called Bolts. A Bolt can be one line or a whole document: a preference somebody mentioned, a pricing decision, the countersigned MSA. The graph grows as an introduction becomes an opportunity, the opportunity becomes an agreement, the agreement becomes delivered projects, and the projects become an active customer, so the context is already there at every next step. Sandboxed to the relationship Each graph serves its own relationship. What Vantage Freight told you stays in the Vantage Freight graph, and an agent working another account cannot read it. Lessons your team keeps When a project wraps, the retrospective proposes lessons. The ones you keep join your workspace playbook and brief the next project, while what a client told you stays anchored to that client. Your own work has a graph too Internal projects and your Storm OS workspace build the same kind of memory for your team, tied to your organization rather than to any customer. Private by construction ## Your context belongs to your company Context is customer data and it is treated like customer data: isolated to your workspace at the database layer, invisible to other tenants, and out of reach of casual inspection by anybody, including us. - Every workspace is isolated at the database layer, enforced by the database itself rather than by application code remembering to check - The people who operate Storm OS have no everyday path into your account data, and that includes your context. Support access happens one way: you hand it over, and you end it - Your own LLM key is sealed when you save it: encrypted, write-only, and never shown again, even to you - We never train a model on your workspace, and Anthropic’s terms forbid it from training on what we send - Coming soon: export your context alongside the rest of your data, for migrations or on demand You hold the dials ## On, off, capped, or on your own key AI in Storm is a set of switches, and they are yours. Turn the agents off and the platform is still the platform. - An admin switch turns AI on or off for the workspace - The included capacity covers enrichment and document work, sized for most Pre-Seed to Seed teams - Plug in your own Claude API key and the agents you move onto it run on your account, with the native caps removed. Background reading of filed documents and the lookups with data providers stay on ours. Other model providers are coming - Coming soon: add capacity in a couple of clicks when you want more of it ## Start free, and let the context build itself From $19 a month with 5 users included. The agents are part of the plan. --- ## Integrations · Storm OS URL: https://storm-os.app/integrations/ Summary: Mailchimp, Stripe, Claude, and Sign in with Google connect to Storm OS today. More email and file tools follow, API access in November, an MCP server in December. Integrations # Your relationship graph talks to the rest of your stack Storm OS works best when it can talk to the tools you already use, like the list you send from, the account your customers pay into, the room where your team talks, and the drive your files live on. Everything on this page is labeled live or coming soon, so you always know what you are getting today. 4 live today · 9 on the way · 3 platform features with dates Live now ## These work today, in the workspace you sign into Open your workspace, connect your account, and these are ready to use right away, with no waitlist and no private beta. ### One audience, whichever screen you opened it from Send a campaign to a Storm segment and keep the audience in step, both ways. - Build the segment in Storm OS from the contacts you already keep, and it lands in Mailchimp as an audience. - It stays in step in both directions, so you are never reconciling two lists by hand and never guessing which one is right. - Storm OS sends campaign email itself, from your own domain. Connect Mailchimp and your campaigns send through your Mailchimp account instead, on its sending reputation, and disconnecting hands sending back. ### Sign in without inventing another password One tap in, for you and everyone you invite. - It works for the first person in and for the fifteenth, so adding a teammate is as simple as sending an invitation. - Storm OS asks Google only who you are: your Google account ID, your name and your verified email address. It never reads your mail, your calendar or your files. - Email and password still work too, and the button on the sign-up and sign-in screens is Google’s own, drawn by Google. ### The intelligence in Storm OS, and the choice of whose account pays for it The agents run on Claude, from Anthropic. Bring your own Anthropic key and the usage is yours. - The five agents run on Anthropic’s Claude models: Haiku for summaries and the daily assistant, Sonnet where a job needs more judgment, and Claude’s own web search for research. Every plan includes a monthly allowance of AI credits that these agents draw on. - The assistant is on from the start, an admin can switch it off during setup or in Settings under Assistant, and nothing is sent while it is off. While it is on, record content and the text of any file you hand an agent go to Anthropic’s API. We never train a model on your records, and Anthropic’s terms forbid it from training on what we send. - Prefer to own the usage? An admin pastes your own Anthropic API key in the same settings and chooses which agents run on it, and those calls bill to your Anthropic account instead of using the workspace’s AI credits. The key is encrypted when you save it, and only its last four characters are ever shown after that. ### Get paid by card, straight into your own Stripe account Card payments on your invoices, charged on the Stripe account you already have. - It comes with Storm Finance, in beta. An admin connects it once, from Admin under Finance, by linking the Stripe account you already run, with no new payout setup and no second onboarding. - Every invoice you send then carries a Pay Now button. Your customer pays on Stripe’s own checkout page with the payment methods you have switched on in Stripe, and the charge is made on your account, so the money lands in your Stripe balance. - The invoice marks itself paid when Stripe confirms the payment. Storm OS adds no fee of its own, so Stripe’s usual processing fees are the only ones, and disconnecting turns Pay Now off while your other ways to pay keep showing. Coming soon ## What we are building next These integrations are planned but not in the product yet, and we list them here so you can see where Storm OS is headed before you move your company onto it. ### Email and lists This is the same two-way segment sync Mailchimp has today, pointed at whichever sender you already pay for. The same segment sync, for the list you already run there. Lightweight sending, connected to the records that know who is who. Campaigns and transactional mail, all working from the same audience. ### Where the work gets talked about It connects your relationship data to the rooms where your team already talks and decides. A Storm OS Zap, so thousands of other tools can reach your records. Early 2027 - A Storm OS Zap puts your relationship graph on the other end of the thousands of connections Zapier already has, so a new signature can start whatever your company does next, wherever that happens. - Triggers for the moments that matter: a deal moves stage, a proposal is signed, an invoice is paid, a project task comes due. Actions for the other direction: create a contact, log a note, raise a task, start a project. - It is the answer for every tool we will never build a native connection to, and it arrives in early 2027. Deal and project news in the server your team already lives in. The deal moved, the proposal was signed, the invoice was paid, and it all lands in the channel. Pull a spec or a brief straight into the project that needs to read it. ### Where your files already live Attach files right where they already live, so you never end up with a second copy that goes stale. Attach what already lives in Drive, without downloading it first. Same for Dropbox, the file stays where it is and the record knows about it. If the one you need is not on this page, write to us and tell us, because the founders who are waiting on an integration decide what we build next. The platform ## Three doors into your own workspace These let you, or any tool you choose, read and write your own data directly, and put the everyday rules in your own hands, so you never have to wait for us to build a specific integration first. ### API access and documentation Read and write everything in your workspace, with docs written in plain language. An API key goes through the same permission checks the app itself uses, so it can never read anything its owner could not already open in the product. It is also what makes the next one possible: an MCP server is a small, well-behaved client of your own API. ### MCP server Point Claude, or any MCP client, straight at your own relationship graph. MCP, the Model Context Protocol, lets an AI tool read a system for itself, which means no more copying a record into a chat window and hoping you grabbed the part that mattered. When ours lands, that connection is live: the client reads your workspace under your account and your permissions, so you can ask about your pipeline in the tool you already have open. Nothing is copied anywhere to make it work, and nobody outside your workspace ends up holding a second copy of your data. MCP is an open protocol, so we are not tied to any one AI vendor, and any tool that supports it can connect to your workspace. ### Workflow and Automation Studio Build the rules your business already runs on: when this happens, do that. Route work, raise documents, send the follow-up, without writing code. Every business runs on rules somebody is holding in their head: when a proposal is signed, raise the invoice and open the project. When a deal goes quiet for two weeks, put it back on my list. The Studio is where you write those down once and let the system keep them. A rule is a plain sentence you build from menus, so you are picking a trigger and picking what happens next rather than learning a scripting language. Rules run under the permissions of the person who owns them, and every run is written to the audit log, so you can always see what fired, when, and what it touched. The wider roadmap - November Storm Service for its first group of beta customers, and API access in private beta - December The MCP server and the Workflow and Automation Studio, both in private beta - Early 2027 A Storm OS Zap, so Zapier can reach your relationship graph ## Your tools should keep themselves in sync Start with your contacts, connect Mailchimp and Stripe, sign in with Google, and let the rest arrive as they go live. Every connection is switched on per workspace, so one you never open costs you nothing. No credit card to start · 30-day trial · Live and customized in 15 minutes --- ## Pricing · Storm OS URL: https://storm-os.app/pricing/ Summary: Storm OS pricing, in public: $24 a month, or $19 a month paid yearly, five users included, every feature on the one plan, and a 30 day trial to start. The numbers, from the site configuration that renders them: - Monthly: $24 a month, 5 users included. - Yearly: $19 a month paid up front, $228 a year, the same 5 users included. - Additional users: $5 a month on the monthly plan, $4 a month ($48 a year) on the yearly plan. - Free trial: 30 days on every new workspace, no credit card to start. - 12,000 AI credits a month for the workspace, and 2,000 more for each extra user. - One plan, every feature. No tiers, no feature gates, no renewal cliff, no contact-sales wall. - Prices in USD. Checkout runs on Stripe when the trial ends, and the price you sign up at is the price you keep. Pricing # One plan, one price The price below is the whole price, and one plan covers all of Storm Eye. 5 users come standard. Join while Storm OS is in early access and your price holds for at least a year. Storm OS · one plan Paid up front: $228 a year for the 5 included users. Additional users are $4 a month each ($48 a year). Additional users 5 are included, add more any time No credit card to start · 30-day trial · Live and customized in 15 minutes Prices in USD. Checkout runs on Stripe when your trial ends, and the price you sign up at is the price you keep. The multi-year math (5 users) The yearly plan works out to $19 a month, about $4.38 a week for the whole team. It is a price that fits the size your company is now. What the price buys All of Storm Eye comes with the one plan, so every feature on this page is yours from day one, and there is no higher tier to compare against. - Relationships One record can be a customer, an investor and a partner at once, each role with its own history. - Pipelines and deals A board per pipeline, weighted forecasting, and billing structures that survive contact with a real contract. - Proposals Write it, send it as a tracked link, get it signed and countersigned, without leaving the deal. - Paperwork Beta NDAs and agreements from your own templates, signed and countersigned, filed on the record. - Private Rooms Beta A branded page for people outside your workspace, with a record of who opened what and when. - Reporting and dashboards Build a report on anything in your workspace, pin it to a dashboard, and see the same numbers everyone else sees. - The Storm Agents Context, Research, On-Task, Project Context and Proposal read what you have already written, and they never write back without you. On every plan, monthly or yearly - 12,000 AI credits a month for the workspace, and 2,000 more for each extra user - Unlimited custom pipelines on top of the three that come built in - Fit and activity scoring that shows you why each score landed where it did - Tasks, notes, files, and one timeline on every record - Reports, dashboards, and a home screen you arrange yourself - Custom fields, layouts, and saved views, no code required - Guided imports that check every value before anything is written, with a week to undo, and a full export whenever you want one - A full help center, one tap from the screens it explains - Installable mobile app that reads and writes offline - Your workspace kept fully separate from everyone else's, with a complete audit trail And right now you get three more: Storm Project, Storm Finance, and Storm Marketing are their own offerings, and they come with your plan at no additional cost for at least a full year when you join now. Here is exactly what that means . Included for early access members ## Three more products, included for at least a year Storm Project, Storm Finance, and Storm Marketing are separate offerings, and each one would normally be priced on its own. Join Storm OS now, while it is in early access, and all three come with your plan at no additional cost for at least a full year. They are in your workspace from the day you sign up, Storm Finance and Storm Marketing still carry a beta label, and you will hear from us long before any of that changes. - Storm Project Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current. Included, $0 extra - Storm Finance Beta Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid. Included, $0 extra - Storm Marketing Beta Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on. Included, $0 extra Coming next - Storm Service , in November. The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers. No credit card to start · 30-day trial · Live and customized in 15 minutes What happens when the year is up is spelled out in the FAQ below , and the short version is that nothing lands on your bill unless you ask for it. Common questions ## Pricing FAQ ### What happens when my team grows past 5 users? Additional users are $5 a month on the monthly plan, or $4 a month paid yearly, and you add them in the app whenever you need them, without a sales call. The 5 included users cover most founding teams for a long while. ### Does the price jump at renewal? Not in your first year. Join while Storm OS is in early access and the price you sign up at holds for at least a full year, with every module included. After that we may raise it only if our operating costs rise, by no more than 20% per module in any year, and we will tell you at least 30 days before it applies at your next renewal. Longer discounts are available case by case. ### Which features are on which plan? All of them come with the one plan. Monthly and yearly differ only in what you pay, so the choice is purely about the math above. The early access offerings, Storm Project, Storm Finance, and Storm Marketing, come with both terms. ### What are AI credits? They are how the assistant’s work on our accounts is counted. Every workspace gets 12,000 a month, shared by the whole team, plus 2,000 for each extra user you pay for, and they renew on your billing date. A summary uses about 1, a question to the assistant about 2, and researching a contact about 360. Anything you run on your own Anthropic key uses none, apart from research’s lookups with the data providers. ### What happens after the included year? Storm Project, Storm Finance, and Storm Marketing go back to being separately priced offerings. We have not set those prices yet. Here is what we will do: any change to your Storm OS plan price is limited to 20% per module in a year, we will tell you in writing well before your year is up, and nothing is added to your bill unless you say yes to it. If you decide a module is not for you, what you put in it exports with everything else. ### What does beta mean for Storm Finance and Storm Marketing? It means they are real and they are already in your workspace, covered by the same permissions, backups, and export as everything else, so your data there is as safe as anywhere in the product. What beta buys you is that we are still shaping them around what people actually do with them, so screens will move and new pieces will land faster there than in the rest of the product. If something is missing, tell us, because right now that is exactly what decides what gets built next. ### What if I want to leave? Every view exports to CSV, and admin includes a complete workspace export covering every record, note, and file reference. You can run the export yourself in one click, and your data goes with you. ### Is there a free trial? Every new workspace starts a 30-day trial with the 5 included licenses, and you can add more licenses at signup if you need them. You do not need a credit card to start, and checkout runs on Stripe when the trial ends. ## The math checks out, and the rest takes one click. Create your workspace now, bring your own data, and take the full 30 days to decide. Everything on this page, Storm Project, Storm Finance, and Storm Marketing included, is there from the first minute. No credit card to start · 30-day trial · Live and customized in 15 minutes --- ## Contact · Storm OS URL: https://storm-os.app/contact/ Summary: Talk to the team behind Storm OS. Send a sales inquiry, open a support ticket, or email us directly at info@storm-os.app or support@storm-os.app. Contact # Talk to the people building it Whether you are sizing Storm OS up for your team or you are already in and have a question, a real person reads and answers every message. Pick the form that fits, or email us directly. ### Talk to sales Curious whether Storm OS fits how your team works? Tell us a little and we will get back to you fast. This opens your email app with the details filled in, ready to send. ### Open a support ticket Already using Storm OS and have a question? Send us the details and we will dig in. This opens your email app with the details filled in, ready to send. Other ways to reach us ## Prefer to just email? You can skip the forms entirely, just write to the right inbox and we will pick it up during business hours. Sales info@storm-os.app For questions about fit, plans, and getting started. Support support@storm-os.app For help when your team is already running on Storm OS. Live chat is coming soon, and until then a form or an email is the fastest way to reach us. --- ## Terms of Service · Storm OS URL: https://storm-os.app/terms/ Summary: The Storm OS Terms of Service: the agreement you accept when you create a workspace or join one. Your data, your payment, and how either side can end it. Legal # Storm OS Terms of Service The agreement between you and Storm OS. Accepted when you create an account or join a workspace. Effective date: October 20, 2026 Last updated: October 20, 2026 Version: 1.4 ### 1. Agreement to these Terms These Terms of Service (" Terms ") are a binding agreement between On-Call CMO LLC , a Pennsylvania limited liability company doing business as Storm OS (" Storm OS ," " we ," " us "), and the person or organization that creates a Workspace or uses the Service (" you ," " Customer "). The " Service " means the Storm OS marketing site and the Storm OS application, both at storm-os.app (including the application's installable Progressive Web App), our APIs, and any related support and documentation. By creating an account, accepting an invitation to a Workspace, installing the app, or otherwise using the Service, you agree to these Terms. If you do not agree, do not use the Service. If you accept these Terms on behalf of a company or other legal entity, you represent that you have authority to bind that entity, and "you" means that entity. The " Early Access Period " runs from August 1, 2026 through at least March 31, 2027 . We may extend it by telling Workspace Admins by email before it ends, and that email will give the new end date. Storm OS is an early release product during that time: its features change quickly as we build it (§10), and the third party services it runs on are still being selected, configured and tuned. Where these Terms, the Privacy Policy or the Data Processing Addendum promise a period of notice before a change takes effect, that period does not apply during the Early Access Period, unless the section that promises it says it does. We still tell you what changed and when, as soon as we reasonably can, and every right you have to object, to terminate or to export your data is unchanged. From the day after the Early Access Period ends, those notice periods apply in full. ### 2. What Storm OS is (and is not) Storm OS is relationship and pipeline management software for founders and small startup teams. It helps you track customers, investors, and partners in one place: records, pipelines, tasks, notes, and reporting. Storm OS is a software tool. It is not a broker-dealer, investment adviser, placement agent, law firm, accounting firm, or fundraising intermediary, and nothing in the Service is legal, tax, accounting, investment, or fundraising advice. Nothing in the Service constitutes an offer or solicitation to buy or sell securities. You are solely responsible for your fundraising, sales, and partnership activities and for complying with the laws that govern them. ### 3. Definitions ### 4. Accounts, eligibility, and sign-in 4.1 Eligibility. You must be at least 18 years old (or the age of majority where you live, if higher) to create an account. The Service is intended for business use and is not directed to children. 4.2 Account security. You are responsible for safeguarding credentials and for all activity under your account. Enable multi-factor authentication where offered. Notify us promptly at security@storm-os.com if you suspect unauthorized access. 4.3 Sign-in with Google. You may sign in using a Google Account. If you do: - Your use of those identity providers remains governed by their own terms and privacy policies. We are not responsible for their services. - We use only the minimum identity information needed to authenticate you and create your profile: your unique Google identifier, your email address and whether Google has verified it, and your name. Google's sign-in response can also carry your profile picture, which we do not read or keep. We do not request access to your Gmail, calendar, files, or contacts as part of sign-in. - If we later offer features that require additional permissions, we will ask you to authorize those permissions separately, describe what they do at the point of consent, and let you decline without losing access to sign-in. - You may disconnect Storm OS at any time from your Google Account permissions page. Disconnecting removes our ability to authenticate you via Google; it does not by itself delete your Workspace or Customer Data (see §14). - If we add further sign-in providers, we will update these Terms and the Privacy Policy before that option becomes available to you. 4.4 Invitations and membership. Workspace Admins may invite, deactivate, and change the roles of Authorized Users. If you join a Workspace created by someone else, you understand that the Workspace's owner controls that Workspace, including its data, permissions, and continued existence, and may remove your access at any time. ### 5. Your data, your ownership 5.1 Ownership. As between you and Storm OS, you own all Customer Data. We claim no ownership rights in it. 5.2 Limited license to us. You grant us a worldwide, non-exclusive, royalty-free license to host, store, transmit, copy, index, display, back up, and otherwise process Customer Data solely to: (a) provide, secure, and maintain the Service for you; (b) prevent or address technical problems, abuse, or security incidents; and (c) comply with law. This license ends when the Customer Data is deleted, except for backups pending expiry. 5.3 What we will not do. We will not sell, rent, or license Customer Data. We will not use Customer Data to serve advertising. We will not use Customer Data to train machine-learning or generative AI models , whether our own or a third party's. 5.4 Who can access Customer Data. Access is limited to: (a) Authorized Users of the Workspace, as governed by that Workspace's permission and sharing settings; (b) Integrations that you or a Workspace Admin explicitly connect; (c) our subprocessors, which receive data to provide their services to us and are listed, with what each one receives, at storm-os.app/subprocessors ; and (d) a small number of Storm OS personnel under the narrow, audited circumstances described in our Privacy Policy (support you request, and investigation of security or availability incidents). We do not browse Workspaces. 5.5 Your responsibility for the data you upload. Storm OS is a relationship tool, which means you will store information about third parties such as prospects, investors, partners, and their staff. You represent that you have a lawful basis to collect and process that information, that you will honor applicable notice and rights obligations toward those individuals, and that you will not upload information you are not permitted to hold. For personal data subject to the GDPR, UK GDPR, or similar laws, you are the controller and we act as your processor (see §6). 5.6 Sensitive data. Do not upload government identification numbers, payment card numbers, health records, precise biometric data, or information subject to sector-specific regimes such as HIPAA, PCI-DSS, GLBA, FERPA, or ITAR/EAR-controlled technical data. The Service is not designed for those categories and we disclaim liability arising from them. ### 6. Data protection roles For Customer Data, you are the controller (or business) and we are the processor (or service provider). Our DATA PROCESSING ADDENDUM (" DPA ") governs that processing, including subprocessors, security measures, international transfer mechanisms, breach notification, and assistance with data-subject requests. The DPA is incorporated into these Terms by reference and applies automatically where required by law. For Account Data and for our own operational and security telemetry, we act as a controller; see the Privacy Policy . ### 7. Acceptable use You will not, and will not permit anyone to: - Use the Service in violation of any law, including data protection, anti-spam (CAN-SPAM, CASL, PECR, GDPR Art. 6/21), securities, sanctions, or export control laws. - Upload or transmit malware, or attempt to gain unauthorized access to the Service, other Workspaces, or any system or data you are not permitted to access. - Probe, scan, or load-test the Service, or conduct penetration testing, without our prior written permission (request at security@storm-os.com ). - Reverse engineer, decompile, or attempt to derive source code, except to the extent that restriction is unenforceable by law. - Resell, sublicense, or provide the Service as a service bureau to third parties, or build a competing product using our confidential information. - Scrape or use automated means to extract data from the Service other than through our documented API and within published rate limits. - Circumvent usage limits, rate limits, or access controls. - Upload content that is unlawful, infringing, defamatory, harassing, or that you lack the right to store. - Use the Service to send unsolicited bulk communications, or to build or enrich contact lists in ways that violate applicable law. - Misrepresent your identity or affiliation, including in Workspace invitations. We may suspend access without notice if we reasonably believe conduct threatens the security, integrity, or availability of the Service or another customer's data. We will restore access promptly once the risk is resolved. 7.1 Marketing sending. Storm OS sends a Workspace's marketing email from that Workspace's own sending domain once the domain is verified, and a Workspace that connects MailChimp sends through its MailChimp account instead. If you use the Service to send marketing email to your own contacts, you warrant that you have valid consent, under CAN-SPAM, CASL, PECR, GDPR, and other applicable law, for every recipient on every list you use, and you will not use a purchased or scraped list. We may pause a send in progress or block a Workspace from sending if it crosses our deliverability thresholds for bounce or spam-complaint rates, and will restore it once the underlying list is fixed. Campaign email a Workspace sends carries no line naming Storm OS. Email that Storm OS sends from its own address on a Workspace's behalf, such as proposals, invoices, Room invitations and form replies, says that it was sent via Storm OS. ### 8. Progressive Web App and offline use Storm OS is installable as a Progressive Web App and caches a working subset of your Workspace on your device so it works offline. - Cached data is scoped to the signed-in user and Workspace and is cleared when you sign out. - Your operating system or browser may evict cached data without warning. Cached data is not a backup. - Changes made offline are queued locally and applied when connectivity returns. Where two people edited the same record, the app will surface a conflict for you to resolve. You are responsible for reviewing and resolving conflicts. - Device-level security is your responsibility: use a device passcode, and use the in-app lock and remote sign-out features if a device is lost. ### 9. Integrations and third-party services You may connect Integrations to a Workspace. MailChimp, your own Stripe account for invoice payments, and your own AI provider key are Integrations. When you connect one, you authorize us to exchange the data necessary for that Integration to function. Integrations are provided by third parties under their own terms; we do not control them, do not warrant them, and are not liable for their acts or omissions, including their handling of data you direct us to send them. Disconnecting an Integration stops future exchange but does not retrieve data already shared. ### 10. Early release, beta features, and how the Service changes 10.1 An early release product. Storm OS is an early release product, and we are building it quickly. During the Early Access Period defined in §1, any part of the Service may change rapidly and without advance notice: features may be redesigned, renamed, moved, combined, split or rebuilt, and the way a feature works may change from one release to the next. Features we label "beta," "preview," or "early access" change the fastest, and may keep changing this way after the Early Access Period ends. 10.2 No feature degradations. We change features to improve them. We will not make a change that takes away what a feature does for you or leaves it doing less, and this includes beta, preview and early access features. When we replace a feature, its replacement does the same job or more, and what you stored in the old one stays yours and stays exportable under §14.4. The only exceptions are a change the law requires, a change security requires, and a change forced on us when a third-party service a feature depends on changes or withdraws what it provides. In those cases we tell Workspace Admins what changed and why, as soon as we reasonably can. AI allowances, and how AI usage is measured, are governed by §11 rather than this section. 10.3 Beta features. Features labeled "beta," "preview," or "early access" are provided as-is and may be less reliable than the rest of the Service. Apart from §10.2, they are excluded from any service commitments. Do not rely on them alone for business-critical processes. ### 11. Fees, plans, and trials Current plans and prices are published at https://storm-os.app/pricing . In summary: - Storm Eye , the core relationship and pipeline module, is licensed per Workspace in a bundle that includes 5 users , at US$19 per month billed annually or US$24 per month billed monthly . - Additional users beyond the included 5 are US$4 per user per month billed annually or US$5 per user per month billed monthly . - Storm Project , Storm Marketing , and Storm Finance are optional modules licensed in blocks of 5 users at US$9 per block per month billed annually or US$12 per block per month billed monthly . Module blocks are allocated at the Workspace level and must cover every licensed Storm Eye user. A Workspace with 6 Storm Eye users therefore requires 2 blocks of any module it enables. Per-user module allocation is not offered. - Early access accounts. A Workspace created during the Early Access Period defined in §1 is an early access account. For at least 12 months from the date the Workspace is created, an early access account has every module and feature of the Service, including Storm Project, Storm Marketing, and Storm Finance, at its introductory price: the Storm Eye and additional user prices above as they stood on the day the Workspace was created, with no charge for any other module. - Early access prices after the first 12 months. After those 12 months, we may raise an early access account's prices if our costs of operating the Service rise, by no more than 20% per module in any 12-month period. Storm Eye, Storm Project, Storm Marketing, and Storm Finance each count separately, and so does the additional user price. An increase is measured from the price the account pays for that module before the increase; for Storm Project, Storm Marketing, and Storm Finance, which an early access account first pays for after its included period, it is measured from the block prices above. We will give Workspace Admins at least 30 days' notice by email before an increase, and it takes effect at your next renewal. Extended discounts are available to early access accounts case by case, and any we agree to is confirmed in writing. - Modules after the included period. At the end of an early access account's first 12 months, Storm Project, Storm Marketing, and Storm Finance will be disabled unless you choose to license them. We will notify Workspace Admins by email at least 30 days before that period ends, stating what will change and what it will cost. We will not begin charging you for a module you have not affirmatively chosen to license. - The two notices in the two bullets above apply during the Early Access Period as well. - AI credits. Each Workspace's plan includes a monthly allowance of AI credits, shown in the Service, that renews on the Workspace's billing date. AI-assisted features use credits when a member asks for them and they run on our accounts. Features that run on a Workspace's own AI provider key use none, except research's lookups with data providers, which always run on our accounts, and reading documents already filed, in the background, uses none. When a Workspace's credits are used up, those features pause until the allowance renews, and the rest of the Service keeps working. All prices are in US dollars , which is currently the only supported billing currency. AI-assisted features. While the Service is in early access we may introduce, adjust, meter, or withdraw AI allowances, and may change how AI usage is measured. Where a change would reduce an allowance included in a plan you are already paying for, we will give at least 30 days' notice by email to Workspace Admins, and you may terminate and export your data under §14.4 if you object. Some AI-assisted features may be offered as beta features under §10. AI output can be inaccurate, incomplete, or unsuitable for your situation. You are responsible for reviewing it before acting on it, and §2 applies to anything it produces. Our commitment in §5.3 applies in full to these features: we will not use Customer Data to train machine-learning or generative AI models. The AI-assisted features are on unless a Workspace Admin turns them off, during setup or at any time. When they run on our account, the content they work with is sent to Anthropic, PBC, under Anthropic's commercial terms, which do not permit Anthropic to train models on it, and Anthropic's data processing addendum. Anthropic states that it deletes API inputs and outputs within 30 days, except where it keeps them longer to enforce its usage policy (up to 2 years for content it flags) or to comply with the law. Where a Workspace routes a feature to its own AI provider key, that provider's terms with the Workspace apply to what runs on that key (§9). Research, unless a Workspace Admin turns it off, sends what it searches with to the data providers listed at storm-os.app/subprocessors . No field on a record is changed until a member accepts what research found, and a research run on a company also files the further company details the providers return, such as funding, technology and headcount, on that company's record. Where fees apply: fees are stated in the applicable plan or order, are payable in advance, are billed to the payment method on file through our payment processor, are non-refundable except where required by law, and exclude taxes, which you are responsible for. We may change pricing on 30 days' notice effective at your next renewal. Non-payment may result in suspension after notice and a reasonable cure period. If we offer a free tier or trial, we may change or discontinue it at any time on reasonable notice. ### 12. Intellectual property; feedback We and our licensors own the Service and all software, design, documentation, trademarks, and content within it, excluding Customer Data. We grant you a limited, non-exclusive, non-transferable, revocable right to access and use the Service during your subscription, for your internal business purposes, subject to these Terms. If you send us feedback, ideas, or suggestions, you grant us a perpetual, irrevocable, royalty-free license to use them without obligation to you. We will not identify you as the source without your permission. ### 13. Confidentiality Each party may receive the other's non-public information. The receiving party will protect it with at least reasonable care, use it only to perform under these Terms, and disclose it only to personnel and advisors who need it and are bound by confidentiality. This does not apply to information that is public through no fault of the receiver, independently developed, or lawfully received from a third party. Compelled disclosure is permitted with prompt notice where legally allowed. Customer Data is your Confidential Information. ### 14. Term, termination, export, and deletion 14.1 Term. These Terms apply from your first use until terminated. 14.2 Termination by you. You may stop using the Service and delete your Workspace at any time from the Workspace Admin console. 14.3 Termination by us. We may terminate or suspend for material breach that remains uncured 10 days after notice, for non-payment, for conduct posing legal or security risk, or if we discontinue the Service (with at least 60 days' notice, and a pro-rata refund of prepaid unused fees). 14.4 Export window. For 30 days after termination, you may export your Customer Data in full, as a documented CSV/JSON bundle covering all objects, custom fields, and relationships. Data portability is included in every plan. 14.5 Deletion. After the export window, we will delete Customer Data from active systems within 30 days and from backups within our normal backup expiry cycle (currently 35 days), except where retention is required by law. Deletion of individual records inside the Service follows the in-product lifecycle: soft delete, Recycle Bin restore for 30 days, then purge. 14.6 Survival. Sections 5.1, 12, 13, 15, 16, 17, 18, and 20 survive termination. ### 15. Disclaimers Except as expressly stated in these Terms and to the fullest extent permitted by law, the Service is provided "as is" and "as available." We disclaim all implied warranties, including merchantability, fitness for a particular purpose, title, non-infringement, and any warranty arising from course of dealing or usage of trade. We do not warrant that the Service will be uninterrupted, error-free, or that it will meet your requirements, and we do not warrant results obtained from the Service, including scores, forecasts, or reports, which are indicative only. Some jurisdictions do not allow certain disclaimers; those disclaimers apply only to the extent permitted. ### 16. Limitation of liability To the fullest extent permitted by law: - Neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, goodwill, or data, even if advised of the possibility. - Each party's total aggregate liability arising out of or relating to these Terms is limited to the greater of (a) the fees you paid or owed to us in the 12 months before the event giving rise to the claim, or (b) US$100 . - These limits do not apply to: your breach of §7 (Acceptable Use), either party's indemnity obligations, your payment obligations, or liability that cannot be limited by law (including, in some jurisdictions, gross negligence, willful misconduct, death, or personal injury). Nothing in these Terms limits rights that consumers or others have under mandatory local law. ### 17. Indemnification 17.1 By you. You will defend and indemnify us against third-party claims arising from Customer Data, your use of the Service in breach of these Terms or applicable law, or your infringement of a third party's rights. 17.2 By us. We will defend and indemnify you against third-party claims that the Service, as provided by us and used in accordance with these Terms, infringes a US patent, copyright, or trademark, and will pay damages finally awarded or agreed in settlement. Our obligation does not apply to claims arising from Customer Data, combination with items not supplied by us, or use of beta features. We may procure the right to continue, modify the Service, or terminate and refund prepaid unused fees. 17.3 Process. The indemnified party must give prompt notice, allow the indemnifying party to control the defense, and provide reasonable cooperation. ### 18. Governing law and disputes These Terms are governed by the laws of the Commonwealth of Pennsylvania , USA, without regard to conflict-of-law rules. The UN Convention on Contracts for the International Sale of Goods does not apply. Before filing a claim, the parties will attempt in good faith to resolve the dispute by notice to legal@storm-os.com and 30 days of discussion. Any unresolved dispute will be brought exclusively in the state or federal courts located in Allegheny County, Pennsylvania , and both parties consent to that jurisdiction and venue. Either party may seek injunctive relief in any court to protect intellectual property or confidential information. If you are a consumer in the EU, UK, or another jurisdiction with mandatory local protections, nothing here deprives you of the right to bring proceedings in your home courts under local law. ### 19. Export controls and sanctions You represent that you are not located in, ordinarily resident in, or organized under the laws of a country or region subject to comprehensive US sanctions, and that you are not on any US, UK, or EU restricted-party list. You will not use or export the Service in violation of US export control or sanctions laws. ### 20. General 20.1 Changes to these Terms. We may update these Terms. For material changes we will give at least 30 days' notice by email to Workspace Admins and by an in-app notice, and the change takes effect at the end of that period. Continued use after the effective date means acceptance. If you object, you may terminate and export your data under §14.4. During the Early Access Period defined in §1, the 30 day period above does not apply. We will still tell Workspace Admins by email what changed, as soon as we reasonably can, and the change takes effect on the date the notice gives. Your right to object, to terminate and to export your data under §14.4 is unchanged. From the day after the Early Access Period ends, the 30 day period applies in full. 20.2 Changes to the Service. We improve the Service continuously. §10 describes how it changes while it is an early release product, and the commitment in §10.2 applies during the Early Access Period and after it. 20.3 Assignment. You may not assign these Terms without our consent, except to a successor in a merger or sale of substantially all assets with notice to us. We may assign to an affiliate or successor. 20.4 Entire agreement. These Terms, the Privacy Policy, and the DPA are the entire agreement and supersede prior discussions. Terms on a purchase order or vendor portal have no effect. 20.5 Severability and waiver. If a provision is unenforceable, the rest remains in effect. A failure to enforce is not a waiver. 20.6 Force majeure. Neither party is liable for delays caused by events beyond reasonable control, excluding payment obligations. 20.7 Independent contractors. No agency, partnership, joint venture, or employment relationship is created. 20.8 Publicity. We will not use your name or logo publicly without your prior written consent. ### 21. Contact On-Call CMO d/b/a Storm OS 239 4th Ave, Ste 1401, Pittsburgh, PA 15222, USA General: hello@storm-os.com · Legal: legal@storm-os.com · Security: security@storm-os.com · Privacy: privacy@storm-os.com Questions about any of this go to legal@storm-os.com . Privacy requests go to privacy@storm-os.com , and anything security related to security@storm-os.com . Earlier versions of these documents are kept at storm-os.app/privacy/archive . --- ## Privacy Policy · Storm OS URL: https://storm-os.app/privacy/ Summary: The Storm OS Privacy Policy: what we collect, why we hold it, who else processes it, and how to export or delete everything in your workspace. Legal # Storm OS Privacy Policy What we hold, why, and what you can ask us to do about it. The short version is at the top. Effective date: October 20, 2026 Last updated: October 20, 2026 Version: 1.4 ### The short version - Your Workspace data is yours. We hold it only to run the product for you. - We do not sell or share your data , we do not serve ads, and we do not use your data to train AI models. - We ask for the minimum from Google: sign-in identity only. We do not read your mailbox, calendar, files, or contacts. - The assistant and research are on unless a Workspace Admin turns them off , during setup or at any time. While they are on, the content they work with goes to the providers listed in §8. - We do not browse your Workspace. Storm OS personnel access Workspace content only when you ask us to for support, or when we must to fix a security or availability incident. Every such session is logged, time-limited, and visible to your Workspace Admins. - You can export everything and delete everything , at any time. The rest of this policy is the detail behind those statements. ### 1. Who we are and what this covers On-Call CMO , doing business as Storm OS (" Storm OS ," " we ," " us "), 239 4th Ave, Ste 1401, Pittsburgh, PA 15222, USA, operates the Storm OS marketing site and the Storm OS application, both at storm-os.app . The application is an installable Progressive Web App for managing customer, investor, and partner relationships. This policy explains what personal data we handle, why, and what rights you have. It applies to visitors to our site, people who create or join a Workspace, and individuals whose information appears inside a customer's Workspace. Two different roles. This distinction determines who you should contact about your data: If your details appear in someone's Storm OS Workspace and you want them corrected or removed, contact that organization directly. If you contact us instead, we will forward your request to the relevant customer and, where the law requires, assist them in responding. See §12. ### 2. What we collect We do not use advertising cookies or cross-site tracking pixels. Google Analytics sets its cookies only on the pages and screens where it runs, listed above, and we configure it not to use Google signals or ad personalization. Everywhere else, the application sets only strictly necessary cookies: the httpOnly , Secure , SameSite=Lax cookies that sign you in and keep you signed in, a cookie that records only that you are signed in, so our site can take you straight to the application, and the fraud-prevention cookies of our payment processor, Stripe, whose payment form the application loads during onboarding and on the billing screen. Because they are strictly necessary, no consent is required for them. Marketing email a Workspace sends to its own contacts is a different case. When a Workspace turns tracking on for a send, that message carries an open pixel and links rewritten through go.storm-os.app , or through a hostname on that Workspace's own domain, beside its sending domain, once the Workspace has published the record for one, to record opens and clicks for that Workspace's own reporting. The unsubscribe address in the message header always stays on go.storm-os.app , so unsubscribing keeps working even if the Workspace's own hostname stops. Tracking is the Workspace's choice, set per campaign and per sending domain, and it never applies to the application itself. - Identity provider (Google): see §3. - Payment processor : subscription status and payment outcomes. Card numbers never reach our servers. - Data you import : CSV/XLSX files you upload, and information from Integrations you connect. We do not buy or sell contact lists. - Research, unless a Workspace turns it off : while the assistant and web research are on, a member who can edit a record can ask Storm OS to research that person or company, or a saved list of them. The run looks them up with the data providers listed in §8, which we pay for each lookup, and on the public web through Anthropic's web search, and shows what it found as suggestions, each with its source. No field on a record is changed until a member reviews and accepts a suggestion. A research run on a company also files the further company details the data providers return, such as funding, technology, headcount, industry codes, products and competitors, on that company's record. What Storm OS stores from a research run, including the providers' answers, is kept private to the Workspace that ran it, for the periods in §11. A request to erase a person from the research results a Workspace has saved for reuse is carried out for each Workspace separately, and everything else research keeps follows the periods in §11. ### 3. Signing in with Google Storm OS offers "Sign in with Google" so you don't need another password. This section is the full disclosure of what that involves. Google is currently our only third-party sign-in provider. If we add another, we will update this policy before that option becomes available to you. We request identity scopes only : We neither request nor can access your Gmail mailbox, your Google Calendar, your Drive files, or your Google Contacts. No message content, no attachments, no meeting data. We use this information solely to: authenticate you; create or match your Storm OS account; populate your display name; and send you transactional email at the address on file. We store the provider's unique identifier, your email address, and your name as your display name. We do not take your avatar from Google. We do not store tokens beyond what is needed to complete sign-in , and we do not use provider data for advertising, profiling, or model training. Storm OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements. Specifically, we: - Use Google user data only to provide or improve user-facing features that are prominent in the Storm OS interface; - Do not transfer Google user data except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with the user's explicit prior consent; - Do not use Google user data for serving advertisements of any kind, including retargeting, personalized, or interest-based advertising; - Do not sell Google user data; and - Do not allow humans to read Google user data unless we have the user's affirmative agreement for specific messages, it is necessary for security purposes such as investigating abuse, it is required to comply with applicable law, or the data has been aggregated and de-identified. Automatic email capture is on our roadmap. If we build it, mailbox access will be a separate, optional, clearly explained authorization that you can decline while continuing to use sign-in normally. Adding those permissions would require a new consent prompt from Google, so access cannot expand silently. We will update this policy and notify Workspace Admins before any such feature launches. You can disconnect Storm OS at any time: - Google: myaccount.google.com/permissions Revoking stops us from authenticating you through Google. It does not delete your Workspace; to delete data, see §11. ### 4. Why we use your data, and our legal bases ### 5. What we never do - We do not sell personal information, and we do not share it for cross-context behavioral advertising, as those terms are defined by the California Consumer Privacy Act. We have not done so in the preceding 12 months. - We do not serve advertising in Storm OS, and we do not let anyone pay to influence what you see. - We do not use Customer Data to train, fine-tune, or evaluate machine-learning or generative AI models , ours or anyone else's. - We do not disclose Customer Data to third parties except as described in §7. ### 6. Who can access Workspace data This is the part most people actually want answered, so here it is plainly. Access is limited to: - Authorized Users of your Workspace. What each one sees is governed by your Workspace's org-wide defaults, ownership, admin sharing rules, and individual record shares. Every record has an access explainer showing who can see it and why. Workspace Admins have full access to Workspace content by design, and their actions are audited. - Integrations you connect. Only the data required for that integration, only after a Workspace Admin authorizes it, and only for as long as it stays connected. - Our subprocessors (§8). Each receives data to provide its service to us, as §8 describes. Stripe also acts as an independent controller for purposes its own terms list, such as fraud prevention and legal compliance. - Storm OS personnel, narrowly and on the record. We do not browse Workspaces and we have no general-purpose window into your data. Our staff may access Workspace content only in these situations: - You ask us to. Support may start a time-limited session acting as your user to reproduce a problem. Every session requires a stated reason, is capped at 60 minutes, displays a persistent banner in the app, is recorded in our platform audit log, and appears in your own Workspace audit log so your admins can see exactly who accessed what, when, and why. - Security or availability incidents. Where we must investigate abuse, a breach, data corruption, or a serious outage, access is limited to what the investigation requires, is role-restricted, and is audited the same way. - Legal compulsion. See §7. Support sessions cannot change your password or email address, and cannot export your data, unless the operator holds an explicitly elevated support permission. Routine engineering does not use production Workspace data; development and testing run against synthetic seed data. These limits are enforced technically as well as contractually: every row in our database carries a workspace identifier, Postgres row-level security is applied as defense in depth, access is resolved server-side by a single authorization module on every read and write, and audit writes are append-only. ### 7. When we disclose data We disclose personal data only: - To subprocessors who help us run the Service (§8). - To Google, for site analytics : Google Analytics receives what §2.2 describes. - At your direction : to Integrations you connect, or to recipients you share with. - For legal reasons : to comply with a valid legal process, or to protect the rights, safety, or property of Storm OS, our customers, or the public. Where we are legally permitted, we will notify the affected customer before disclosing Customer Data so they can seek protective relief. We will push back on requests that are overbroad or defective. - In a business transfer : if we are involved in a merger, acquisition, financing, or sale of assets, data may transfer to the successor, which will remain bound by this policy or give notice before any material change. Google user data would transfer only with the affected user's explicit prior consent (§3.3). ### 8. Subprocessors We use a small number of vendors to operate the Service. Current subprocessors: The assistant and web research are on unless a Workspace Admin turns them off. Nothing is sent to these subprocessors while the assistant is off, and the three data providers are used only while web research is also on and a member runs research on a record or a saved list. Anthropic publishes its own subprocessors, including any provider behind its web search, at anthropic.com/subprocessors . Google also provides the site analytics described in §2.2. That covers visits to our own site, sign-up and onboarding, never Customer Data, so Google Analytics is not on this list. Integrations a Workspace connects itself. MailChimp, a Workspace's own Stripe account for invoice payments, and a Workspace's own Anthropic key are Integrations the Workspace controls. Each runs on the Workspace's own account with that provider, under the Workspace's own agreement with it, and none of them is our subprocessor. With a Workspace's own Anthropic key, two things still run on our accounts: the background reading of documents already filed on people, companies and deals, and a research run's calls to the data providers above. We maintain the current list at storm-os.app/subprocessors and will give Workspace Admins at least 30 days' notice before adding a new subprocessor that processes Customer Data, with an opportunity to object. During the Early Access Period defined in the Terms of Service (August 1, 2026 through at least March 31, 2027), that 30 day period does not apply, because the third party services we run on are still being selected and configured. We will tell Workspace Admins by email as soon as we reasonably can and update the subprocessors page, and the opportunity to object is unchanged. From the day after the Early Access Period ends, the 30 day period applies in full. ### 9. International transfers Storm OS is operated from the United States. Customer Data is hosted in the United States and Germany. While a Workspace has the assistant or research on, what is sent to the providers in §8 is processed in the locations listed there. Wherever your Workspace is hosted, our personnel, support, and administrative systems are located in the United States, so operating the Service involves processing your data in the US and in other countries whose data protection laws may differ from your own. Where we transfer personal data from the European Economic Area, the United Kingdom, or Switzerland, we rely on: - the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum, or the Swiss equivalent), executed in our Data Processing Addendum, as our primary transfer mechanism; - supplementary technical and organizational measures, including encryption in transit and at rest, tenant isolation, least-privilege access, and a policy of challenging overbroad government requests; and - where a subprocessor holds a valid certification, the EU-US Data Privacy Framework and its UK Extension and Swiss-US Framework, as an additional basis. The Standard Contractual Clauses do not extend to a research data provider that offers no separate data protection terms (§8, DPA §7.4). A copy of the relevant transfer mechanism is available on request at privacy@storm-os.com . Storm OS is not currently self-certified under the EU-US Data Privacy Framework. Standard Contractual Clauses are our own transfer mechanism; the Framework is relevant only where a subprocessor is separately certified. ### 10. Security We design for hard tenant isolation and least privilege. Our current measures include: - In transit: TLS 1.2+ everywhere; HSTS. - At rest: encryption at the storage layer for the database and blob storage. - Credentials: passwords hashed with Argon2id with a strength requirement; passwords are never stored or logged in readable form. - Sessions: short-lived access tokens plus rotating refresh tokens in httpOnly , Secure , SameSite=Lax cookies that are never readable by JavaScript; token-reuse detection invalidates the whole session family; per-device sign-out and "sign out everywhere." - Multi-factor authentication: optional TOTP per user; Workspace Admins can require it for everyone. - Tenant isolation: every row is workspace-scoped, Postgres row-level security applied as defense in depth, cross-tenant access tested in CI as a failing-closed test. - Authorization: a single server-side module resolves access on every read and write, including search, reports, and offline sync, so clients never receive rows they aren't entitled to. - Files: attachments and exports are stored privately and served only through short-lived signed URLs; nothing is publicly addressable. - On your device: offline data is scoped to user and Workspace and wiped on sign-out; an optional app lock re-authenticates after inactivity; revoking a session remotely takes effect on the device's next connection. - Operations: brute-force and rate limiting, append-only audit logging, error and performance monitoring, automated dependency vulnerability scanning, an automated test suite that gates every deployment and includes denied-path authorization tests on every endpoint, and least-privilege access for personnel bound by written confidentiality obligations. We have not yet commissioned an independent third-party penetration test. When we do, we will say so here and make the summary available to customers on request. No system is perfectly secure. If we become aware of a breach affecting your personal data, we will notify affected Workspace Admins without undue delay and in any event within 48 hours of becoming aware , matching our contractual commitment in DPA §9 , and will notify regulators and individuals where required by law. Report suspected vulnerabilities to security@storm-os.com . ### 11. How long we keep data ### 12. Your rights If you are an Authorized User or account holder , you can view and update most of your data directly in the app: profile and preferences, active sessions and devices, notification settings, and Workspace export. For anything else, contact privacy@storm-os.com . Depending on where you live , you may have the right to: access your personal data; correct it; delete it; obtain a portable copy; restrict or object to processing (including profiling); withdraw consent; opt out of the sale or sharing of personal information and of targeted advertising (we do neither); limit the use of sensitive personal information (we do not collect it for the purposes the law targets); and appeal a refused request. We will not discriminate against you for exercising these rights. To exercise a right, email privacy@storm-os.com . We will verify your identity by confirming control of the email address on the account, or by other proportionate means. We respond within 30 days (extendable by a further 60 where the law allows, with notice). You may use an authorized agent where the law provides for one. If your information is in a customer's Workspace , that customer is the controller. Send your request to them. If you send it to us, we will route it to them within 10 business days and support them in responding; we will not unilaterally alter or delete their records. Complaints. You may lodge a complaint with your local supervisory authority: in the EEA, your national data protection authority; in the UK, the Information Commissioner's Office; in California, the California Privacy Protection Agency or the Attorney General. We would appreciate the chance to resolve it first. EU/UK representative. Storm OS markets and sells the Service in the United States. Prices are quoted only in US dollars and the Service is offered only in English, so we do not consider ourselves to be offering goods or services to individuals in the EU or UK within the meaning of GDPR Article 3(2), and we have not appointed an Article 27 representative. If we begin actively marketing to the EU or UK, we will appoint one and update this policy before doing so. ### 13. Children Storm OS is a business tool and is not directed to children. We do not knowingly collect personal data from anyone under 16 . If you believe a child has provided us data, contact privacy@storm-os.com and we will delete it. ### 14. Automated decision-making Storm OS computes two relationship scores: a Fit Score from criteria your Workspace Admin configures, and an Activity Score based on recency and type of interactions. Both are decision support. Each is shown with a full breakdown of how it was calculated, and can be manually overridden by your users. They are not used by us to make automated decisions producing legal or similarly significant effects about any individual. ### 15. Changes to this policy We will update this policy as the product changes. For material changes we will notify Workspace Admins by email and post an in-app notice at least 30 days before the change takes effect, and update the "Last updated" date above. During the Early Access Period defined in the Terms of Service, the 30 day period does not apply, as Terms of Service §1 describes. Where the change requires consent, we will ask for it. We keep prior versions of this policy, the Terms of Service and the Data Processing Addendum at storm-os.app/privacy/archive . ### 16. Contact us On-Call CMO d/b/a Storm OS 239 4th Ave, Ste 1401, Pittsburgh, PA 15222, USA Privacy: privacy@storm-os.com · Security: security@storm-os.com · Storm OS has not appointed a Data Protection Officer, as it is not required to do so under GDPR Article 37. Privacy inquiries are handled at the address above. Questions about any of this go to legal@storm-os.com . Privacy requests go to privacy@storm-os.com , and anything security related to security@storm-os.com . Earlier versions of these documents are kept at storm-os.app/privacy/archive . --- ## Data Processing Addendum · Storm OS URL: https://storm-os.app/dpa/ Summary: The Storm OS Data Processing Addendum: how we handle personal data on your behalf under GDPR, UK GDPR, and CCPA. It applies with no signature required. Legal # Storm OS Data Processing Addendum How we process personal data on your behalf. It forms part of the Terms and applies automatically, with no signature needed. Effective date: October 20, 2026 Last updated: October 20, 2026 Version: 1.4 ### 1. Parties and scope This Data Processing Addendum (" DPA ") forms part of the Storm OS Terms of Service at https://storm-os.app/terms (the " Agreement ") between: Processor / Service Provider: On-Call CMO LLC, a Pennsylvania limited liability company doing business as Storm OS, of 239 4th Ave, Ste 1401, Pittsburgh, PA 15222, USA (" Storm OS ," " we ," " us "); and Controller / Business: the customer that has accepted the Agreement (" Customer ," " you "). This DPA applies where Storm OS processes Personal Data on Customer's behalf in providing the Service, and it applies automatically, with no signature required, from the date Customer accepts the Agreement. Customer may also request a countersigned copy at legal@storm-os.com . This DPA does not apply to Account Data, security telemetry, or diagnostic data for which Storm OS acts as a controller in its own right. That processing is governed by the Privacy Policy . ### 2. Definitions ### 3. Roles of the parties 3.1 Customer is the Controller (and Business) of Customer Personal Data. Storm OS is the Processor (and Service Provider) and processes Customer Personal Data only on Customer's documented instructions. 3.2 Customer determines what Personal Data it puts into the Service, why, and who may access it. Customer is responsible for having a lawful basis for that processing, for providing any required notices to Data Subjects, and for the accuracy and legality of Customer Personal Data. This matters more than usual for a relationship management product: Customer Personal Data will typically include information about prospects, investors, partners, and their staff who have not interacted with Storm OS directly. 3.3 Where Customer is itself a processor for another controller, Customer warrants that it has authority to appoint Storm OS as a subprocessor on the terms of this DPA, and references to Customer's instructions include instructions from that controller as passed through by Customer. 3.4 For any processing outside the scope of §1, each party acts as an independent controller. 3.5 Marketing sending. Where Customer uses the Service to send marketing email to its own contacts, Customer is the Controller of the recipient list it sends to, and warrants that it holds valid consent, under applicable law, for every recipient on that list. Storm OS processes the recipient list, the message content, and the resulting engagement events as Processor, on Customer's instructions, under this DPA, once Customer's sending domain is verified. 3.6 The assistant and research. The assistant and web research are on unless a Workspace Admin turns them off, during setup or at any time. Leaving either on, which is part of Customer's configuration of the Service, and an Authorized User then asking for a summary, a document reading or a research run, or filing a document, are Customer's instructions under §4.2 to process the Customer Personal Data involved with the Subprocessors that Annex III lists for that feature, on the terms §7 describes for each of them. A research run looks a person or company up with third-party data providers and on the public web. No field on a record is changed until an Authorized User accepts what the run found, and a research run on a company also files the further company details the data providers return, such as funding, technology, headcount, industry codes, products and competitors, on that company's record. What Storm OS stores from a research run, including the data providers' answers, is kept within Customer's Workspace, and Storm OS never shows it to another customer. ### 4. Instructions 4.1 Storm OS will process Customer Personal Data only: (a) as necessary to provide, secure, and maintain the Service under the Agreement; (b) in accordance with Customer's further documented instructions, where those instructions are consistent with the Agreement and technically feasible; and (c) as required by applicable law, in which case Storm OS will inform Customer of that requirement before processing unless the law prohibits it on important grounds of public interest. 4.2 The Agreement, this DPA, Customer's configuration of the Service, and Customer's use of Service features constitute Customer's complete documented instructions. 4.3 Storm OS will inform Customer if, in its opinion, an instruction infringes Data Protection Laws, and may suspend that instruction until it is amended or confirmed. Storm OS may decline instructions that would require material changes to the Service or that it reasonably believes to be unlawful. 4.4 Prohibited uses. Storm OS will not: (a) Sell or Share Customer Personal Data, as those terms are defined in the CCPA; (b) retain, use, or disclose Customer Personal Data for any purpose other than performing the Service, including any commercial purpose of its own, except as permitted by Data Protection Laws; (c) retain, use, or disclose Customer Personal Data outside the direct business relationship between Storm OS and Customer; (d) combine Customer Personal Data with Personal Data received from or on behalf of another person, or collected from its own interactions with a Consumer, except as permitted for a Service Provider under the CCPA; or (e) use Customer Personal Data to train, fine-tune, benchmark, or evaluate machine-learning or generative artificial intelligence models , whether Storm OS's own or a third party's. 4.5 Storm OS certifies that it understands the restrictions in §4.4 and will comply with them. 4.6 Aggregated and deidentified data. Storm OS may create and use aggregated or deidentified data derived from operating the Service (for example, volumetric and performance statistics) for capacity planning, security, and product improvement, provided such data cannot reasonably be used to identify any Data Subject or Customer, Storm OS commits to maintaining it in deidentified form, does not attempt to reidentify it, and contractually obligates any recipient to the same. ### 5. Confidentiality and personnel 5.1 Storm OS will treat Customer Personal Data as Customer's Confidential Information under the Agreement. 5.2 Storm OS will ensure that personnel authorized to process Customer Personal Data are bound by written confidentiality obligations that survive termination of employment, are trained on their data protection responsibilities, and are granted access only on a least-privilege, need-to-know basis. 5.3 Personnel access to Workspace content. Storm OS does not routinely access Customer Personal Data. Personnel may access it only: (a) at Customer's request, to provide support, via a support session that requires a stated reason, is capped at 60 minutes, displays a persistent in-app banner to the acting user, is recorded in Storm OS's platform audit log, and is written to Customer's own Workspace audit log so Customer's administrators can see who accessed what, when, and why; (b) as strictly necessary to investigate or remediate a security incident, data corruption, abuse, or a serious availability failure, limited to what the investigation requires and audited on the same terms; or (c) where compelled by law, subject to §10.6. Support sessions cannot change a user's password or email address, and cannot export Customer Data, unless the acting operator holds an explicitly elevated support permission. Development and testing are performed against synthetic seed data. ### 6. Security 6.1 Storm OS will implement and maintain the technical and organizational measures set out in Annex II , designed to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, and the nature, scope, context, and purposes of processing. 6.2 Storm OS may update those measures over time provided the overall level of protection is not materially reduced. 6.3 Customer is responsible for the security decisions within its control: configuring Workspace access defaults, sharing rules and roles; enabling and enforcing multi-factor authentication; managing membership and promptly deactivating departed users; and securing the devices on which the Progressive Web App is installed. ### 7. Subprocessors 7.1 General authorization. Customer grants Storm OS general authorization to engage Subprocessors, subject to this §7. The Subprocessors engaged as at the effective date are listed in Annex III and maintained at https://storm-os.app/subprocessors . 7.2 Notice and objection. Storm OS will give Customer at least 30 days' notice before adding or replacing a Subprocessor that processes Customer Personal Data, by email to Workspace Admins and by updating the subprocessors page. Customer may object on reasonable data protection grounds within that period by written notice to privacy@storm-os.com . The parties will discuss the objection in good faith; if Storm OS cannot offer a reasonable alternative, Customer may terminate the affected Service without penalty and receive a pro-rata refund of prepaid unused fees. 7.2.1 Early Access Period. During the Early Access Period defined in the Terms of Service (August 1, 2026 through at least March 31, 2027), the 30 days' notice in §7.2 does not apply, because the third party services Storm OS runs on are still being selected and configured. Storm OS will notify Customer by email as soon as reasonably practicable and update the subprocessors page. Customer's right to object under §7.2, and to terminate without penalty if Storm OS cannot offer a reasonable alternative, is unchanged. From the day after the Early Access Period ends, the 30 days' notice applies in full. 7.3 Flow-down and liability. Storm OS will impose on each Subprocessor data protection obligations no less protective than those in this DPA, and remains fully liable to Customer for each Subprocessor's performance. A research data provider that offers no separate data protection terms processes lookups under its published terms instead, as its row in Annex III states. 7.4 Where a Subprocessor is located outside the EEA, UK, or Switzerland, Storm OS will ensure an appropriate transfer mechanism is in place under §10, except with a research data provider that offers no separate data protection terms (§7.3). ### 8. Data subject rights and assistance 8.1 Self-service first. The Service gives Customer the tools to respond to most Data Subject requests directly: search, record edit and delete, soft delete with a 30-day Recycle Bin, merge, and full Workspace export in CSV/JSON. Customer will use those tools where they are sufficient. 8.2 Assistance. Taking into account the nature of the processing, Storm OS will provide reasonable assistance, by appropriate technical and organizational measures and insofar as possible, to help Customer fulfill its obligations to respond to requests for access, rectification, erasure, restriction, portability, and objection. 8.3 Requests received by Storm OS. If Storm OS receives a request from a Data Subject relating to Customer Personal Data, it will not respond substantively other than to acknowledge and redirect, and will notify Customer without undue delay (and in any event within 10 business days ) so Customer can respond as Controller. Storm OS will not alter or delete Customer's records in response to such a request without Customer's instruction. 8.4 Further assistance. Storm OS will provide reasonable assistance with data protection impact assessments and prior consultations with Supervisory Authorities under GDPR Articles 35 and 36, and with Customer's obligations under Articles 32 to 36 generally, taking into account the information available to Storm OS. 8.5 Assistance beyond what is reasonably required by Data Protection Laws, or that is disproportionate in scope or frequency, may be chargeable at Storm OS's then-current professional services rates, on prior notice. ### 9. Personal Data Breach 9.1 Storm OS will notify Customer of a Personal Data Breach affecting Customer Personal Data without undue delay and in any event within 48 hours of becoming aware of it, by email to Workspace Admins and the security contact on file. 9.2 The notification will include, to the extent known and as it becomes known: the nature of the breach, the categories and approximate number of Data Subjects and records affected, the likely consequences, the measures taken or proposed to address it and mitigate its effects, and a contact point for further information. Where information is not available at the time of notification, Storm OS will provide it in phases without further undue delay. 9.3 Storm OS will take reasonable steps to contain, investigate, and remediate the breach, and will preserve relevant logs and evidence. 9.4 Storm OS's notification is not an acknowledgment of fault or liability. Customer is responsible for determining whether the breach requires notification to Supervisory Authorities or Data Subjects and for making those notifications. Storm OS will not notify any Supervisory Authority or Data Subject on Customer's behalf without Customer's prior consent, except where independently required to do so by law. 9.5 Customer will keep an accurate security contact email current in the Workspace Admin console. ### 10. International transfers 10.1 Customer acknowledges that Storm OS is established in the United States and that provision of the Service involves transfer of Customer Personal Data to the United States and, where applicable, to Subprocessor locations identified in Annex III. 10.2 EEA transfers. Where Customer Personal Data is transferred from the EEA to a country that is not the subject of an adequacy decision, the SCCs are incorporated into this DPA by reference and apply as follows: - Module Two (Controller to Processor) applies where Customer is a Controller; - Module Three (Processor to Processor) applies where Customer is a Processor acting on behalf of a third-party controller; - Clause 7 (docking clause) applies; - Clause 9, Option 2 (general written authorization) applies, with the notice period specified in §7.2 of this DPA; - Clause 11(a) optional language (independent dispute resolution) does not apply; - Clause 17, Option 1 applies, and the SCCs are governed by the law of Ireland ; - Clause 18(b): disputes will be resolved before the courts of Ireland ; - Annex I to the SCCs is populated by Annexes I(A), I(B), and I(C) of this DPA; - Annex II to the SCCs is populated by Annex II of this DPA; - Annex III to the SCCs (where used) is populated by Annex III of this DPA. 10.3 UK transfers. The UK Addendum is incorporated and applies to transfers from the UK, completed as set out in Annex IV . 10.4 Swiss transfers. For transfers subject to the FADP, the SCCs apply with these amendments: references to the GDPR are read as references to the FADP; the competent authority is the Swiss Federal Data Protection and Information Commissioner; the term "Member State" does not limit Data Subjects in Switzerland from bringing proceedings in their place of habitual residence; and the SCCs also protect the data of legal entities until the FADP no longer extends to them. 10.5 Supplementary measures. In addition to the SCCs, Storm OS applies the measures in Annex II, including encryption in transit and at rest, tenant isolation enforced in the database layer, least-privilege and audited personnel access, and the government-request handling in §10.6, as supplementary measures supporting the transfer. 10.6 Government access requests. If Storm OS receives a legally binding request from a public authority for Customer Personal Data, it will: (a) review the request for lawfulness and challenge it where there are reasonable grounds to consider it unlawful, overbroad, or defective, seeking interim relief where appropriate; (b) disclose only the minimum data legally required; and (c) notify Customer of the request before disclosure where legally permitted, or, if prohibited, seek a waiver of the prohibition and provide such information as it is lawfully able, as promptly as possible. Storm OS will document such requests and provide the information required by Clause 15 of the SCCs. 10.7 Alternative mechanisms. If a transfer mechanism relied on here is invalidated, amended, or superseded, the parties will work in good faith to implement a valid alternative (including any successor clauses) without undue delay, and Storm OS may update this DPA accordingly on notice. ### 11. Audit and information rights 11.1 Storm OS will make available to Customer the information reasonably necessary to demonstrate compliance with this DPA and Article 28 GDPR. In the first instance this will be satisfied by: this DPA and its Annexes, the Privacy Policy, the subprocessors page, and a completed standard security questionnaire (Storm OS will use commercially reasonable efforts to complete Customer's own questionnaire once per twelve-month period). 11.2 Where the documentation in §11.1 is genuinely insufficient to demonstrate compliance, Customer may conduct an audit, itself or through an independent auditor bound by confidentiality that does not compete with Storm OS, subject to: at least 30 days' prior written notice; no more than once per twelve-month period except following a Personal Data Breach affecting Customer or where required by a Supervisory Authority; conduct during normal business hours; a scope limited to Storm OS's processing of Customer Personal Data; and no access to other customers' data, to Storm OS's own confidential commercial information, or to production Personal Data of any kind. 11.3 Customer bears its own audit costs and will reimburse Storm OS's reasonable costs for audits beyond the first in any twelve-month period. 11.4 Where the SCCs apply, this §11 is the parties' agreed means of exercising the audit rights in Clause 8.9, without limiting those rights where they cannot be limited by law. ### 12. Return and deletion 12.1 On termination or expiry of the Agreement, Customer may export Customer Personal Data in full, as a documented CSV/JSON bundle covering all objects, custom fields, and relationships, for 30 days , using the Workspace export in the Admin console. 12.2 After the export period, Storm OS will delete Customer Personal Data from active systems within 30 days , and it will age out of backups within Storm OS's rolling backup expiry cycle (currently 35 days). Storm OS will certify deletion in writing on request. 12.3 Storm OS may retain Customer Personal Data to the extent required by applicable law, and will continue to protect it under this DPA for as long as it is retained. ### 13. General 13.1 Order of precedence. In the event of conflict, the SCCs prevail over this DPA, and this DPA prevails over the rest of the Agreement, in each case only as to the subject matter of the conflict. 13.2 Liability. Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Agreement, except to the extent Data Protection Laws prohibit that limitation. Nothing in this §13.2 limits any Data Subject's rights under the SCCs. 13.3 Term. This DPA takes effect with the Agreement and continues until Storm OS ceases to process Customer Personal Data, at which point the obligations that by their nature should survive will do so. 13.4 Changes. Storm OS may update this DPA where required by changes in Data Protection Laws, changes to the Service, or the introduction of new transfer mechanisms, on at least 30 days' notice to Workspace Admins, provided no update materially reduces the protections afforded to Customer Personal Data. During the Early Access Period defined in the Terms of Service, that notice period does not apply, as Terms of Service §1 describes. 13.5 Governing law. Except where the SCCs, UK Addendum, or Data Protection Laws require otherwise, this DPA is governed by the law and venue specified in the Agreement. 13.6 Contact. Data protection matters: privacy@storm-os.com . Security matters and incident reports: security@storm-os.com . Contractual matters: legal@storm-os.com . ## Annex I(A): Parties Data exporter (Controller / Processor): the Customer identified in the Agreement. Contact: the Workspace Admin email address and any privacy contact designated by Customer in the Workspace Admin console. Activities relevant to the transfer: use of the Storm OS relationship and pipeline management service. Role: Controller (or Processor where §3.3 applies). Signature and date: deemed executed on Customer's acceptance of the Agreement. Data importer (Processor): On-Call CMO d/b/a Storm OS, 239 4th Ave, Ste 1401, Pittsburgh, PA 15222, USA. Contact: privacy@storm-os.com. Activities relevant to the transfer: hosting and operating the Storm OS application, database, file storage, transactional and marketing email, and support, and AI-assisted features and record research unless Customer turns them off. Role: Processor. Signature and date: deemed executed on Customer's acceptance of the Agreement. ## Annex I(B): Description of processing Categories of Data Subjects - Customer's Authorized Users: founders, employees, contractors, advisors, and observers with Workspace access - Customer's prospects, leads, and customers, and their employees and representatives - Current and prospective investors, and the employees and representatives of funds and syndicates - Partners, resellers, referrers, and their employees and representatives - Any other individual whose details Customer chooses to record in its Workspace Categories of Personal Data - Identity and contact: name, job title, employer, email address, telephone number, postal or business address, social profile URLs, website and domain - Account and authentication (Authorized Users): password hash, Google identity provider subject identifier, MFA enrollment status, session and device metadata, IP address at sign-in - Relationship and workflow: relationship role and sub-type, engagement level, ownership, introductions and associations, pipeline and stage, opportunity value and line items, tasks, next steps, loss reasons, tags, relationship fit and activity scores - Interaction records: notes, logged activities, meeting and call records entered by users, timeline events - Content: attachments and documents uploaded by Authorized Users, which may contain Personal Data determined solely by Customer - Custom fields: additional fields defined by Customer, the content of which is determined solely by Customer - Audit: actor, timestamp, device summary, and before/after values for audited actions - Marketing email engagement: open and click events, and the user agent and IP address at the event, for marketing email a Workspace sends to its own contacts - Form and landing page submissions: the answers a person submits on a Workspace's public form or landing page, the page and step it was submitted on, the time, and, where the form collects them, the referring site and campaign (UTM) parameters - Research results: unless Customer turns research off, the values a research run found about a person or company, the source of each, and the data providers' answers Sensitive data. The Service is not designed for and Customer is contractually prohibited from submitting special category data under GDPR Article 9, data relating to criminal convictions and offenses under Article 10, government identifiers, payment card numbers, health records, precise biometric data, or precise geolocation. If Customer nonetheless submits such data through free-text fields, custom fields, or attachments, Customer does so as Controller and at its own risk, and the restrictions in the Agreement apply. Frequency of transfer: continuous, for the duration of the Agreement. Nature of the processing: collection, recording, organization, structuring, storage, retrieval, consultation, use, indexing, deduplication and merging, scoring, AI-assisted summarization, extraction and drafting, and research with third-party data providers and the public web unless Customer turns them off, synchronization to Authorized Users' devices for offline use, backup, disclosure to Authorized Users and authorized Integrations, marketing email composition, sending, and engagement tracking where a Workspace enables it, erasure, and destruction. Purpose of the processing: providing the Storm OS relationship and pipeline management service to Customer under the Agreement, including hosting, synchronization, notification, reporting, support, security, marketing email sent by Customer to its own contacts where Customer enables it, and AI-assisted features and record research unless Customer turns them off. Duration: for the term of the Agreement, plus the retention and deletion periods in §12 of this DPA. Subprocessor processing: as described in Annex III, for the duration of the Agreement or until the Subprocessor is replaced. ## Annex I(C): Competent Supervisory Authority Where the data exporter is established in an EEA Member State, that Member State's Supervisory Authority. Where the data exporter is not established in the EEA but falls within the territorial scope of the GDPR under Article 3(2) and has appointed a representative under Article 27, the Supervisory Authority of the Member State in which that representative is established. Where the data exporter is not established in the EEA and has not appointed a representative, the Supervisory Authority of Ireland , consistent with the choice of law in §10.2. Storm OS has not appointed an Article 27 representative, on the basis that it markets the Service in the United States only, quotes prices solely in US dollars, and offers the Service solely in English. It will appoint one and update this Annex before actively marketing to the EU or UK. ## Annex II: Technical and organizational measures Storm OS maintains the following measures. Detail is current as at the effective date and may be updated under §6.2. Pseudonymization and encryption - TLS 1.2 or higher for all data in transit, with HSTS enforced on storm-os.app and its subdomains - Encryption at rest at the storage layer for the Postgres database, blob storage, and backups - Passwords hashed with Argon2id and a minimum strength requirement; passwords never stored or logged in recoverable form - Attachments and export bundles stored privately and served only through short-lived signed URLs; no publicly addressable object storage Confidentiality and access control - Multi-tenant isolation: every tenant row carries a workspace identifier; Postgres row-level security is applied as defense in depth; cross-tenant access is covered by a fail-closed test in continuous integration - A single server-side authorization module resolves access on every read and write, and the same module trims list, search, report, and offline-sync results, so clients never receive records they are not entitled to - Capability roles (Admin, Manager, Member, Read-Only) combined with per-object access defaults, admin sharing rules, and per-record shares, all configurable by Customer - Short-lived access tokens plus rotating refresh tokens stored in httpOnly , Secure , SameSite=Lax cookies, never readable by client-side script; refresh-token reuse detection invalidates the entire session family - Optional TOTP multi-factor authentication per user; Workspace-wide MFA enforcement available to Customer administrators - Per-device session listing with individual and global sign-out; deactivating a member immediately revokes sessions and API access - Least-privilege personnel access; support access to Workspace content only under the reason-gated, time-capped, dual-audited process in §5.3 - Brute-force protection with per-account and per-IP throttling and progressive delays Integrity - Append-only audit logging of authentication, membership, role, permission and sharing changes, schema changes, merges, deletions, purges and restores, imports and undo, exports, branding changes, and support sessions, retained 400 days and exportable by Customer administrators - Idempotency keys on unsafe endpoints and per-mutation identifiers on offline sync, preventing duplicate application of retried writes - Field-level conflict detection with explicit user resolution for concurrent offline edits - Soft deletion with a 30-day Recycle Bin; merges reversible for 7 days; imports undoable for 7 days, keeping any field edited since the import - Schema-level input validation on every API payload Availability and resilience - Serverless architecture with automatic scaling and no single points of manual intervention - Managed database with point-in-time recovery and automated backups - Documented disaster recovery procedure with restore drills and recorded RTO/RPO targets - Error monitoring, function error-rate dashboards, dead-letter queue with retry for background jobs Testing and assurance - Automated unit, integration, and end-to-end test suites gating every deployment, including negative authorization tests on every endpoint - Dependency vulnerability scanning - Automated unit, integration, and end-to-end test suites gating every deployment, including denied-path authorization tests on every endpoint, with severity-1 and severity-2 findings remediated before release. Storm OS has not yet commissioned an independent third-party penetration test; it will update this Annex and notify Customers when one is completed Device and endpoint measures (Progressive Web App) - Offline data scoped to the signed-in user and Workspace, and wiped on sign-out - Authentication never stored in JavaScript-readable browser storage - Optional app lock requiring re-authentication after inactivity - Remote session revocation honored on the device's next connection - Attachment binaries not stored offline Organizational measures - Written confidentiality obligations for all personnel with access - Data protection and security awareness training - Documented incident response procedure with defined notification timelines - Subprocessor due diligence and contractual flow-down of these obligations, except as §7.3 describes - Development and testing against synthetic seed data Measures for transfers - The government-request handling process in §10.6 - Storm OS does not currently publish a periodic transparency report. It will notify affected Customers of compelled disclosures directly, as set out in §10.6 ## Annex III: Subprocessors ### Used for every Workspace ### Used only while a Workspace has a feature on The assistant and web research are on unless a Workspace Admin turns them off. Nothing is sent to these Subprocessors while the assistant is off, and the three data providers are used only while web research is also on and an Authorized User runs research on a record or a saved list. Anthropic publishes its own subprocessors, including any provider behind its web search, at https://www.anthropic.com/subprocessors . Integrations a Workspace connects itself. MailChimp, a Workspace's own Stripe account for invoice payments, and a Workspace's own Anthropic key are Integrations under §9 of the Terms. Each runs on the Workspace's own account with that provider, under the Workspace's own agreement with it and on the Workspace's instruction, and none of them is a Storm OS Subprocessor. With a Workspace's own Anthropic key, two things still run on Storm OS's accounts: the background reading of documents already filed on people, companies and deals, which uses Storm OS's Anthropic account, and a research run's calls to the data providers above. The current list is maintained at https://storm-os.app/subprocessors . ## Annex IV: UK International Data Transfer Addendum Completed in accordance with the UK Addendum (version B1.0). Table 1: Parties. As set out in Annex I(A). Start date: the date Customer accepted the Agreement. Table 2: Selected SCCs, Modules and Selected Clauses. The SCCs as incorporated by §10.2 of this DPA, including the modules and optional clauses selected there, and Annexes I to III as populated by this DPA. Table 3: Appendix Information. - Annex 1A (List of Parties): Annex I(A) of this DPA - Annex 1B (Description of Transfer): Annex I(B) of this DPA - Annex II (Technical and organisational measures): Annex II of this DPA - Annex III (List of Sub processors): Annex III of this DPA Table 4: Ending the Addendum when the Approved Addendum Changes. Neither party may end the UK Addendum as set out in Section 19 of the UK Addendum. ### Acceptance This DPA is accepted by Customer on acceptance of the Agreement and requires no signature. A countersigned PDF is available on request at legal@storm-os.com . On-Call CMO d/b/a Storm OS 239 4th Ave, Ste 1401, Pittsburgh, PA 15222, USA privacy@storm-os.com · security@storm-os.com · legal@storm-os.com Questions about any of this go to legal@storm-os.com . Privacy requests go to privacy@storm-os.com , and anything security related to security@storm-os.com . Earlier versions of these documents are kept at storm-os.app/privacy/archive . --- ## Subprocessors · Storm OS URL: https://storm-os.app/subprocessors/ Summary: The vendors Storm OS uses to run the product, what each one processes, and where. Workspace admins get 30 days notice before we add another one. Legal # Annex III: Subprocessors The vendors that help us run Storm OS and what each one receives. Workspace admins are told by email when we add one, and can object. This list is Annex III of the Data Processing Addendum , version 1.4, effective October 20, 2026. ### Used for every Workspace ### Used only while a Workspace has a feature on The assistant and web research are on unless a Workspace Admin turns them off. Nothing is sent to these Subprocessors while the assistant is off, and the three data providers are used only while web research is also on and an Authorized User runs research on a record or a saved list. Anthropic publishes its own subprocessors, including any provider behind its web search, at https://www.anthropic.com/subprocessors . Integrations a Workspace connects itself. MailChimp, a Workspace's own Stripe account for invoice payments, and a Workspace's own Anthropic key are Integrations under §9 of the Terms. Each runs on the Workspace's own account with that provider, under the Workspace's own agreement with it and on the Workspace's instruction, and none of them is a Storm OS Subprocessor. With a Workspace's own Anthropic key, two things still run on Storm OS's accounts: the background reading of documents already filed on people, companies and deals, which uses Storm OS's Anthropic account, and a research run's calls to the data providers above. The current list is maintained at https://storm-os.app/subprocessors . Questions about any of this go to legal@storm-os.com . Privacy requests go to privacy@storm-os.com , and anything security related to security@storm-os.com . Earlier versions of these documents are kept at storm-os.app/privacy/archive . --- ## Not for indexing The 15 public pages above are the whole of the readable site. Everything else on this origin is an authenticated product surface, excluded in /robots.txt and marked noindex in its own HTML: - The tenant app at https://storm-os.app/app/, behind sign-in. Nothing past it is public. - A frozen clickable demo at https://storm-os.app/demo/, kept as a reference, not as a source of facts about the product. - The internal operator console at https://storm-os.app/ops/, on its own auth realm with mandatory MFA. - The JSON APIs at https://storm-os.app/v1/ and https://storm-os.app/ops/v1/, which are endpoints, not documents. Please cite the public pages listed above instead. If a claim about Storm OS is not on one of them, it did not come from us.