Privacy

What Softling knows about you.

A gift is personal, so this page is deliberately specific about what is stored, where it lives and who can open it.

Last updated

The short version: Softling stores the gift you write, the names you enter, any photos you choose to add, and a simple view count. There is no account, no email capture and no advertising tracker in this build. A gift is only reachable through its link.

1. What is collected

When you save a gift, the following is written to the deployment’s database:

  • Recipient and sender name. Used to personalise the gift and the private link.
  • Gift content. Opening line, letter, final question, button labels and any other fields you fill in.
  • Photos you add. Optional, up to three. Compressed in your browser before upload.
  • Chosen stickers. Optional, up to three decoration ids and their corners. They are artwork that ships with Softling, not personal data.
  • A hashed deletion key. A one-time random token is created with the gift. Only its SHA-256 hash is stored, so it can authorise deletion without keeping the token itself.
  • A view counter. Incremented when the gift page is opened. No IP address is stored.
  • Creation timestamp. Stored with the gift record so the link can be resolved.

No email address, password, phone number or payment detail is requested, because none of those are needed to make or open a gift.

2. How photos are handled

Photos are compressed in your browser before they leave your device: resized to a maximum of 1080px, converted to WebP and targeted at roughly 300KB. The original file is never uploaded.

If the deployment has Cloudinary configured, the compressed image is uploaded to Cloudinary and the gift stores its URL. If Cloudinary is not configured, the deployment runs in local mode and the compressed image is embedded directly inside the gift record.

In both modes the image is served as part of the private gift page. It is not added to a public gallery, a sitemap or a social preview.

The bonus photo library ships with Softling as local WebP files under /assets/suggestions/. Choosing one copies its path into the gift; no third-party image request is made when the gift opens, and no data about the recipient is sent to the stock provider.

Drafts in your browser

While you build a gift, the current fields and stickers are saved as a draft in this browser using localStorage. The draft stays on your device, is offered back the next time you open the same template, and is removed when you save the gift, discard the draft or clear site data. It is not uploaded until you press the save button. Photos embedded in a draft count toward the browser’s storage quota; if the quota is full, Softling says so instead of silently dropping content.

3. Where the data lives

Softling supports two storage modes and uses whichever the deployment is configured for:

  • Supabase — gifts are stored in a Supabase project controlled by the site operator.
  • Local file — gifts are stored in a JSON file on the server running the app. This mode exists so the product works without external credentials.

The public marketing pages are served by the hosting provider (for example Vercel) and do not read gift data.

4. Cookies and analytics

This build sets no analytics, advertising or cross-site tracking cookies. No third-party tag manager, pixel or session recorder is included.

Hosting providers may keep standard server logs for security and reliability. Those logs are controlled by the operator, not by Softling’s application code.

5. Who can open a gift

A gift is unlisted: it is not browsable, not linked from public pages and marked noindex, nofollow so search engines are told not to index it. It is also excluded from the sitemap.

This is privacy by obscurity, not encryption. Anyone who has the exact URL can open the gift. Treat the link the way you would treat a private message, and do not post it publicly if the content is personal.

6. How long it stays

There is no automatic expiry in the current product. A gift remains available while the deployment keeps its data. In local mode, clearing the stored file removes every gift created in that environment.

If you need a gift removed, ask the operator of the deployment where it was created. Include the gift URL in the request.

The browser that created a gift also gets a one-time deletion key. While the success screen is open, Delete this gift removes the record, its names, letter and photos. The key is not shown again and there is no account to recover it, so keep the success screen until you are sure. Deleting cannot be undone.

7. Your choices

  • Leave photos out — the experience skips the photo scene without breaking.
  • Use a first name or nickname instead of a full legal name.
  • Avoid including addresses, ID numbers or other sensitive details in the letter.
  • Delete a gift from the success screen in the browser that created it, using the one-time key issued at save time.
  • Create a new gift and share the new link if you want to replace something; published gifts cannot be edited.

8. Contact

This build does not configure a dedicated privacy email address. The person or organisation operating the deployment is responsible for data requests. If you received a gift and want it removed, reply to the person who sent it and ask them to contact the operator.

For how the product works, see how it works and the FAQ. For acceptable use, see terms.