Intraconnected | Last updated October 25, 2026
Intraconnected is a personal app for growing ideas on a tree, operated by an individual (Hunter Africk), not a company. Hunter Africk is the "controller" of your personal data (the person who decides how it is used), and "we" in this policy means him. We take privacy seriously: the text of your ideas is encrypted on your device before it leaves it. This is not end-to-end encryption; see "How Your Data Is Protected" below. The one exception is a branch or a single idea you choose to share as a link (see "Shared Links").
Email address. Used to create and identify your account, and to send billing receipts through Stripe if you upgrade. We never sell it or use it for marketing.
Your ideas. The text of each idea (its name, notes, links, and checklist items) is encrypted on your device before being stored. The structure of your tree is stored as plain data so that sync and the app can work: which ideas sit under which, whether each is an idea, note or checklist, their priorities, whether an idea is censored, whether a checklist item is ticked, and when each idea was created and last changed. Idea IDs reflect their creation time, and ciphertext lengths are visible. Because you decide what to write, your ideas may contain any kind of information about you or others, including sensitive information. We do not use it for any purpose other than providing the service to you.
Sync and app settings. A random identifier for each device you sign in on, so your devices know when to sync with each other, and a few settings such as whether you've seen the welcome tips and which patch notes you've read.
Usage counts, paid accounts only. Once a day we count the ideas in each paid account, without reading them, and keep the latest count. If an account's count is unusually high or grows suddenly, we record a flag with the account's email so we can look at it, and post a notice containing only the counts (no account details) to our public issue tracker on GitHub. Nothing is blocked or changed as a result, and no decision about you is made by automated means.
Rate-limit counters. To limit abuse, we keep short-lived counters of how often an account calls certain features (for example recovery, link previews or reports); they are cleaned up automatically. If a sign-in upgrade step fails, we record your account ID so we can follow up.
Network address, when signed out. To limit abuse of our problem-report form, which also opens from sign-in errors, we store a keyed one-way hash of your IP address. We cannot reverse it to an address, and it is deleted automatically a few days after your last report.
Hosting logs. Our hosting and authentication providers (Netlify and Google) necessarily receive your IP address and basic request details whenever your device contacts the service, and they may keep ordinary server logs of them under their own policies (see Third-Party Services).
Payment information, if you upgrade. If you choose a paid plan, your card details are collected and processed directly by Stripe, our payment processor, we never see or store your card number. Stripe shares back with us only what's needed to run your account: your plan, purchase date, subscription status, and the Stripe customer and subscription identifiers that link your account to your payments. If you buy a plan in the iPhone, iPad or Android app, Apple or Google processes the payment and we never see your payment details; we receive the purchase record (what you bought, when, whether it renews, and store transaction identifiers) through RevenueCat (see Third-Party Services).
Nothing else. We do not use analytics, advertising trackers, or cookies of our own. We do not sell or share any of the above for marketing or advertising purposes, and we have not done so in the past 12 months.
We use your data only to run the service you asked for: to create and secure your account, store and sync your ideas, process payments and keep your plan accurate, recover your account, answer problem reports, prevent abuse and keep the service running and secure, and meet legal obligations.
If you are in the European Economic Area, the United Kingdom or a similar region, the legal bases for this are: performing our contract with you (account, sync, billing, recovery); our legitimate interests in keeping the service secure, preventing abuse and keeping costs sustainable (the abuse-prevention hash, usage counts and logs), which we balance against your rights; compliance with legal obligations (tax and accounting records, responding to valid legal requests); and, where we ask for it, your consent, which you can withdraw at any time.
Idea text is encrypted on your device (AES-256-GCM) before it is sent to our servers, and connections use HTTPS/TLS. Your password is not stored. This is not end-to-end encryption: the service keeps a recovery copy of your encryption key, encrypted with a public key whose private counterpart is held in Google Cloud KMS. Our server asks KMS to unlock it only for a signed-in request from your account made within 10 minutes of signing in, and checks that the key belongs to that account. Because we operate that server and the KMS key, we are technically able to decrypt your ordinary ideas, and we use this only to restore your access at your request or when the law requires it. Each successful recovery through our server is recorded in a record you can read and shown to you in the app, and Google may log the KMS operation in its own audit logs. These logs help detect use; they do not prevent misuse and are not guaranteed to be tamper-proof. The tree's structure, idea IDs, timestamps, priorities, checklist state, which ideas are pinned, and ciphertext lengths are not encrypted. Reminder and repeat schedules are encrypted with the rest of the idea, and reminders are timed on your device, not by our servers. If you turn on reminder notifications, they are created on your device and are not sent through our servers. Unless you choose generic text, a notification shows the idea title (never a censored idea, and vault notes have no reminders): it is held in plain text in your device's queue of scheduled notifications and notification history, can appear on your lock screen, and may be mirrored by your phone or browser to other devices such as a watch. A decrypted copy of your ideas is cached on your device, and scripts or browser extensions running in the page may be able to use your key while you are signed in. Links are encrypted in storage, but a link you save on an idea is sent to our server in plain text to build its preview (see Third-Party Services).
Vault notes have a second layer of encryption with a key protected by your vault passphrase and a recovery code that only you receive. We cannot read or recover them: if you lose both, no one can open them.
No system is perfectly secure. If a breach affects your personal data in a way that the law requires us to report, we will notify you and the relevant authorities as required, without undue delay.
We share personal data only with the service providers below, who process it to run the service, and in the situations described under Legal Requests and Business Transfers. We do not sell your personal data.
Intraconnected uses Netlify to host the website and run the server functions that handle billing, account deletion and reports. Every request to the service passes through Netlify. Netlify is subject to Netlify's Privacy Policy.
Intraconnected uses Firebase (Google LLC) for authentication and encrypted data storage. Firebase is subject to Google's Privacy Policy. Your email address is handled by Firebase Authentication. Your encrypted idea data is stored in Firebase Firestore.
Google Cloud KMS holds the private recovery key. It receives the encrypted recovery copy of your key (not your ideas) when a recovery is requested. If Data Access audit logging is enabled, Google records key-decryption operations in Cloud Audit Logs; our service also records successful recoveries so the app can notify you.
If you upgrade to a paid plan, we use Stripe to process your payment. Stripe is subject to Stripe's Privacy Policy. Your card details go directly to Stripe, we never see or store them. The email address on your account is also sent to Stripe, where it is attached to your customer record and used for receipts and payment notices, and it is updated there if you change your email. Stripe also uses cookies and device information of its own for fraud prevention while checkout is open; that's Stripe's processing, not ours, and is covered by their policy above.
Purchases in the iPhone, iPad and Android apps are processed by Apple (App Store) or Google (Google Play) under their own privacy policies. To keep track of those purchases we use RevenueCat, which receives your account's user ID (not your email or your ideas) and the store's purchase records for it, and tells our server what plan you have. Its in-app library also sends basic information about your device and app version. RevenueCat is subject to RevenueCat's Privacy Policy. When you delete your account, we ask RevenueCat to delete its record of you; Apple and Google keep their own purchase records.
The website and app load their fonts from Google Fonts, so your device requests them from Google's servers, which receive your IP address and browser details as part of that request. Google Fonts is subject to Google's Privacy Policy.
The Windows desktop app is published on GitHub. Downloading it, and the app's checks for and downloads of updates, are requests to GitHub's servers, which receive your IP address and basic request details. No account or idea data is sent. GitHub is subject to GitHub's Privacy Statement.
Link previews. To show a thumbnail and title for a link you save on an idea, the app sends that link, in plain text, to our server, which loads the page from our hosting provider's servers and returns a small screenshot and the page title. This includes links on censored ideas. Links on vault notes are never sent. The page you link to sees a request from our provider, not from you. Because the link leaves your device unencrypted for this, do not save a link that is itself a secret (for example a private share link that works for anyone who has it). The whole address, including anything after a "?", is requested from the linked site. We do not store the link or the preview on our servers, but our hosting provider's request logs may record the request. The result is cached in your browser and removed when you sign out. The server only fetches public web addresses (http or https) and refuses private or internal ones.
Intraconnected is not directed at children under 13, and you must be at least 13 to create an account (or older, if your country sets a higher age for entering a contract or consenting to data processing, up to 16). We do not knowingly collect personal data from anyone under the required age. If you believe a child has created an account, email us and we will delete it.
We operate from the United States, and our providers process data in the United States and other countries. If you use the service from the EEA, the UK or Switzerland, your data is therefore transferred outside your region. Where required, those transfers rely on the safeguards our providers offer, which may include the EU-U.S. Data Privacy Framework or Standard Contractual Clauses depending on the provider; each provider's own policy states what it uses. You can ask us for details using the contact address below.
If you share a branch of your ideas as a link, the text of that branch (idea names, note text, checklist items and web links) is copied to our servers as plain text, not encrypted with your key, so that anyone with the link can read it without an account. We can read it too. Vault notes are never included and censored ideas are left out. We store a title, the idea count, when it was made, when it expires, and your account ID so you can list and take down your links; the account ID is never shown to people who open a link. Link previews on other sites show the title and the number of ideas, not note text. A link is kept until you take it down, it expires (Free accounts: 30 days), or you delete your account. Opening a link does not require an account; we rate-limit readers by a hash of their IP address, the same as for problem reports.
If you share a single idea, checklist or note, its name, note text or checklist items are stored the same way (plain text, readable by us) for 7 days, then the link ends. Link previews of a single idea show a picture of the idea itself, drawn from that text, so the text can appear in the message in the app you send it to. Vault notes cannot be shared.
If you send a problem report, we store what you wrote, the technical details shown in the form (such as the page, your browser and any error text), and any contact address you chose to add. If you were signed in, the report is also linked to your account and email so we can follow up. Reports from verified accounts may also be posted as a public issue on our GitHub project, containing your description and those technical details, but not your account or contact details. Reports about the word filter are not posted publicly. Reports linked to your account are deleted with it; public GitHub issues are not (you can ask us to remove one by email). A report sent while signed out isn't linked to any account, so to have it deleted, email us. Never include idea content, passwords or anything else private in a report.
If you submit a feature request through the app's "Recommend a feature" form, the title and description you write are posted as a public GitHub issue on our project repository so we can track and prioritize it. Do not include personal information in a feature request that you don't want made public. This is unrelated to your idea content, which stays encrypted and private as described above. Deleting your account does not remove public GitHub issues that were already posted; you can ask us to close one by email.
Intraconnected caches a decrypted copy of your ideas in your browser for performance. This cache stays on your device and is not sent anywhere. It's refreshed the next time your device syncs with your account, and it's cleared if you delete your account. Signing out removes your key from the device but does not erase this cache or any changes not yet sent. If you use a shared or public computer, clear your browser's site data when you're done.
To keep you signed in, your device holds your encryption key: in the browser it is held as a non-extractable key in browser storage. Without "Remember me" it is limited to the current tab session; with "Remember me" it can remain available for up to 30 days. After 30 minutes without activity (or 30 days with "Remember me"), you are signed out and the key is removed from the device.
In the mobile app, the encryption key is kept in the device's secure storage (the iOS Keychain or Android Keystore). It is not backed up to the cloud and does not leave the device.
This browser and device storage is strictly necessary for the service to work and to keep your account secure, and is used for nothing else, so we do not show a cookie banner. It is not used to track you across other sites. We do not sell or share personal data, so there is nothing for an opt-out signal such as Global Privacy Control or "Do Not Track" to change. We do not currently read those signals.
You can download a copy of your data at any time from Profile → Data → Export Your Data, on any plan. You can choose Markdown or OPML (your decrypted ideas, for use in other notes, outliner or mind-map apps) or JSON (your decrypted ideas plus basic account information, as a full backup). Vault notes are not included in these exports; you can export them separately from Profile → Vault while your vault is unlocked, and that file is not encrypted.
You can permanently delete your account and all associated data at any time, yourself, from Profile → Danger Zone → Delete Account in the app. No need to contact us. Deleting your account permanently erases your ideas and every copy of your encryption key and recovery audit records from our servers, so that data cannot be recovered afterward, along with any problem reports you sent while signed in and any usage counts and flags. Payment records held by our payment processor (Stripe), such as past charges and the email on them, are kept as the processor and tax rules require. Public GitHub issues are not removed (see Problem Reports and Feature Requests). If you'd rather we do it for you, or you can't access the app, email us at the address below.
Other rights. Depending on where you live (including the EEA, the UK, California and other US states with privacy laws), you may also have the right to: know what personal data we hold about you and get a copy; correct it (you can edit your ideas and your account email in the app); delete it; receive it in a portable format; restrict or object to some uses; withdraw consent you gave; and not be treated differently for using these rights. We do not sell or share personal data and do not use it for targeted advertising or automated decisions about you. We do not use sensitive personal information to infer characteristics about you.
How to use them. Email us at the address below. We may need to confirm the request comes from the account's email address before acting on it. We respond within one month (45 days for US state requests, extendable once where the law allows). You can also ask an authorized agent to make a request for you. Because your idea text is encrypted, a copy of it comes from the in-app export, which decrypts it on your device. If we decline a request, you can appeal by replying to our answer, and if you are still unhappy you can complain to your data protection authority (in the EU, the authority in your country; in the UK, the Information Commissioner's Office) or, in the US, to your state attorney general.
We may disclose personal data if a valid legal process requires it, or if needed to protect people from serious harm or to defend our legal rights. We review each request for validity and disclose only what the law requires, and unless the law forbids it, we will tell you before we do.
If the service is sold, transferred or restructured, your data may move to the new operator. We will tell you before that happens, and the new operator must honor this policy or give you a fresh choice, including the option to export and delete your data.
If we make material changes to this policy, we will update the date at the top of this page and notify you in the app or by email before the change takes effect. We will not use personal data we already hold for a materially different purpose without telling you first and, where the law requires, getting your consent.
Questions or privacy requests? Reach us at support@intraconnected.app. See also our Terms of Service.