Privacy Policy

A plain-language account of the limited data this site processes, why it is needed, how long it is kept and how to reach us about it.

This policy describes how ingramdown.in (“IngramDown”, “we”) handles information when you use the site. It covers only this website — not Instagram, Meta or any other third party. Last updated: November 16, 2026.

Overview

IngramDown is a small, browser-based utility for previewing and saving supported public Instagram media. We designed it to collect as little information as possible: there are no user accounts, no profiling, no advertising trackers and no analytics scripts on the site today. The data described below exists only to run the service, keep it secure and let people who contact us receive a reply.

IP addresses and rate-limit files

Like most servers, we need to know the originating IP address of a request in order to apply rate limits. To avoid keeping raw addresses on disk, the IP is salted and hashed (SHA-256) before it is used as a file key. The rate-limit state lives as small JSON files in a private directory outside the public website folder, with permissions that block direct web access.

  • What is stored: a one-way hash of your IP address together with timestamps of requests, used to count activity inside a rolling 15-minute window (currently a shared budget of 18 requests per IP across the download endpoints).
  • Why: to stop a single client from exhausting the shared server and to keep the tool usable for everyone.
  • Retention: only events inside the current window matter; stale entries age out automatically and are overwritten as time passes. The raw IP is never written to these files.

Server and web logs

The site runs on hosting infrastructure operated by Hostinger. As with virtually any web server, the hosting provider may record standard log lines — IP address, user agent, requested URL, response status and timestamp — for operations, troubleshooting and security. Those logs belong to the hosting layer and are governed by the provider’s own policies as well as this one. Our application additionally writes a small internal error log (severity, message, file name) under a blocked storage folder when something fails, so we can fix bugs. Those application logs contain no message content and no passwords — we never collect passwords at all.

Temporary processing files

When you request a preview or a download, media and metadata are processed in a temporary working folder outside the public website root. These files exist only for the duration of the request: they are streamed to you and deleted when the request finishes. If a request is interrupted, a periodic cleanup removes leftover folders automatically. IngramDown does not operate a permanent media library and does not keep copies of the posts you download.

Honest caveat: “deleted after the request” is a real design goal, not a cryptographic guarantee — a file can exist briefly on the server while a transfer is in flight. We simply do not retain media once the transfer completes or fails.

The only cookie this site sets is a standard PHP session cookie (normally named PHPSESSID). Its single purpose is to hold the cross-site request forgery (CSRF) token that protects forms and API calls.

  • Purpose: CSRF protection only — no personalisation, no tracking.
  • Flags: HttpOnly (not readable by JavaScript), SameSite=Lax, Secure when the site is served over HTTPS.
  • Lifetime: session cookie — it expires when you close your browser (server-side session data expires shortly after).

See the Cookie Policy for the full list of cookies and third-party requests.

Contact and report forms

If you use the contact form or the abuse report form, we process what you choose to send:

  • Contact form: name, email address, subject and message (up to 5000 characters).
  • Abuse report form: optional name, required email address, optional URL of the content concerned (up to 500 characters), a reason category and your description (up to 4000 characters).
  • Purpose: nothing other than reading your message and replying to you, or acting on a report.
  • Retention: kept only as long as needed to handle your message and resolve any related complaint — typically a reasonable period after the matter is closed, then deleted. We do not add you to any mailing list.
  • Spam protection: submissions are checked with a CSRF token and a hidden honeypot field; rejected submissions are not delivered.

Never send us passwords, Instagram login details or session cookies. We will not ask for them.

No user accounts

IngramDown has no registration, no login and no profile system. We do not know who you are when you download a public post, and we do not try to find out. Any identity information exists only if you voluntarily include it in a message you send us.

Third-party requests and hosting

  • Instagram CDN thumbnails. Preview images are loaded by your browser directly from Instagram/Meta content delivery networks (for example cdninstagram.com or fbcdn.net). That is a request from your browser to a third party, which can see your IP address and standard request headers under its own privacy policy. Our scripts set referrerpolicy="no-referrer" on those images to avoid leaking page context.
  • Google Fonts. The site stylesheet loads the Inter font from fonts.googleapis.com and fonts.gstatic.com. Those requests go to Google; the providers may set or read cookies on that request under their policies.
  • Hosting. As noted above, infrastructure is provided by Hostinger, which processes request data at the server level.
  • No social embeds or pixel trackers are installed on this site.

Advertising and analytics

Advertising: advertising is currently disabled. No ad scripts run and no ad cookies are set. If advertising (for example Google AdSense) is enabled in the future, that would introduce third-party requests and cookies — we would update this policy, the Cookie Policy and the Advertising Policy, and obtain consent where the law requires it before any such cookies are used.

Analytics: no analytics tool (Google Analytics or otherwise) is installed. We do not receive visitor counts, heatmaps or behavioural profiles from this site. Aggregate, server-level figures such as response codes may exist in hosting logs, which are not used to profile individuals.

Your rights

Depending on where you live, you may have rights over personal data we hold about you — for example the right to request access, correction or deletion of information you sent through a form, or to object to certain processing. We do not hold account data to delete, and rate-limit hashes cannot realistically be tied back to you without the original IP. If you sent us a message, write to us and tell us what you would like removed; we will act on valid requests within a reasonable time and as required by applicable law.

How to reach us

Questions about this policy or your data:

creatorbabadk@gmail.com

or use the contact form. Related documents: Cookie Policy, Terms of Service, Disclaimer and Copyright & DMCA.

This policy is written for this site only. Instagram, Meta, Hostinger, Google and any future ad network are independent controllers of their own data — review their policies separately. We will update this page if our practices change.