Skip to content

Privacy Policy

Last updated: November 13, 2026

This policy explains what personal information we collect when you use the SEC Blast v3 API and the website at www.secblast.com, what we do with it, who we share it with and what choices you have.

1. Who we are and what this policy covers

1.1 "SEC Blast", "we", "us" and "our" mean Tower Software Inc, 8 The Green, Ste R, Dover, DE 19901. We decide how the personal information described here is used. You can reach us about privacy at support@secblast.com.

1.2 This policy covers the website at www.secblast.com (the "Site"), the account system behind it, and the SEC Blast v3 API at api.secblast.com/v3 (the "API"). It does not cover our other websites or APIs, or other companies' sites that we link to.

1.3 Section 9 deals separately with personal information that appears inside SEC filings, which are public records that we did not write.

2. What we collect

2.1 Account information. Your email address, and your name if you or your sign-in provider give it. If you sign in with Google or GitHub, we receive from that provider the identifier of your account with it and your verified email address. We do not receive your password for those services, and we do not use passwords ourselves: you sign in with a one-time code or link sent to your email, or through one of those providers.

2.2 Organization and team information. The name of each Organization, who its members are and their roles, and the email addresses that members invite.

2.3 Session information. When you sign in we set a cookie that keeps you signed in (section 6). For each session we record when it started and was last used, the network (IP) address and the browser's user-agent string, so that you can see your active sessions and end them.

2.4 Security and abuse-prevention records. We record the IP address, the time, the user-agent string and the account involved when someone signs up, signs in or fails to, asks for a sign-in code, creates an API Key, or starts a payment. We keep a record of who did what in an Organization (for example created or revoked a key, changed a role). We use these records to find and block abuse.

2.5 API usage. For each request made to the API with a key issued through the Site, we record the time, the Organization and the API Key used, the kind of route, the response status, the size of the response, how long it took, the IP address the request came from and a request identifier. We do not record the content of responses. Separately, the servers in front of the API and the Site keep ordinary web-server logs (IP address, time, address requested, status, user-agent).

2.6 Billing information. Payments are handled by Stripe. When you pay, you give your card and billing details to Stripe, not to us. We receive from Stripe, and keep, a customer identifier, your Plan and billing period, the status and amounts of invoices and payments, your billing email address, and, if you save a card for automatic recharge, its brand and last four digits. We never receive or store your full card number.

2.7 Email records. We keep a record of the service emails we send you (what kind, when, and whether the sending succeeded), and your choices about optional email.

2.8 What you send us. The contents of messages you send to support.

2.9 What we do not collect. We do not ask for or need sensitive categories of personal information. The console on the Site sends your API requests from your browser straight to the API; the Site's server does not see the API Key you type there or the responses. We do not buy personal information about you from data brokers.

3. Why we use it

We use personal information to:

  • provide the Service: create and run your Account, sign you in, issue API Keys, apply your Plan's limits, and show you your usage;
  • bill: take payments, keep the Credit balance and its history, issue invoices and refunds, and meet tax and accounting duties;
  • keep the Service secure: detect, investigate and block abuse, fraud and attacks, and enforce our terms;
  • write to you: send sign-in codes, invitations, and notices about your keys, usage, limits, Credit, billing and security; and, only if you opt in, product news;
  • run and improve the Service: measure load, errors and response times, and plan capacity;
  • meet legal duties and establish or defend legal claims.

Where the law requires a legal basis for this, we rely on: performing our contract with you (providing the Service and billing); our legitimate interests in securing and running the Service, which we balance against your rights; your consent (optional email); and compliance with the law.

We do not use your personal information for advertising, and we do not make decisions about you by automated means that have legal or similarly significant effects.

4. Who we share it with

4.1 We do not sell personal information, and we do not share it for cross-context behavioural advertising.

4.2 Service providers. We use these companies to run the Service. Each receives only what it needs for its task:

ProviderWhat it does for usWhat it receives
StripePayments, subscriptions, invoices, refunds, sales tax and payment-fraud checksYour billing details and payment method, which you give to Stripe directly; your Organization's identifier with us; what you bought
PostmarkDelivery of the email we sendYour email address and the content of the message
GoogleSign-in, only if you choose "Sign in with Google"That you are signing in to SEC Blast; Google tells us your account identifier and email address
GitHubSign-in, only if you choose "Sign in with GitHub"That you are signing in to SEC Blast; GitHub tells us your account identifier and email address
Cloudflare (Turnstile)A challenge that tells people from automated sign-up attempts, shown on the sign-in page when neededYour IP address and information about your browser, sent by your browser to Cloudflare when the challenge loads
HostingThe servers the Service runs onEquinix, the data center where our servers are hosted

These companies handle the information under their own terms and privacy policies as well as their agreements with us.

