1. Overview
This policy explains what Rad Soft Inc. ("we", "us", "our") collects when you use the Markbase website at markbase.co, the API at api.markbase.co, your dashboard, and our emails, together the "Service". It also explains how we use that information and who else handles it.
The Markbase SDK and MCP server run on your own machine and call the API, so this policy covers the requests they make. If you connect the MCP server to an AI assistant, that assistant's provider handles your prompts and results under its own terms.
2. Information We Collect
Account: Your email address, plus your name and profile image if you sign in with Google or GitHub. For those sign-ins we also keep the provider's account ID and sign-in tokens, which we encrypt.
Sign-in sessions: The IP address and browser details for each signed-in session.
API keys: Your key, plan, any custom limits, and when the key was last used. We store keys so your dashboard can show them, and account emails can include your key.
Billing: Stripe collects your payment details, and we do not receive your full card number. We keep your Stripe customer and subscription IDs, plan, subscription status, and renewal date.
API requests: For each request, with or without a key, we record the method, path, status code, response time, plan, API key, IP address, and time. We also store an approximate location (country, region, and city) that we look up from the IP address using a service we run ourselves, and we remove the IP address and city after 90 days. A path can include a trademark serial number.
Search terms: Our usage records, API server logs, and reverse proxy logs store the path without the query string, so they do not contain what you searched for. Proxy logs written before November 6, 2026 can still contain search terms until they are deleted, by the end of January 2027. Search terms are part of the request URL, so Cloudflare handles them in transit. Names you send to batch clearance travel in the request body, and we do not log or count request bodies.
Search and filter counts: We keep daily totals of the search terms, owner names, and filters used on the API so we can see what it is used for. A search term is saved only after at least three different API keys or IP addresses have searched for it on the same day, so a name checked from only one or two of them is never saved. Until then it is held in memory with a temporary hash of each caller, and both are discarded by the end of the day. Saved terms are lowercased and shortened to 100 characters. These totals do not include an API key, IP address, or account.
Website analytics: We use PostHog for page views and product usage, and Vercel Analytics for site traffic. PostHog uses cookies and local storage to connect activity to a pseudonymous identifier, which is linked to your account ID when you open your dashboard. We remove query strings from page URLs before they reach PostHog. Session recording and automatic interaction capture are disabled. Like any web request, these reach the provider with your IP address, which it may use to estimate your general location.
Activation events: Our servers send PostHog events about your account's setup, such as your first successful request. They include your account ID, the endpoint category, and your plan, but not API keys, email addresses, IP addresses, search terms, or trademark serial numbers.
Signup source: We store a first-touch source category, signup method, and public landing page with your account, using a cookie that expires after 90 days. We do not retain raw referral URLs or query strings for this attribution. Missing sources remain unknown.
Contact form: The name, email address, company, plan, and message you send reach us by email, and you get a copy. We also check whether that email address has an account so we can help you. We do not save these messages in our database.
3. How We Use Your Information
- To provide the Service, sign you in, and deliver your API key
- To count quotas, enforce rate limits, and detect abuse
- To take payment and deal with billing problems
- To send account and service emails: sign-in links, your API key, a welcome message, a one-time setup follow-up, and warnings at 80% and 100% of your monthly quota
- To tell paying customers about service incidents
- To send The Markbase Drop, our product update email, to verified account holders. Every issue has an unsubscribe link
- To understand how the Service is used and improve it
- To respond to support requests and meet legal obligations
4. Who Handles Your Information
We do not sell or rent your personal information, and we do not use advertising networks. The API, database, search index, and backups run on servers we operate. These service providers handle information needed to run the Service:
- Stripe: payments and billing
- Resend: email delivery, including email addresses and unsubscribe status
- PostHog: product analytics
- Vercel: website hosting and site analytics
- Cloudflare: the network between you and the API, which handles full request URLs
- Railway: hosting for Pingbase, our incident notification service, which receives the names and email addresses of active paying customers
- CrowdSec: security tooling that reads our proxy logs and can share addresses flagged for abuse
- Google and GitHub: sign-in, only if you choose it
- Google Fonts: fonts on the hosted API reference at api.markbase.co/docs
We may also disclose information if the law requires it or to protect our rights, our users, or the Service. If Rad Soft Inc. is involved in a merger, acquisition, or sale of assets, your information may transfer as part of that deal.
5. Data Retention
- Account, key, and subscription records: while your account is active, and afterward as needed for operational and legal obligations.
- API request records: we use these for service operations, security, and product analytics. We remove the IP address and city after 90 days. The rest of each record, including the API key, path, country, and region, has no fixed deletion date.
- Sign-in sessions: we remove the IP address 90 days after a session expires.
- Reverse proxy logs: about 11 weeks at most. They hold the request path, time, and browser details, and can include an IP address.
- Search and filter counts: 90 days.
- Database backups: about 30 days, so deleted information can remain in a backup until it expires.
- Emails you send us: these stay in our mailbox with no fixed deletion date.
6. Security
We use TLS for connections to the Service, encrypt stored sign-in tokens from Google and GitHub, and restrict access to production systems. No system is 100% secure, and we cannot guarantee absolute security. Your API key works like a password, so keep it private and rotate it from your dashboard if it is exposed.
7. Cookies and Local Storage
- Sign-in: a session cookie across markbase.co and api.markbase.co. It lasts up to 7 days and renews as you use the site.
- Signup source: a cookie that expires after 90 days.
- Analytics: a PostHog cookie and local storage entry.
- Preferences: your light or dark theme, in local storage.
We do not use advertising cookies. You can block cookies in your browser, but signing in needs them.
8. Your Choices and Rights
- Unsubscribe from The Markbase Drop with the link in any issue. Account and service emails continue while you have an account.
- Rotate your API key from your dashboard, and cancel a subscription from the billing portal there.
- Ask us to access, correct, or delete your personal information by emailing hello@radsoftinc.com. Accounts are closed this way too. We will confirm the request comes from you first, and we may keep records the law requires us to keep.
Depending on where you live, local privacy law may give you other rights, including the right to complain to a data protection authority.
9. Public Trademark Records
The trademark data we serve is separate from your account information. It comes from public USPTO records, which can include the names and addresses of trademark owners and the names of their attorneys. To change a record, contact the USPTO. We update our copy from what the USPTO publishes.
10. Where We Process Information
Rad Soft Inc. is based in the United States, and our servers are there. If you use the Service from another country, your information is processed in the United States, where privacy laws may differ from those where you live.
11. Children
Markbase is built for developers and businesses. It is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact us and we will delete it.
12. Changes to This Policy
We may update this policy. We will post the new version here with a new date and note material changes in the changelog.
13. Contact
For privacy questions, contact us at hello@radsoftinc.com.