Developer API · MCP server

Privacy policy

What the AstroNest Developer API, developer portal and MCP server keep, what they never store, and who else handles data. In short: we keep your account, keys and a usage record per call; we do not store the birth data or questions in your requests.

Last updated 1 November 2026.

1. Who we are and what this covers

AstroNest is operated by OneDot Links Inc., a corporation based in Ontario, Canada (“AstroNest”, “we”, “us”).

This policy covers:

  • the developer portal at www.astronest.ai/developer and the developer documentation under www.astronest.ai/developers;
  • the AstroNest Developer API at https://www.astronest.ai/api/developer/v1;
  • the AstroNest MCP server at https://www.astronest.ai/api/developer/mcp, including when you use it through an AI assistant such as Claude or ChatGPT (section 5).

The AstroNest consumer app has its own privacy policy. The use of the API is also governed by the Developer API terms.

2. Two kinds of data, two roles

  • Your account data (your email, keys, usage, purchases, support messages). We decide how this is used, and this policy describes it.
  • Request data: the birth details, questions and other inputs you send in an API or MCP call, which are often about your own users. We process it only to answer the call, on your behalf. If you send data about other people, you are responsible for having a lawful basis and for telling them, and they should contact you about it first.

Business customers who need a data processing addendum can ask for one at astronest@onedotlinks.com.

3. What we keep about you

  • Account. Your email address, whether it is confirmed, when the account was created, and a display name if you set one. Your password is handled by our authentication provider and never stored by us in readable form.
  • Sign-ins. The date and your country (a two-letter code from our hosting provider). Not your IP address or city.
  • API keys. A one-way hash of each key (we cannot read the key back), its short prefix and last four characters, the name you give it, its scopes, whether it is live or sandbox, its status, an optional monthly credit limit, and when it was created, last used, rotated, revoked or set to expire.
  • A usage record for every call: which key, a request identifier, the endpoint, the channel (direct API, MCP, or a marketplace), the credits charged, the response time, the HTTP status and the time. It contains no birth data, questions, names or response content.
  • Credits and purchases. Your balances, monthly usage totals, your free-credit grant and its expiry, and for each purchase the pack, the credits, the payment reference and the date, plus any refund or dispute adjustment.
  • Terms acceptance. The terms version you accepted, when, and your browser's user-agent string. Not your IP address.
  • Support messages you send from the portal, with your account email, and our replies.
  • Docs visit statistics. When someone views the developer documentation pages, we record the page, the host name of the referring site (not the full address), a campaign tag if the link carried one, a two-letter country, a salted one-way hash of the IP address (not the address itself) and whether the visitor was signed in. Known bots are skipped. This privacy policy and the terms page do not record visits.

We do not receive your card details. Payments are taken by Stripe, which shares with us the payment status, a payment reference, the purchaser's email and the pack bought; we give Stripe your account email and account identifier to link the payment to your account.

4. Birth data and other request data

Requests contain birth details (date, time if known, timezone, latitude and longitude). Some endpoints also take names (optional), gender, a free-text question or event description, dates, places, and the life area a reading is about.

  • Processed in transit, not stored. We do not write request bodies or responses to any database, file or cache. They are held in server memory while the call runs and discarded when the response is sent. The usage record above holds none of it.
  • Sandbox keys. Inputs are checked for validity and then discarded. Nothing is computed, no language model is called, and a fixed sample is returned.
  • Charts are computed by our own engine, inside our hosting provider, without sending your inputs to a separate chart or ephemeris service.
  • Narrated text. Two endpoints write a narrative with a language model: /v1/forecast and /v1/timing/resolve (the MCP tools get_forecast and resolve_timing). For these, a reading computed from the birth data, the life area and the question are sent to Anthropic, with OpenAI as the fallback if Anthropic fails. /v1/forecast also sends the question text to OpenAI to create a text embedding used to find relevant source passages. No other endpoint calls a language model.
  • We use these providers through their business APIs, whose terms do not allow them to train models on what we send. They may keep it for a limited period to monitor for abuse.
  • We never use request data or responses to train models, and we do not sell or share them for advertising.

Our hosting provider keeps its own platform logs of requests (for example time, path, status code and user agent) for a limited period. Our code does not write request bodies to them.

5. Connecting through AI assistants

