NOA CRM Privacy Notice
Effective date: 12 October 2026
Controller / operator: NOA SHADE
1. About NOA CRM
NOA CRM is a locally run customer-relationship application for managing projects, social accounts, fan profiles, notes, interactions, follow-ups, content catalog details, and offers. In this version, the application server and the selected SQLite database run on the operator’s Mac or a storage device connected to that Mac. The application does not use a NOA CRM hosted cloud database.
2. Instagram data
When the operator connects a professional Instagram account and opens the Instagram inbox, NOA CRM requests the connected account’s basic profile information and conversation data from Meta. This can include the account identifier, username and account type; conversation identifiers and timestamps; participant identifiers and usernames; and message text and timestamps returned by Instagram.
The current version fetches conversation lists and message history from Meta when requested and displays the response in the local CRM interface. It does not write Instagram conversation history to the CRM SQLite database. The connected account’s access token and account identifier are stored in the macOS Keychain. The operator can disconnect Instagram in NOA CRM settings, which removes the stored access token and connected account identifier.
3. Other information entered into the CRM
The operator may enter or create CRM records such as project and account details, fan usernames and profile links, notes, interaction records, follow-ups, offer text and outcomes, and content names, tags, descriptions, and local file paths. These records are saved in the SQLite database selected by the operator and remain under the operator’s control on that Mac or connected storage device.
If the operator connects Telegram, NOA CRM stores the Telegram session and connection credentials in the macOS Keychain. It saves explicit Telegram contact links and hidden-contact state in the local SQLite database. Telegram dialogue history is fetched when a conversation is opened and is not written to that database by the current version.
4. Where data is processed and shared
For Instagram features, NOA CRM communicates with Meta’s Instagram API to authorize the account and retrieve the requested profile and conversation data. The local CRM server relays the response to the operator’s browser on the same Mac. The operator’s SQLite database is not sent to Meta by these features.
During Instagram connection only, the operator may enable a temporary Cloudflare Quick Tunnel so Meta can reach the OAuth callback on the Mac. The callback carries the one-time authorization response to the local application. The tunnel is intended for this callback and is stopped by the operator or when the CRM closes. NOA CRM does not send Instagram message history through that callback.
If Telegram is enabled, the local application communicates with Telegram to authenticate the operator’s account and retrieve or send messages at the operator’s request. Meta and Telegram process data under their own terms and privacy notices. NOA CRM does not configure a hosted CRM service or analytics provider in this local version.
5. Retention and deletion
Instagram conversation data is fetched on demand and is not persistently stored in the CRM database by the current version. Instagram credentials remain in the macOS Keychain until the operator disconnects the account. Telegram session credentials can likewise be removed by disconnecting Telegram in NOA CRM settings.
CRM records entered by the operator remain in the selected local database until the operator removes them or removes that database. To ask the operator to locate or delete information associated with an Instagram or Telegram account, contact hey.noashade@gmail.com. The operator will review the request and, where applicable, remove locally held records and credentials. NOA CRM cannot delete data held by Meta or Telegram; requests concerning their services must also be made to those providers.
6. Security
The application runs locally on the operator’s Mac. Instagram and Telegram connection secrets are stored in the macOS Keychain rather than in the SQLite database. The operator is responsible for securing the Mac, its user account, backups, and any connected storage device. No claim is made here that the SQLite database is encrypted.
7. Changes and contact
This notice will be updated when the application’s data practices change. For privacy questions or data requests, contact hey.noashade@gmail.com.
Notitia Privatitatis NOA CRM — Latine iocose
Dies effectivus: 12 Octobris 2026.
Curator datorum: NOA SHADE.
Haec versio Latina iocosa est; textus Anglicus supra vim officialem habet.
1. De NOA CRM
NOA CRM est instrumentum locale ad opera, rationes sociales, perfiles fanorum, notas, commercia colloquiorum, res futuras, catalogum rerum creatarum et oblationes ordinandas. In hac versione, ministerium et basis SQLite in Mac curatoris aut in disco ei coniuncto habitant. Nubes CRM? Nulla est; Mac ipse est arca thesauri.
2. De Instagram
Si curator rationem Instagram professionalem coniungit et epistulas aperit, NOA CRM a Meta petit notitias fundamentales et colloquia. Possunt includi numerus rationis, nomen usoris, genus rationis, numeri colloquiorum, tempora, participes, nomina usorum et verba epistularum quae API reddit.
Index colloquiorum et historia epistularum tantum rogatu curatoris petuntur atque in interfacie locali ostenduntur. Historia Instagram in SQLite non scribitur. Tessera accessus et numerus rationis in Clavibus macOS servantur. Curator Instagram disiungere potest; tunc tessera et numerus rationis removentur. Clavis in arca, epistula in fenestra.
3. De ceteris rebus CRM
Curator in CRM scribere potest de operibus, rationibus, fanis, notis, colloquiis, rebus futuris, oblationibus, titulis, notis indicantibus et viis ad files locales. Haec in basi SQLite a curatore electa servantur atque in eius Mac vel disco manent.
Si Telegram coniungitur, sessio et documenta accessus in Clavibus macOS servantur. Nexus curatoris inter contactus Telegram et fanos, itemque notae contactuum absconditorum, in SQLite locali manent. Historia colloquii aperti tum petitur, sed in SQLite non reponitur. Memoria brevis, basis quieta.
4. Quomodo data moventur
Pro Instagram, NOA CRM cum API Meta loquitur ut rationem auctorizet et notitias petitas accipiat. Ministerium locale responsum ad navigatorem eiusdem Mac mittit. Basis SQLite ad Meta non mittitur. Mac epistulas foras non portat.
Ad solam coniunctionem Instagram curator interdum cuniculum temporarium Cloudflare Quick Tunnel aperire potest, ut Meta ad responsum OAuth in Mac perveniat. Per cuniculum responsum singulare auctoritatis transit; historia epistularum non transit. Curator cuniculum claudit aut id cum CRM clauditur. Pons parvus, non via imperialis.
Si Telegram adhibetur, applicatio cum Telegram communicat ut rationem curatoris comprobet et epistulas, eo iubente, petat aut mittat. Meta et Telegram sua cuique regula et notitia privatitatis habent. Hic CRM nec nubem suam nec analytica externa constituit; calculator tamen multum scit, si nimis multa ei narras.
5. De memoria et deletione
Colloquia Instagram rogatu petuntur et in hac versione in basi CRM non diu servantur. Tessera Instagram in Clavibus macOS manet donec curator rationem disiungat. Documenta sessionis Telegram eodem modo removentur cum Telegram in CRM disiungitur.
Notitia CRM a curatore scripta in SQLite manet donec curator eam vel ipsam basim removeat. Si vis ut curator notitias rationi Instagram vel Telegram coniunctas inveniat aut removeat, scribe ad hey.noashade@gmail.com. Curator rogatum examinat et, si licet, records locales et documenta accessus removet. NOA CRM data apud Meta vel Telegram delere non potest; illis quoque scribendum est. Tabula deletur, sed Internet memoriam longiorem habet.
6. De securitate
Applicatio in Mac curatoris currit. Secreta Instagram et Telegram in Clavibus macOS, non in SQLite, servantur. Curator Mac, rationem suam, exemplaria reservata et discos coniunctos custodit. Hoc nuntium non promittit basim SQLite esse encryptam; arca lignea non fit ferrea quia nomen eius Latinum est.
7. Mutationes et contactus
Haec notitia mutabitur si consuetudines datorum mutantur. De privatitate aut petitionibus datorum scribe ad hey.noashade@gmail.com. Nuntius ad curatoris in arca electronica perveniet, non ad augurem Romanum.