Privacy Policy — Instagram MD

In plain language

All your data stays on your device — no servers, no accounts, no tracking.
Your Groq API key is encrypted on-device and never sent anywhere except directly to Groq under your own account.
Instagram post content (captions, audio, images) is sent only to Groq’s API to generate your markdown notes — it is not stored by us.
We collect nothing. We receive nothing. We have no backend.

1. What Instagram MD does

Instagram MD is a Chrome extension that converts your Instagram saved posts into Obsidian-ready markdown notes. It reads post captions, transcribes audio from Reels, and describes images by calling the Groq AI API using the API key you provide.

The extension has no backend server. The developer (Arnaldo Koo) does not operate any service that receives, stores, or processes your data.

2. Data stored on your device

The following is stored in your browser via chrome.storage.local — it never leaves your device except as described in section 3.

What	Why	Where
Groq API key (AES-GCM encrypted)	Sent to Groq on your behalf when you click Process	Device only
Post queue (URLs, author handles, captions)	Holds posts awaiting processing between sessions	Device only
Processed markdown notes	Shown in the preview and available to download	Device only
Settings (batch size, AI model, theme)	Restores your preferences between sessions	Device only

        Your Groq API key is encrypted with AES-GCM using a device-specific non-extractable key generated by the Web Crypto API. The raw key is never written to disk and cannot be read — even by the extension itself — without the device key.
      

3. Data sent to the Groq API

When you click Process, the extension sends Instagram post content to api.groq.com using your own Groq API key. The following content may be included depending on the post type:

Content	Sent to	Purpose
Post captions and author handles	Groq chat API	Categorization and markdown note generation
Reel audio (fetched from Instagram CDN)	Groq Whisper API	Transcription
Image descriptions (generated locally via Groq vision)	Groq vision API	OCR and image understanding for markdown notes

This data is sent under your Groq account and is subject to Groq’s Privacy Policy. The developer of Instagram MD has no access to any data passing through Groq’s API.

4. What we do not do

We do not:

Collect, transmit, or store any user data on our own servers
Sell, share, or transfer user data to any third party (other than Groq as described above)
Use your data for advertising or profiling purposes
Include any analytics, telemetry, or crash-reporting libraries
Access your Instagram account credentials

5. Chrome permissions used

Permission	Why it is needed
`storage`	Saves your post queue, processed notes, encrypted API key, and preferences locally
`alarms`	Keeps the service worker alive during multi-post AI processing batches
`offscreen`	Decodes Reel audio and encodes it as WAV before sending to Groq Whisper
`tabCapture`	Fallback audio capture when Instagram CDN audio URLs have expired
`scripting`	Injects the content script into Instagram to collect saved-post metadata during bulk import
instagram.com host permission	Required for the content script to read saved-posts page and detect newly saved posts
api.groq.com host permission	Required to call Groq’s API for transcription, vision, and categorization
cdninstagram.com / fbcdn.net host permissions	Required to fetch Reel audio directly from Instagram’s CDN for transcription

6. Data retention and deletion

All data is stored in your browser’s local storage. You can delete it at any time by clicking Settings → Clear all data in the extension, or by removing the extension entirely from Chrome (which deletes all associated storage).

The developer has no copy of your data and therefore cannot delete it on your behalf — you are always in full control.

7. Changes to this policy

If this policy changes materially, the “Last updated” date at the top of this page will be revised. Continued use of the extension after a change constitutes acceptance of the updated policy.

8. Contact

Questions about this privacy policy? Open an issue on GitHub or email arnaldokoo@gmail.com.