AsAManThinks is a contemplative platform that takes data dignity seriously. This Privacy Policy describes the data we collect when you use asamanthinks.com and its sub-sites, why we collect it, where it lives, who can see it, and how to remove it. Plain language first; specifics second.
1. Plain language summary
- We do not sell your data. We do not have advertising partners. We do not use your content to train AI models.
- We use your activity to personalize the Platform. Reading a book, completing a breathing session, or drawing an Oracle card creates a "Memory Event" that helps Oracle and Messenger respond with awareness of your recent journey.
- You can run AI inference locally. If you connect a local model (Ollama, LM Studio, or llama.cpp), our browser bridge relays your prompts directly between your browser and your localhost. Your prompts never reach our servers in that mode.
- You can export and delete everything. Account > Data > Export downloads a JSON of your content. Account > Delete Account permanently removes it within 30 days.
2. What data we collect
Account data
- Name and email address (required).
- Optional: birth date, time of birth, and birth location — only if you choose to use the astrology / numerology features.
- Authentication tokens for keeping you signed in.
Activity data ("Memory Events")
As you use the Platform, we record short structured events that summarize what you've done. Examples:
- journal_saved — that you saved a journal entry, the word count, and any mood tag you applied.
- breathing_session — the breath pattern, the duration, and the change in HRV-coherence (if measured).
- oracle_reading — the spread you drew and a short summary of the interpretation.
- book_session_started, book_progress, book_finished — which Library title you opened, your last page, and total reading time.
- chat_message, wisdom_viewed, music_play, numerology_calculated, etc.
Each event includes a one-line human summary that the AI features can read, plus a structured payload (JSON). We strip personally-identifying details from event payloads — for example numerology events store the calculated numbers but not your full birth date.
Content you create
Journal entries, oracle reading interpretations, chat history with MaiiaM, lab session notes, book reading progress, study highlights, and any other content you create. This is yours; we store it so the Platform can offer it back to you and so personalization features can work.
Technical data
Standard server logs (IP address, user-agent, request paths, timestamps) for security and debugging. Retained for 30 days. We do not use Google Analytics, Facebook Pixel, or comparable third-party trackers on the marketing site or Platform.
3. Where your data lives
The Platform uses a dual-backend architecture:
- WordPress (identity, content, purchases) — your account, journal entries, oracle readings, library reading progress, and Memory Events live in a MySQL database on our own servers. This is the source of truth for your personal data.
- Compute API (AI inference, telemetry) — a stateless FastAPI service that handles AI requests. It does not retain conversation contents after a response is returned, except as forwarded to the WordPress Memory Event store.
- Your browser (when you use the local-model bridge) — if you have configured a local model (Ollama / LM Studio / llama.cpp), your prompts and responses flow browser ↔ your localhost only for those calls. Our server sees the same prompt and response strings it would have seen using the cloud, but the model weights and intermediate activations stay on your machine.
4. AI inference — cloud vs. local vs. bridge
By default, MaiiaM features use one of three inference paths:
- Local-bridge (highest priority) — when your browser has connected your local Ollama/LM Studio/llama.cpp to the Platform, we route inference through it. Your prompts are sent over a WebSocket from our API back to your browser, which calls your local model. Our server stores the input prompt and the output text as Memory Events; it does not see the model itself.
- VPS-local — if you have not configured a local bridge, but our server has its own local model running, we use that for inference. Your prompts and responses are processed in memory and stored as Memory Events.
- Cloud (Anthropic Claude) — fallback when neither local option is available. Your prompts are sent to Anthropic's API, which has its own privacy commitments. Anthropic does not train models on API traffic.
Every API response includes inference_metadata.routed_to so you can verify which path served your request.
5. Who can see your data
- You. Always.
- The AsAManThinks team. A small number of operators can access support-related data (account email, recent activity) when you contact us for help. We don't browse content for any other reason.
- Service providers who run necessary infrastructure: our hosting (Hostinger), payment processor (Stripe via WooCommerce when purchases are enabled), and email delivery (transactional only). Each is bound by their own privacy policies and is granted access only to the data necessary for their function.
- Anthropic — only when cloud-mode inference fires. Anthropic processes the prompt+response pair to generate a reply and does not train on it under their API agreement.
- Legal authorities only when compelled by valid legal process. We will tell you if this happens unless legally prohibited.
6. Cookies & local storage
We use:
- Session cookies for authentication. Required for sign-in to work.
- Local storage in your browser for non-essential preferences: your reader theme, last page in each book, music volume, the bridge session ID, etc. You can clear it at any time via your browser's site-data tools.
We do not use cookies for advertising or third-party tracking.
7. Children's privacy
The Platform is intended for users 16 and older. We do not knowingly collect data from children under 16. If you believe a child has registered, please email privacy@asamanthinks.com and we will delete the account.
8. Your rights
You have the right to:
- Access all data we hold about you. Account → Data → Export.
- Correct inaccurate data. Account → Profile.
- Delete your account and all associated content. Account → Delete Account. Deletion completes within 30 days, subject to legal retention.
- Object to specific processing — for example, you can disable Memory Event collection in Account → Privacy.
- Lodge a complaint with your local data protection authority if you believe we are not handling your data correctly.
These rights apply globally. If you are in the EU/UK, they are guaranteed by GDPR. If you are in California, CCPA gives you the same rights plus the right to know whether your data was sold (we don't sell).
9. Data retention
- Account & content: kept until you delete your account, or until 24 months of inactivity (we will email you first).
- Memory Events: kept as long as your account exists, since they make personalization work. Deletable individually or in bulk via Account → Privacy → Memory Events.
- Server logs: 30 days, then automatically rotated.
- Backups: rolling 7-day window. After deletion, your data may persist in backups for up to 7 days before being purged.
10. International transfers
Our primary servers are in the United States. If you are in the EU/UK, your data is transferred to the US under the EU-US Data Privacy Framework / Standard Contractual Clauses. If you use cloud-mode inference, your prompts may also be processed by Anthropic in the US.
11. Security
We use TLS 1.3 for all connections, hash passwords with industry-standard algorithms, and segregate inference traffic from identity / payment systems on separate machines. We are a small team and do not claim a zero-incident track record; if something happens, we will tell you within 72 hours of discovery.
12. Changes to this Policy
We will update this Policy as the Platform evolves out of beta. Material changes will be announced on the marketing site and via email at least 30 days before they take effect.
13. Contact
For privacy-specific questions, requests, or complaints, email privacy@asamanthinks.com. For account or product questions, see our contact page. For terms of service, see our Terms of Service.