Privacy Policy

Most privacy policies are long because the product collects a lot. This one is short because Designly collects nothing. The rest of this page exists so you can verify that claim rather than take it on faith.

To be explicit, because vagueness here would be the whole problem:

• Your Markdown, your slides, your images, your exports. These are processed in your browser and stored only in your browser.
• Your name, email address, or any identity. There is no sign-up form, so there is nothing to fill in.
• Payment details. There is nothing to pay for.
• Usage analytics, event tracking, session recordings, or heatmaps. No Google Analytics, no Plausible, no Posthog, no pixel of any kind.
• Advertising or cross-site tracking identifiers. Designly has no advertisers.

This is a design decision, not a promise about future restraint. The application has no code that sends your content anywhere. Open your browser’s network tab while you work and you will see this for yourself.

Designly saves your work in your browser’s IndexedDB — a private database that belongs to your browser and your device. Ours is named designly and it has two object stores: docs and media. It is never sent to us, and no other website can read it.

Here is everything it holds:

docs → designly:document

The Markdown you paste, your chosen format, any layouts you have pinned, and your call-to-action text. This is your work. It is saved so a refresh or a closed tab does not lose it.

docs → designly:settings

Your theme and your brand kit — name, handle, website, accent colour, and which badges you show. Small, boring, and yours.

media → one entry per image

Any logo, avatar, or slide background you add, held as a Blob — the raw image file itself. Nothing else is kept beside it: no filename, no upload date, no account.

One thing sits outside that database, in localStorage:

theme

Light, dark, or system. Written by next-themes, and kept in localStorage rather than IndexedDB because it has to be read before the first paint so the page does not flash the wrong colour at you.

That is the complete list. There is nothing else, and nothing hidden in a cookie.

You can give Designly a logo, an avatar, and background images for your slides. These are worth their own section, because an image feels like the kind of thing that gets uploaded somewhere. This one does not.

• The file is read by your browser, resized to something sensible, and written straight into the media store of the designly database as a Blob. That happens on your machine, in the tab you are looking at.
• It is displayed through a blob: URL — a temporary reference that only this tab can resolve. It points at your own disk, not at a server, and it stops working the moment you close the tab.
• It is never transmitted. Designly makes no upload request, because there is nowhere to upload to. The same bytes that render your slide are the ones that get exported.
• Resizing quietly helps you: the image is redrawn on a canvas, which discards the original file’s metadata — including any GPS coordinates your camera wrote into it.

Images are deleted exactly the way everything else is: remove them in the app, or clear this site’s data and the whole database goes with it.

Because your data lives only in your browser, deleting it takes seconds and does not involve us at all. The surest route clears the database and the theme key together:

• Browser settings. Find the privacy section — usually Privacy and security → Cookies and site data → See all site data in Chrome and Edge, or Privacy & Security → Cookies and Site Data → Manage Data in Firefox. Search for designly.1619.in and delete it. This removes the IndexedDB database, the theme key, and anything else this site has stored.
• Developer tools. Open them, go to Application → Storage (Chrome and Edge) or Storage (Firefox), and use Clear site data. To delete only part of it, expand IndexedDB, find the designly database, and delete it or the individual entries inside docs and media.
• A private window. Everything is discarded the moment you close it.

Deleting your browsing history alone will not do it — on most browsers that leaves site data untouched. Use one of the routes above.

Designly makes almost no outbound requests. There are exactly two worth telling you about.

Google Fonts

Our typefaces — Fraunces, Public Sans, and JetBrains Mono — come from Google Fonts. They are downloaded at build time and served from our own domain, so your browser does not contact Google when you load a page. No font request, no IP address shared, no cookie set.

Our host

The site is served by a hosting provider, which — like every web server on the internet — necessarily sees the IP address and user agent of anyone requesting a page, and may keep short-lived operational logs for security and uptime. This is the raw mechanics of HTTP, it applies to the page files only, and it never touches the content you create inside the app. We do not read these logs to build a profile of you and we do not join them to anything.

Privacy law — the GDPR in Europe, the Digital Personal Data Protection Act in India, and their equivalents elsewhere — gives you rights over personal data a company holds about you: access, correction, erasure, portability, objection.

These rights are real and we respect them. They are also, in our case, largely moot: we hold no personal data about you, so there is nothing to disclose, correct, or delete. You exercise every one of them yourself, instantly, without asking us:

• Access — open the designly database in your browser’s developer tools and read it. Your text is stored as plain, readable JSON; your images are the image files themselves.
• Portability — export your designs, or copy your Markdown. It is your text in an open format, not locked in a proprietary store.
• Erasure — clear this site’s data, as described in How to erase all of it. Done.

If you believe we hold personal data about you anyway, get in touch via 1619.in and we will answer honestly — including if the honest answer is “we don’t have anything of yours”.

Designly is not directed at children and collects no data from anyone, of any age. There is no age gate because there is nothing to gate.

If Designly ever gains a feature that touches a server — sync, accounts, anything at all — this policy will be updated before that feature ships, not after, and the change will be obvious rather than buried. The “last updated” date at the top of this page always reflects the current text.

Designly is built and operated by Deepak Kumar, based in India. For anything on this page, reach me via 1619.in.