Astera Bond

Privacy Policy

Astera Bond

Effective date: September 13, 2026

Plain-language summary. Astera Bond is available through mobile, web, and supported AI clients such as ChatGPT and Claude. You can begin some AI-client/MCP features without signing in. We collect only the information reasonably needed to provide the Bond workflow, keep saved Connections and episode history associated with the correct user, synchronize protected accounts, maintain security, and operate the service. We do not sell personal information. The public Astera Bond MCP does not store raw screenshot image bytes or full raw pasted message transcripts from AI-client episode analysis.

1. Who we are

This Privacy Policy explains how Maks Astera / Maksym Andriienko (“we”, “us”, or “our”) handles information when you use Astera Bond through supported mobile applications, web applications, websites, and Model Context Protocol (“MCP”) integrations such as Astera Bond connectors for ChatGPT and Claude (collectively, the “Service”).

2. Scope of this Policy

Astera Bond may be accessed through different interfaces that share the same underlying account and saved Bond data. Features may differ by platform. This Policy applies to data handled by Astera Bond itself.

When you use Astera Bond inside a third-party AI client such as ChatGPT or Claude, that provider also processes the conversation content you submit to its service under its own terms and privacy practices. For ChatGPT, you can review OpenAI’s privacy information at https://openai.com/policies/privacy-policy/. For Claude, you can review Anthropic’s privacy information at https://www.anthropic.com/legal/privacy.

3. Information you provide

Depending on the features you use, you may provide:

an optional display name or nickname;
a language preference and onboarding reason;
user-created Connection labels or nicknames;
relationship status, desired relationship format or goal, and analysis focus selected for a Connection;
structured summaries of relationship episodes that you explicitly choose to save;
the real-world date or time you assign to a saved episode;
goal-relative Episode Signals and descriptive Words / Actions / Direction evidence associated with saved episodes;
support messages and information you choose to include when contacting us.

Some mobile or web versions of Astera Bond may also offer optional self-reflection questionnaires or Partner Snapshot features and may store answers or resulting profile dimensions. These scored questionnaire features are not required for the public MCP connector workflow.

Please avoid entering information that you do not have the right to provide. You may use nicknames or labels instead of real names for other people.

4. Guest use and pseudonymous identifiers

You may begin using supported Astera Bond MCP features without signing in. Merely opening or previewing the plugin does not create a saved guest record.

When you explicitly choose to save onboarding information, create a Connection, update saved Bond data, or save an episode, Astera Bond may create a Firebase Anonymous user so that guest history can persist.

A supported AI client may provide a host-scoped identifier so Astera Bond can reconnect the same guest history. Astera Bond does not store the raw host identifier for this purpose; it uses a one-way derived key.

5. Account sign-in and synchronization

You may choose to protect or synchronize Astera Bond data by signing in with a supported authentication method such as Google, Apple, or email-based authentication through Firebase Authentication.

If an existing guest history is protected into an empty authenticated Astera Bond account, Astera Bond may transfer that guest history to the authenticated account and remove the old anonymous guest copy after a successful transfer. Astera Bond does not automatically merge two already populated relationship histories.

When you connect an Astera Bond account through a supported AI client such as ChatGPT or Claude, OAuth is used to authorize access. OAuth access/refresh tokens, Firebase identifiers, and other authentication internals are not returned as ordinary Bond tool output.

6. Data stored in Firebase and Google Cloud

Astera Bond may store account and Service data in Google Firebase and Google Cloud services, including Firebase Authentication, Cloud Firestore, Cloud Run, and related infrastructure. Stored data may include:

anonymous or authenticated user identifiers needed to associate data with the correct user;
onboarding state and optional profile fields;
Connections and their selected goals/status/focus;
saved structured episode summaries and event dates;
goal-relative Episode Signals and descriptive longitudinal evidence;
subscription-entitlement status;
technical fields needed to operate, secure, synchronize, and maintain the Service.

7. AI clients / MCP data handling

Astera Bond MCP operates only on the task-specific information that the AI client or model intentionally sends to an Astera Bond tool. The MCP server does not pull, reconstruct, or infer the user’s full conversation history from the AI client.

