Digital Estate
Digital-asset and password-inheritance planning: a checklist, access framework, and glossary
Brand-neutral VPN and privacy-tool concept reference: what a VPN does and doesn't do, plus a category comparison and glossary
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
vpn_mechanismprotection_checklistvpn_mechanismcategory_comparisonprivacy_glossaryevaluation_frameworkPrivacyBasics is a fully local, brand-neutral VPN and privacy-tool concept reference — general educational reference only, never a recommendation, endorsement, or sale of any specific product. vpn_mechanism explains what a VPN actually encrypts and hides, and is explicit about its limits: no absolute anonymity, no protection from phishing/malware/weak passwords/browser fingerprinting/logged-in tracking, since the VPN provider itself can see your traffic. category_comparison gives a genuine technical comparison of VPN, Tor, privacy-focused browsers, ad/tracker blockers, and encrypted messaging: what each protects, its trust model, relative performance, and limits. protection_checklist returns two non-overlapping lists of what a VPN protects against and what it does not. privacy_glossary defines core terms: no-logs policy, kill switch, split tunneling, DNS leak, WebRTC leak, end-to-end encryption vs. encryption-in-transit, exit node, threat model, and more. evaluation_framework is a neutral checklist of questions to ask before choosing any privacy tool — jurisdiction, logging-policy specificity, independent audits, open-source status, and funding model. Every response carries a disclaimer field. Keyless; fully local; zero upstream calls; nothing stored.
Sources: Hand-curated technical reference on VPN, Tor, and privacy-tool concepts, using published protocol and standards documentation; fully local, zero upstream calls
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
5 tools, grouped by job. Every one is read-only or compute-only.
https://privacybasics.connectorbay.com/mcpDigital-asset and password-inheritance planning: a checklist, access framework, and glossary
The 5-stage anatomy of a tech-support scam, red flags, and a recovery checklist
Password-reuse risk score, credential-stuffing explainer, and a password-manager migration guide
Phishing red-flags checklist, URL-inspection guide, and a real lookalike-domain detector
Scam-call pattern recognition — common tactics, a verification method, and a red-flags risk score
Digital-wallet security checklist, scam patterns, a lost-phone plan, and a real self-assessment score
PrivacyBasics is a VPN and privacy-tool concept reference for learning and general technical understanding.
It is never a recommendation, endorsement, or sale of any specific product, brand, or service, and never a
guarantee of privacy, anonymity, or security. It describes technologies and concepts only — no specific
commercial VPN product, browser, or company is ever named or endorsed. Every tool response carries a
disclaimer field restating this.
The questions that come up before choosing (or trusting) a privacy tool — what a VPN actually encrypts and hides, what it does not protect against, how it really compares to Tor or an ad blocker, and what to ask a provider before trusting it — answered with accurate, honest technical reference and no upstream calls or data about the user stored.
vpn_mechanism explains what a VPN actually does — encrypts traffic between your device and the VPN server
and hides your IP from the destination — and is explicit about its limits: it does not make you anonymous in
any absolute sense, does not encrypt traffic end-to-end to the destination, and does not protect against
phishing, malware, weak passwords, browser fingerprinting, or logged-in account tracking, because the VPN
provider itself sits in the middle of every connection. category_comparison gives a genuine technical
comparison of VPN, Tor, privacy-focused browsers, ad/tracker blockers, and encrypted messaging — what each
protects, its trust model (a VPN needs one trusted operator; Tor splits trust across independent relays),
relative performance, and what it does not provide. protection_checklist returns two non-overlapping lists:
what a VPN protects against and what it does not. privacy_glossary defines core terms: no-logs policy, kill
switch, split tunneling, DNS leak, WebRTC leak, end-to-end encryption vs. encryption-in-transit, and more.
evaluation_framework is a neutral checklist of questions to ask before choosing any privacy tool —
jurisdiction, logging-policy specificity, independent audits, open-source status, and funding model.
Not a shopping guide, not a VPN or privacy-product seller or broker, and not a compatibility or trust database for any specific provider. It does not know any specific vendor's current logging practices, audit status, or jurisdiction — those change and must be verified directly with the provider and independent auditors. It is not a substitute for defining your own threat model: the right combination of tools depends entirely on who you're protecting your data from and what they're capable of.
Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What PrivacyBasics is. PrivacyBasics is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a brand-neutral VPN/privacy-tool concept reference, a technical category comparison, a protects/does-not-protect checklist, a glossary, and a provider-evaluation framework. PrivacyBasics is general educational reference only and is never a product recommendation, endorsement, or sale. It does not itself provide, resell, or broker any VPN or other privacy service. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.
What we receive. The arguments of each tool call — for example a list of category names or a glossary term — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.
Everything is answered locally and nothing is stored. PrivacyBasics makes zero upstream/network calls: every response is drawn from bundled, hand-curated reference data. No request is forwarded to any third party, and no query is logged in request bodies, recorded, or used to train anything.
What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. We do not know which privacy tools, VPNs, or browsers you use or are considering. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.
Sub-processors. None — the entire reference dataset is bundled with the server and served locally. Hosting: Vercel (United States regions).
Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.
Children. PrivacyBasics is a general-audience service operated by the adult using the assistant.
Changes. We will post changes here with a new effective date.
Effective 28 September 2026. These terms govern use of the PrivacyBasics connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://privacybasics.connectorbay.com/mcphttps://privacybasics.connectorbay.com/openapi.jsonWhen you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. PrivacyBasics never asks for them.