Legal
Cookie Policy
Designly sets no cookies. It uses a database inside your browser to hold your work, your images, and your theme preference — on your device, for your benefit, and for nothing else.
Last updated
What we use instead
We use IndexedDB, plus a single localStorage key. It is worth being precise about the difference, because “cookie policy” is the page people look for and neither of those is a cookie.
- A cookie is sent to a server with every single request. That is what makes it useful for tracking you.
- IndexedDB is a database that never leaves your browser. Nothing is transmitted. It is a private drawer on your own device that only this site can open. We use it because it holds real image files, which a cookie could never do.
- localStorage is the same idea, smaller and simpler. One preference lives there.
Everything Designly remembers about you sits in that drawer. Our database is named designly, with two object stores — docs for your text and settings, media for your images:
- IndexedDB · designly → docs → designly:document
- Your Markdown, your format, your template — for the deck and for any card you picked one for — and your call-to-action text. Stored so a refresh, a crash, or a closed tab does not lose your work. Strictly necessary for the tool to be usable.
- IndexedDB · designly → docs → designly:settings
- Your theme and brand kit — name, handle, website, accent colour, badges — so you are not reconfiguring the same things every visit.
- IndexedDB · designly → media
- Any logo, avatar, or slide background you add, held as the image file itself. It never leaves your device, and nothing is recorded about it.
- localStorage · theme
- Light, dark, or system. Read before the first paint so the page does not flash white at you in dark mode.
All four are what the law calls strictly necessary or preference storage. None of them profile you, and none of them are shared with anyone. There is no fifth item, and no hidden one.
Third-party storage
None. Designly embeds no third-party scripts, no analytics SDK, no social widgets, no embedded video, no chat bubble — none of the usual things that quietly set cookies on a site’s behalf.
Our fonts are self-hosted rather than loaded from Google’s servers, so even that request never leaves our domain. Details in the Privacy Policy.
Your control
You can clear this storage at any time, without asking us and without telling us:
- Clear site data for designly.1619.in in your browser’s privacy settings — under Cookies and site data. This is the one that removes everything above in a single step.
- Or, in developer tools, use Application → Storage → Clear site data. To pick through it instead, expand IndexedDB and delete the designly database, or individual entries in docs and media.
- Or browse in a private window — storage is discarded when you close it.
- Or block storage for this site entirely. Designly will still render and export; it will simply forget your work between visits.
Full detail, including what each item holds, is in the Privacy Policy.
Changes to this policy
If Designly ever adds something that sets a cookie or does track you, this page will say so plainly and ask your consent first. The “last updated” date above reflects the current text.
Questions about any of this: 1619.in.