The public Astera Bond MCP does not store raw screenshot image bytes or the full raw pasted message transcript supplied to an AI client such as ChatGPT or Claude for an episode analysis. The AI client provider may process the screenshot, text, or other evidence the user explicitly shares in that conversation under its own terms and privacy practices. Astera Bond may receive and store only the bounded structured result needed for the Bond workflow when the user chooses to save it.

Users may also choose an unsaved analysis path. An unsaved episode analysis is not added to the Astera Bond relationship timeline by the MCP.

8. Episode Signals and analysis boundaries

Astera Bond may assign a categorical Episode Signal such as green, yellow, red, or insufficient data. The signal describes only a specific episode relative to the relationship goal selected by the user.

An Episode Signal is not a score, diagnosis, safety determination, or personality classification of another person, and it is not a global rating of the relationship. The same observable episode may be interpreted differently for different user-stated goals.

The public Astera Bond MCP does not use numeric personality or partner scores. It is designed to distinguish observable facts from practical possibilities and unknowns, and it does not intentionally infer hidden motives or sensitive personal attributes from relationship messages.

9. Analytics, diagnostics, and service logs

Mobile or web versions of Astera Bond may use Firebase Analytics to understand general feature usage and Firebase Crashlytics to diagnose crashes and stability problems. These services may process app instance identifiers, device/app information, usage events, crash logs, diagnostics, and related technical data.

We design analytics events not to include names, message contents, screenshots, relationship notes, or other free-form private content.

Google Cloud and other infrastructure providers may automatically process limited technical request metadata, such as timestamps, IP addresses, user-agent information, and error/security logs, as necessary to host, secure, and troubleshoot the Service. We do not use this technical metadata to build relationship or personality profiles.

10. Remote configuration and app operation

Firebase Remote Config or similar services may be used in mobile or web versions of Astera Bond to deliver feature settings, maintenance flags, minimum-version settings, and other configuration needed to operate the Service.

11. Payments and subscription entitlements

Astera Bond may offer paid features through supported channels such as Apple App Store, Google Play, or Stripe on the Astera Bond website. Payment providers process payment-card or store-payment information under their own terms.

Astera Bond does not store full payment-card details. We may store or receive customer/subscription identifiers, purchase status, expiration information, and entitlement state needed to provide features already included in your account.

The AI-client/MCP integration may read an existing entitlement so that a signed-in user can access features already included in the user’s Astera Bond account. The MCP does not require payment-card data as a tool input.

12. How we use information

to provide, maintain, and synchronize Astera Bond;
to save Connections, selected goals, and episode history when you ask us to save them;
to compare a current or saved episode with the relationship goal selected by you;
to summarize dynamics over the episodes you choose to save;
to maintain guest or authenticated account state and associate data with the correct user;
to provide features already included in an existing subscription entitlement;
to understand general Service usage where analytics are enabled;
to detect, diagnose, and fix crashes and technical problems;
to protect the Service against abuse, unauthorized access, and security incidents;
to answer support and privacy requests;
to comply with legal, security, tax/accounting, and platform obligations.

13. Service providers and categories of recipients

Information may be processed by the following categories of recipients when reasonably necessary to provide the Service:

Google Firebase / Google Cloud for authentication, database storage, cloud hosting, analytics, diagnostics, and related infrastructure;
AI client providers, such as OpenAI when you invoke Astera Bond through ChatGPT, or Anthropic when you invoke Astera Bond through Claude, for conversation and model processing controlled by that provider;
payment and platform providers, such as Stripe, Apple, or Google, for payment processing, purchase verification, and entitlement management;
support, security, legal, or regulatory recipients when reasonably necessary to respond to requests, prevent abuse, protect rights, or comply with law.

These providers process information under their own terms, privacy commitments, and applicable data-processing arrangements.

14. Data sharing and sale

We do not sell your personal information or saved relationship content. We do not use saved relationship content for advertising. We disclose information only as described in this Policy, to service providers needed to operate the Service, when required by law, or when reasonably necessary to protect users, the Service, or legal rights.

15. Data retention