4.3 Your Organization. The owners and administrators of an Organization can see its members, their roles and email addresses, its API Keys, its usage and its record of account actions.

4.4 Legal reasons. We may disclose information where the law, a court order or another binding legal process requires it, or where we reasonably believe it is needed to protect the rights, property or safety of us, our users or others, or to investigate fraud or abuse.

4.5 Business transfers. If the business the Service belongs to is sold or merged, personal information may pass to the new owner, who must continue to honour this policy until it is changed.

5. Analytics and tracking

We use no third-party advertising or analytics trackers on the Site, and we load no fonts, scripts or images from other companies, with one exception: the Cloudflare Turnstile challenge on the sign-in page, which is loaded only when it is needed. If we count visits to the public pages, we do it ourselves, without cookies and without keeping IP addresses.

6. Cookies and browser storage

  • Three cookies, all our own and all strictly necessary. None can be read by scripts in the page, each is sent only to www.secblast.com, and none is used to track you. We set no analytics or advertising cookies. __Host-v3fe_session keeps you signed in; it is removed when you sign out. __Host-v3fe_preauth is set when you ask for a sign-in code and lasts 10 minutes; it ties the code and the link in the email to the browser that asked for them, and is removed when you sign in. __Host-v3fe_oauth_state is set when you start signing in with Google or GitHub and lasts 10 minutes; it ties the answer from that provider to your browser, and is removed when the sign-in finishes.
  • Browser storage. If you open an invitation link before signing in, the invitation is held in your browser's session storage for that tab until you have signed in, and is then removed. We do not keep API Keys or other secrets in browser storage.
  • Other companies' pages. When you pay, you are on a page run by Stripe, and when you sign in with Google or GitHub you are on their pages. Their own cookie practices apply there, and the Turnstile challenge may store what it needs to work.

7. How long we keep it

InformationHow long
Account, Organization and team informationWhile the Account is open
Individual API request records (section 2.5), including the IP address of each requestAbout 90 days
Daily usage totals per Organization, API Key and kind of route (no IP addresses)Kept while they are useful for billing history and capacity planning
SessionsUntil they expire or are ended, then for as long as necessary for security and to keep account records
Security and abuse-prevention records (section 2.4), and blocksFor as long as necessary for security, abuse prevention and account records
Billing records, invoices and the Credit historyAs long as tax, accounting and other laws require, and while needed to deal with disputes
Web-server logsFor as long as necessary to operate and secure the Service
Support correspondenceWhile needed to deal with the matter and for a reasonable time afterwards

When you delete your Account we delete or de-identify your account information, except what we must or may lawfully keep: billing and tax records, the Credit history, records needed to prevent abuse (for example a block on an address or account that was used for abuse), and records needed for a legal claim.

8. Your choices and rights

8.1 What you can do yourself. On the Site you can see and end your sessions, manage your API Keys and team, choose which optional emails you get, and delete your Account. Service emails (for example sign-in codes, billing and security notices) are part of the Service and cannot be switched off while you have an Account.

8.2 Rights under privacy laws. Depending on where you live, the law may give you the right to ask us for a copy of the personal information we hold about you, to correct it, to delete it, to restrict or object to some uses of it, to receive it in a portable form, and to withdraw a consent you gave. We do not treat you worse for using these rights. To use them, write to support@secblast.com from the email address of your Account. We may need to confirm who you are. If we refuse a request we will say why, and you may ask us to look at it again.

8.3 Complaints. If you are not satisfied with our answer you may complain to the data-protection or consumer-protection authority where you live.

9. Personal information in SEC filings

9.1 The filings served by the API are public records that filers submitted to the U.S. Securities and Exchange Commission (SEC) and that the SEC publishes through its EDGAR system. Some contain personal information, for example the names, business addresses and securities transactions of officers, directors and other individual filers. We copy and index these records as published; we do not add personal information to them.

9.2 We cannot change what a filing says. To correct or remove something in a filing, contact the filer or the SEC. When the SEC removes a filing and our systems learn of it, the API stops serving that filing.

10. Security

We use technical and organizational measures intended to protect personal information, including encrypted connections to the Site and the API, restricted access to our systems, and logging of administrative actions. No system is perfectly secure, and we cannot guarantee that information will never be accessed or disclosed without authorization. Treat your API Keys as secrets, and tell us at once if you think one has been exposed.

11. Where information is processed

We are based in the United States and our systems and service providers process information in the United States and other countries. Those countries may have data-protection laws that differ from the law where you live.

12. Children

The Service is for business and professional use by adults. It is not directed to children, and we do not knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, write to us and we will delete it.

13. Changes to this policy

We may change this policy. We will post the new version on the Site with its date, and if the change is significant we will also tell you by email or by a notice on the Site before it takes effect.

14. Contact

Tower Software Inc, 8 The Green, Ste R, Dover, DE 19901. Email: support@secblast.com.