You can add AstroNest to an AI assistant, such as Claude, ChatGPT or another app that supports the Model Context Protocol (MCP), so the assistant can call AstroNest for you.

  • You authorise the connection. You give the assistant one of your API keys or, where the assistant supports it, sign in to your AstroNest developer account and approve its access.
  • We receive only what the assistant sends. When the assistant decides to use an AstroNest tool, it sends us that tool's inputs, such as the birth details and question you gave it. We do not receive your conversation, your chat history or anything else in the assistant. Those inputs are handled exactly as in section 4.
  • Calls are billed to your account, as API calls, at the price of the tool used. Sandbox keys stay free. You can set a monthly credit limit on a key so an assistant cannot spend more than you allow.
  • What we record about the connection. Each tool call creates the usage record in section 3, labelled as MCP. For each tool call the MCP server also logs the client's user-agent string and the names (not the values) of the request headers, so we can tell which assistants connect. If you connect by signing in, we also store the assistant's name, when you approved it and when it was last used; its access tokens are stored only as one-way hashes.
  • Disconnect at any time from the developer portal at www.astronest.ai/developer (Connected apps, or revoke the key the assistant uses), or by removing AstroNest in the assistant's settings.
  • The assistant is a separate service. How Anthropic, OpenAI or another provider handles your conversation is governed by their privacy policy, not this one.

6. How we use account data

  • to run the service: sign you in, check keys and scopes, answer calls, and show you your usage;
  • to bill: count credits, apply free credits, record purchases, refunds and disputes;
  • to protect the service: rate and concurrency limits, abuse and fraud prevention, security;
  • to support you and to tell you about changes to the service or these documents;
  • to understand, in aggregate, how developers find and use the API (for example, how many docs visitors create a key);
  • to meet legal obligations, such as keeping payment records.

Where a law asks for a legal basis: providing the service you signed up for (contract), protecting and improving it (legitimate interests), and keeping records the law requires (legal obligation). We do not sell personal information and do not use it for advertising.

7. Service providers and where data is processed

ProviderWhat it doesData it handlesWhere
Vercel Inc.Hosting; runs every API and MCP call, including chart computationAll request data, in memory while a call runs; request logsUnited States
Supabase, Inc.Database and sign-inAccount data in section 3; no request dataCanada (Montreal)
Anthropic, PBCWrites narrated text for the two narrated endpointsA computed reading, the life area and the questionUnited States
OpenAIFallback narration; question embedding for /v1/forecastAs for Anthropic; the question text for embeddingsUnited States
Stripe, Inc.Payments for credit packsYour payment details (collected by Stripe), your account emailUnited States and other Stripe locations
Upstash, Inc.Short-lived counters for rate and concurrency limitsA counter keyed by account identifier; no request dataUnited States

Your account data is stored in Canada. Request data is processed in the United States while each call runs. Where data leaves your country we rely on contractual safeguards with these providers. If you call AstroNest through a marketplace such as RapidAPI, that marketplace's own policy covers your account with it.

8. How long we keep it

  • Request data and responses: not stored; discarded when each call ends (language-model providers: see section 4).
  • Account, keys, balances, usage records and terms acceptances: while your account is open; deleted when the account is deleted.
  • Purchase records: while your account is open; deleted when the account is deleted. Stripe keeps its own payment records under its policy.
  • Sign-in records (date and country): 13 months.
  • Support messages: 24 months from receipt.
  • Docs visit statistics: no fixed deletion period is set yet. They hold no IP address (only its salted hash) and no account email.

9. Security

  • The API and portal are served only over HTTPS, and calls to our providers are encrypted in transit.
  • API keys are random secrets shown once; we store only a one-way hash. Keys can be scoped, given an expiry, rotated and revoked.
  • Database tables are protected by row-level security; billing and usage records are reachable only by our server.
  • Provider keys and other secrets are kept in our hosting provider's environment settings, not in source code.
  • We hold no independent security certification (such as SOC 2 or ISO 27001).

10. Your rights and choices

Depending on where you live, you can ask to access, correct, delete or export your personal information, object to or restrict some uses, and withdraw consent. Email astronest@onedotlinks.com from your account address. We reply within 30 days.

  • Revoke keys and see your usage at any time in the developer portal.
  • To close your account, email us.
  • If your users ask us about data you sent, we will pass the request to you: we do not keep their request data, so we cannot look it up.
  • You can complain to a data protection authority, such as the Office of the Privacy Commissioner of Canada, or the authority where you live.

11. Children

The developer service is for businesses and professionals aged 18 or older. Do not direct an app built on AstroNest at children, and do not send data about anyone under 18 unless the law allows it and you have any parental consent it requires.

12. Cookies

The developer portal uses the session cookies needed to keep you signed in. The documentation pages set no advertising or third-party tracking cookies. The API and MCP server use no cookies; they authenticate each call with your key or authorised connection.

13. Changes to this policy

We will post any change on this page with a new date. For a material change, we will also tell account holders by email or in the developer portal before it takes effect.

14. Contact, Privacy Officer and Grievance Officer

For privacy questions or to exercise your rights: astronest@onedotlinks.com.

Privacy Officer: OneDot Links Inc., Ontario, Canada (astronest@onedotlinks.com).

For users in India (Digital Personal Data Protection Act, 2023): Grievance Officer, OneDot Links Inc. (astronest@onedotlinks.com). Grievances will be acknowledged within 48 hours and resolved within 30 days.