Authenticated Astera Bond data. Saved account and relationship data is retained for as long as the Astera Bond account remains active or until the user deletes the relevant data, deletes the account, or submits a valid deletion request, subject to limited retention required for legal, security, fraud-prevention, tax/accounting, or dispute-resolution purposes. We do not apply a separate fixed automatic expiration to active saved relationship records.

Unprotected guest MCP history. Guest history is retained until it is protected/synchronized into an authenticated account, deleted through available controls, or deleted following a valid privacy/deletion request. At present, unprotected guest histories do not have a separate fixed automatic expiration period. When a guest history is successfully transferred into an empty authenticated account, the old anonymous guest copy is removed after the transfer.

Authentication records. Authentication and OAuth-related records are retained only as needed to maintain, secure, expire, revoke, or troubleshoot the relevant authentication session or account relationship.

Analytics, crash, and infrastructure logs. Analytics, diagnostics, and infrastructure/security logs are retained according to the configured retention settings and operational requirements of the applicable service provider. These records may not always be directly identifiable by us from an email address.

Payment and legal records. Purchase, subscription, tax/accounting, fraud-prevention, or dispute records may be retained for the period required by applicable law or reasonably necessary to establish, exercise, or defend legal rights.

16. User controls, account deletion, and data deletion

You control whether to save an episode to Astera Bond. You may choose an unsaved analysis path. Guest users can choose whether to protect/synchronize guest history with an authenticated Astera Bond account.

You can request deletion of your Astera Bond account and associated data using the instructions on our Data Deletion page. Supported mobile/web versions may also provide an in-product path for account deletion.

For privacy or deletion requests, contact asteraspprt@gmail.com. We may request reasonable information needed to verify the request and identify the relevant Astera Bond data.

17. Security

We use reasonable technical and organizational safeguards, including authenticated access controls, bounded tool permissions, and controls intended to restrict users to their own protected data. No method of electronic storage or transmission is completely secure, so absolute security cannot be guaranteed.

18. Other people’s information

Astera Bond may allow you to save a nickname, relationship status, goal-relative observation, or structured episode summary involving another person. You are responsible for ensuring that you have a lawful basis or appropriate permission to provide information about other people.

We encourage you to use nicknames and avoid unnecessary identifying or sensitive information. Astera Bond does not need another person’s full legal name, address, precise location, government identifier, payment details, credentials, or medical records to provide its relationship-context workflow.

19. Restricted and sensitive information

Please do not submit restricted credentials or regulated records to Astera Bond tools. Do not provide payment-card details, government identification numbers, passwords, API keys, MFA/OTP codes, or protected health information as Astera Bond MCP tool inputs.

Astera Bond does not intentionally request sensitive or special-category information such as health diagnoses, political opinions, religion, sexual orientation, or other protected characteristics for the public MCP workflow. If such information appears incidentally in content you choose to share with an AI client, Astera Bond tools are designed to omit unnecessary sensitive details from saved structured relationship summaries.

20. Age eligibility

Astera Bond is not directed to children under 13. Access through ChatGPT, Claude, or another AI client is subject to that platform’s age and account eligibility requirements. Mobile or web versions of Astera Bond may carry higher age ratings or restrictions where required by an app store, local law, or platform policy.

21. Self-reflection and professional-advice disclaimer

Astera Bond is designed for education, organization of relationship context, and self-reflection. It is not a medical device and does not diagnose, treat, cure, or prevent any condition. Astera Bond results should not be treated as professional psychological, psychiatric, medical, legal, emergency, or safety advice.

22. International data processing

Service providers may process information in countries other than your country of residence. Where required, processing is subject to applicable legal safeguards and provider data-protection terms.

23. Your privacy rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of certain personal information, and to withdraw consent where processing is based on consent. You may also have rights under applicable U.S. state, Canadian, EEA, UK, or other privacy laws.

To submit a privacy request, contact asteraspprt@gmail.com. We may need reasonable information to verify the request and identify the relevant Astera Bond account or guest history.

24. Changes to this Policy

We may update this Privacy Policy when the Service, our providers, supported AI integrations, or legal requirements change. We will update the effective date above and, when appropriate, provide additional notice.

25. Contact

Developer: Maks Astera / Maksym Andriienko
Email: asteraspprt@gmail.com
Website: https://maksastera.com/apps/astera-bond/