The tools collect nothing. There is no account, no analytics, no tracking pixel, no ad network and no third-party script. Two small values may be saved in your own browser’s local storage — your colour theme and, if you use it, your grid planner arrangement — and neither leaves your device. The web server keeps ordinary request logs, described honestly below. The one place data is collected is the contact form, and there is a section on exactly what it stores.
Last updated: 29 July 2026.
What the tools collect: nothing
This is not a promise about how carefully we handle your data; it is a statement about architecture. The tools have no backend — no application server, no database table, no API endpoint that accepts what you type. Each tool is a JavaScript module your browser downloads once and then runs locally, in the same sandbox as every other tab you have open.
Nothing you enter is transmitted
Open your browser’s developer tools, switch to the Network tab, load a tool, clear the request list, then use it. You will see no further requests — no POST, no fetch, no beacon. That is the whole privacy story, confirmable in under two minutes.
The calculators
Engagement rate, influencer rates, follower growth and posting times are pure arithmetic. Your follower count, likes, comments, reach, prices and time zones stay in the input boxes. Close or reload the tab and they are gone. Nothing is stored, queued or sent to us.
The text tools
Captions, bios and hashtag sets are transformed character by character inside the textarea you typed them into. Text you paste — including an unpublished draft — is processed in the page and never uploaded. There is no autosave, no draft sync and no server-side spell or grammar service reading over your shoulder.
The image tools
When you choose or drag a file into the carousel splitter, size checker, safe zone checker or grid planner, the browser creates a local object URL pointing at the file already on your disk. The tool draws that image onto a canvas element in your own memory, crops or measures it there, and hands the result back as a blob your browser downloads to you. The object URL is released afterwards. The file never becomes an upload, because there is no upload endpoint on this domain to receive one.
Local storage: six keys, and this is the complete list
Local storage belongs to your browser, on your machine. It is not a cookie: it is never attached to a request, so it is not sent to a server when you load a page. Several tools use it to remember your work between visits. Here is every key this site writes, what goes in it, and which tool writes it. If you find one that is not on this list, that is a bug and we want to know.
| Key | Written by | What it holds |
|---|---|---|
sg-theme |
Every page | The single word light or dark, written when you press the theme toggle, so the site does not flash the wrong colours on your next visit. |
stealthgram.er-history.v1 |
Engagement Rate Calculator | Calculations you chose to save: the follower and interaction figures you typed, the resulting rate, and a date. Capped at 50 entries; the oldest drop off. |
stealthgram.fonts.v1 |
Font Generator | Which text styles you starred as favourites. Style names only — not the text you typed. |
stealthgram.captions.v1 |
Caption Length Counter | Caption drafts you chose to save, capped at 20. This one holds text you wrote, so it is the key most worth knowing about. |
sg-hashtag-sets |
Hashtag Set Builder | Hashtag sets you named and saved, capped at 40. |
stealthgram.grid-planner.v1 |
Grid Planner | Your tile order, any notes and planned dates you added, and a downscaled 400px JPEG thumbnail of each image encoded as text, so the planner can redraw the grid after a reload. Capped at roughly four megabytes; above that the planner says so on screen and stores nothing rather than failing silently. |
Every one of these is written only if you actively use that feature — save a calculation, star a style, save a draft or a set, build a grid. None of the calculators remember your last inputs unless you explicitly save them, and no tool writes anything on page load except the theme preference.
What this does and does not mean
These values live in your browser and are never transmitted. Our code contains no call that would send them anywhere, and there is no server-side copy, so we have no way of seeing what is in them. What we cannot claim is that they are inaccessible to us as code: JavaScript served from this domain can read this domain’s local storage, which is exactly how the grid planner redraws your grid. The honest statement is that nothing here transmits it, not that nothing here can read it.
The practical consequences are worth being clear about, because they are trade-offs rather than pure benefits:
- Nothing syncs. A grid plan saved on your laptop is not on your phone. A caption draft in Chrome is not in Safari. There is no account to sync it to, by design.
- Clearing site data deletes it permanently. There is no backup and no recovery, because we never had a copy. Where a tool produces something you would hate to lose, it offers a CSV, text or ZIP export — use it.
- Private or incognito windows discard everything on close, and some browsers refuse local storage there entirely. The tools detect that and say so rather than silently losing your work.
To delete all of it: in your browser’s settings, clear site data or cookies for stealthgram.in.net. Individual tools also offer their own clear or delete controls — the engagement rate history has a “clear history” button, and saved captions, hashtag sets and grid tiles can each be deleted from within the tool.
Server logs
We will not pretend the internet works without this. The site is served by nginx, which like every web server writes a line per request to an access log and an error log on the server itself. A log line holds the requesting IP address, the date and time, the URL, the HTTP status and response size, the referring page if the browser sent one, and your browser’s user agent string.
That is standard operational data: it is how anyone notices a page erroring, an asset missing, or a bot hammering the server. It is not linked to any account, because there are no visitor accounts, and it contains nothing you typed into a tool, because none of that is ever sent. We do not build profiles from it, sell it, or feed it into any advertising system.
Analytics: there is none
There is no Google Analytics here. No gtag, no Tag Manager container, no dataLayer, no Meta pixel, no Plausible, Fathom, Matomo or Hotjar, no session recorder, no heatmap, no A/B testing script. The WordPress installation behind the site runs no conventional plugins at all — only two must-use components, an autoloader and the site’s own code for page titles, meta descriptions and structured data. Neither tracks anybody.
The practical consequence is that we do not know how many people visit or which tools are popular, beyond what a raw server log would show if someone read it. That is the cost of being able to make this page’s claim without qualification.
Cookies
Ordinary visitors receive no cookies from this site. WordPress itself sets cookies in two situations: when someone logs in to the administration area, and when someone submits a comment. Comments are disabled site-wide — the theme switches them off for every post and page, so no comment form is rendered and no comment cookie can be set. Login cookies apply only to whoever administers the site, not to readers. There is no consent banner because there is nothing to consent to; if you ever see one on this domain, it is not ours.
Third parties
No third party is involved in serving you a page. The two typefaces are self-hosted: the .woff2 files sit in the theme’s own fonts directory, referenced by relative path from the site’s stylesheet, so no font CDN ever sees your IP address. There are no external scripts, no ad network, no embedded video players, no social widgets, no comment platform, no chat bubble and no CAPTCHA service. The tool modules import nothing from outside this domain.
Children
This site is aimed at people who post on Instagram, which has its own minimum age requirement. We do not knowingly collect personal information from anyone of any age, because the tools collect none at all — there is no sign-up and no profile. The only form on the site is the contact form, which collects only what someone deliberately types into it. For a parent or guardian, that means there is nothing here to ask us to delete.
The contact form: the one thing that is collected
Everything above describes the tools, and remains true of them. The contact form is the single exception on this site, and it deserves to be described exactly rather than buried.
If you submit it, four things you typed are written to this site’s database: the name you gave, the email address you gave, the topic and subject line you chose, and the text of your message. Two things you did not type are stored alongside them: the timestamp and your browser’s user-agent string. Your IP address is not stored with the message; it is used only to hold a one-minute rate limit in temporary storage, which expires on its own.
That record is kept because it is the message — this server has no mail server attached and the domain has no MX records, so an email notification is attempted but cannot be relied on. The stored copy is what a person actually reads. Records are kept only as long as they are useful for answering, and can be deleted on request.
The form loads no third-party script: no CAPTCHA, no reCAPTCHA, no anti-spam service, no analytics. Spam is filtered with a hidden field and a timing check evaluated on our own server, so submitting the form still tells no other company that you were here.
Requests about your data
Privacy law gives people rights to access, correct, export and delete the personal data an operator holds about them. For the tools, the answer to any such request is that none is held: no account record, no email list, no analytics profile, no stored copy of anything you entered into a tool. The one exception is a contact form message, if you have sent one. The only visitor-linked data that exists is the server log described above, kept for operational reasons and not indexed by person.
Requests can be made through the contact form. You can also write to privacy@stealthgram.in.net, or security@stealthgram.in.net for a security report. The form is still the more dependable of the two, because it works without email at all — submissions are stored on the server rather than sent on. To have a message you previously sent erased, say so and include the email address you used, so the right record can be found. There is no automated system on the other end, so allow several days.
To ask anything about your data, or about what this site stores in your browser, write to privacy@stealthgram.in.net. For security reports specifically, use security@stealthgram.in.net. There is also a contact form, which stores your message rather than relying on mail delivery.
Changes to this policy
If the site changes in a way that affects any of this — an analytics tool, an embedded third party, a new local storage key, a change to what the contact form stores — this page will be edited to describe it and the date at the top updated. Better an accurate, unglamorous policy than a polished one describing a site we are not running.
Not affiliated with Instagram or Meta
StealthGram is an independent project and is not affiliated with, endorsed by or connected to Instagram or Meta Platforms, Inc. We never connect to, automate or access any Instagram account, and we never ask for your login. Nothing on this page describes how Instagram itself handles your data — for that, read Instagram’s own privacy policy.