
Privacy Policy
Effective November 14, 2026
This policy explains what Wallflores collects, why, who can see it, and how to have it removed. It covers wallflores.com and every Wallflores event page, wall, and dashboard.
1. Who we are
Wallflores is a shared photo and video album for events. It is operated by JDOM LLC, a Texas limited liability company. Privacy questions and requests: contact@jdoviedo.com.
There are four kinds of people in this policy:
- Hosts create an event and may buy a plan for it. Co-hosts help a host.
- Guests join an event from a link or QR code and share photos and videos.
- People in photos appear in something a guest shared. They may never have used Wallflores.
- Visitors look at our website, try the sample event, or join our early access list.
2. What we collect
From hosts and co-hosts:
- Your email address, when you sign in. If you sign in with Google, also your name from your Google account.
- Event details you enter: event name (often the names of the people being celebrated), type, date, time zone, welcome message, photo ideas for guests, page style, and a cover photo.
- If you add a co-host: that person's email address.
- If you answer our short survey after your event: how many flowers you gave (1 to 5), any words you wrote, the topics you picked, and whether we may quote your words on Wallflores, with the name you chose to show (or Anonymous).
- Payment: handled by Stripe on Stripe's checkout page. We receive a record of the purchase (which plan, the amount, the date, and Stripe's reference numbers). We never receive your card number.
From guests:
- The first name you type when you join. It is shown next to what you share.
- Photos and videos you upload, with any captions.
- Hearts you give to posts, and messages you leave for the host.
- The time you joined and the time you accepted the sharing rules.
- An anonymous ID stored in your browser, so the Service knows which posts are yours. We do not ask guests for an email address or phone number.
About people in photos. Photos and videos show people's faces, and often children, and the people shown may not be users. We store these images only to run the event album. We do not use face recognition: we do not detect, measure, group, or search faces, and we do not offer a "find my photos" feature.
Information inside photo and video files. Phones store extra information inside a photo or video: where it was taken, the date and time, and the device model.
- Location is removed before a file is stored. Your phone blanks the location fields in JPEG, HEIC, and HEIF photos and in MP4 and MOV videos before uploading, and our server checks JPEG photos again. The file keeps its size, date, and camera make and model. Nobody receives the location, the host included.
- Not covered: PNG and WebP images (camera photos are not saved in these formats), and location written in a photo's XMP block by editing software rather than by the camera.
- The smaller copies shown on the wall and in the feed are redrawn images that do not carry this extra information.
- We read the camera make and model fields to tell camera photos from screenshots. We do not store them separately.
Collected automatically:
- Device and connection data that any website receives: IP address, browser type, and the pages requested.
- Error reports, through Sentry, so we can find and fix problems. Reports contain technical details of the error. Cookies, sign-in headers, request contents, event links, and media links are removed before anything is sent. No performance tracing and no session recording.
- An activity log we keep for 180 days: when an event was created, a guest joined, a co-host was added or removed (with the co-host's email), a link was replaced, a post was deleted or removed, a full-quality original was downloaded by someone other than the person who posted it, a plan was bought or refunded, and an event was purged. The log holds IDs and these facts, never photos or guests' names.
- Short-lived counters of how often an action happens (joins, uploads, hearts, downloads), kept for two days, so the Service cannot be flooded.
- Product analytics, through PostHog, on our website, the pages where a host sets up an album, and the host dashboard. Never on event pages, the wall, or the sample event, so guests are never measured. We record steps a host takes (for example, which setup question they reached, that they downloaded their QR code, or which plan they chose) to see where people get stuck. From our server we also record that a plan was bought, that a free album filled up, and that a host answered our survey (the rating and topics, never the words). We do not record sessions, what you type, photos, names, email addresses, or event links. Before you sign in, a random ID stored in your browser groups your visits; after a host signs in, those visits are tied to the host's account ID, never their email. If your browser sends Global Privacy Control or Do Not Track, analytics does not load.
From visitors: if you join the early access list, your email address and the time you signed up. The sample event at wallflores.com/demo runs in your browser and saves nothing you do there.
What we do not collect: guest lists, phone numbers, contacts, precise location from your device, or anything from your camera roll that you did not choose to upload. We do not run advertising trackers, and analytics never runs on event pages.
3. How we use it
- To run the event: show posts to the people allowed to see them, show public posts on the event's wall, and let the host download the album.
- To keep events appropriate: every photo, and still frames from every video, are checked by an automated service for explicit, violent, or hateful content before they appear. Flagged posts wait for the host. If that service cannot be reached, the post appears without that check. Captions and messages are checked against a word list.
- To take payment, apply the plan the host bought, and handle refunds and disputes.
- To fix problems, prevent abuse, and improve the product, including seeing which steps of setting up an album confuse people.
- Survey answers: to learn what to fix and to reply to you. If you tick the box, we may also quote your words on Wallflores, with the name you chose or as Anonymous. Without the box, your words are never shown to anyone outside Wallflores.
- To meet legal obligations and enforce our Terms.
- Early access list: only to tell you when Wallflores opens. Nothing else.
What we do not do. We do not sell personal information. We do not use photos, videos, or any personal information for advertising. We do not use your photos or videos to train AI models. We do not use your photos in our marketing unless you separately agree in writing.
4. Children
Hosts, co-hosts, and guests must all be at least 18. Wallflores is not directed to children, and we do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has joined an event or uploaded, write to contact@jdoviedo.com and we will delete what they provided.
Children often appear in event photos taken by adults. A parent or guardian can ask for a photo or video of their child to be removed at any time. See section 7.
6. How long we keep it
| What | How long |
|---|---|
| Photos, videos, captions, hearts, guest messages, cover photo, guest list | Until the event's gallery closes: 7 days after the event date on the free plan, 30 days, 3 months, 1 year, or 3 years on the paid plans. After the gallery closes, everything in the event is permanently deleted, normally within a few days. The event's name, dates, and plan stay as a record. |
| A post its uploader removes or the host deletes | Leaves the event at once. Its files and record are held in a trash for 7 days (so the host can undo their own deletion, or we can undo a mistake), then deleted. |
| Uploads that fail our checks or never finish | Deleted by the daily job after one day |
| Guest first names and join times | Deleted with the event. The anonymous ID itself holds no personal details. |
| Activity log | 180 days |
| Usage counters | 2 days |
| Analytics | Up to 1 year, then deleted by PostHog |
| Host account (name, email) | Until the host asks us to delete it |
| Survey answers | Until you ask us to delete them, or your account or the event is deleted. A quote you allowed comes down whenever you ask. |
| Payment records (plan, amount, date, and Stripe's reference; never a card number) | Kept indefinitely, as business and tax records |
| Early access email addresses | Until we send the launch notice |
| Backup copies | The database is backed up daily and each backup is kept 7 days. Photos and videos are copied nightly to a separate backup bucket; a file deleted from the Service stays in that backup for up to 30 more days, then is deleted there too. |
7. Your choices and rights
You can ask us to give you a copy of the personal information we hold about you, correct it, delete it, or give it to you in a portable format. Write to contact@jdoviedo.com. We respond within 45 days.
Guests can also remove their own posts themselves, from the same browser, while the wall is open. Because guests have no account, we may ask for details (the event, your first name, when you posted) to find your posts.
If you are in a photo or video someone else shared, whether or not you ever used Wallflores, ask any of these people; use whichever is fastest:
- The person who posted it. They can remove it from their phone.
- The host. The host can hide or delete any post in their event right away.
- The co-host. The co-host can hide it right away, which takes it off the wall and out of every guest's view, and can ask the host to delete it.
A parent or guardian can ask for any photo or video of their child to be removed the same way.
If it is an intimate image, or you feel unsafe, write to contact@jdoviedo.com with "URGENT" in the subject line. We handle these first. Tell us the event's name or link, a description of the photo or video, and how you are connected to it. Please do not send ID documents unless we ask.
We cannot remove copies that someone already downloaded or captured from a screen.
9. Security
- All connections use HTTPS, and browsers are told to use it for a year.
- Photos and videos are stored in a private storage bucket. They can be viewed only through links that expire after 15 minutes, issued only to people allowed to see that post.
- Uploads go through links that expire after 10 minutes and accept only the approved file type and size. Each arrived file is moved to a location no upload link can write before it is checked and shown, so a file cannot be swapped after approval.
- Database rules limit each person to the events and posts they are allowed to see.
- Administrative keys are kept on the server and are never sent to browsers.
- Hosts sign in through Google or with a one-time code sent to their email. We do not use or store passwords.
- A host can replace the event link at any time, which locks out anyone who has the old one and has not joined.
- Pages carry a content security policy that limits where scripts and media may load from, and cannot be shown inside other websites.
- How often anyone can join, upload, heart, or download is limited.
- An activity log records sensitive actions (section 2).
- The database is backed up daily, and photos and videos are copied nightly to a separate bucket that the website's own keys cannot reach.
- Event pages are kept out of search engines, and event links are not passed to other sites.
No system is perfectly secure. An event link works for anyone who has it, so its privacy depends on who it is shared with. If a breach affects your information, we will notify you as the law requires.
10. Changes to this policy
When we make an important change we will update the date at the top and post the new policy on our site. Guests do not give us contact details, so guests see the current policy linked from the event page. A change to our service providers is a change to this policy.
11. Contact
JDOM LLC (Wallflores). Email: contact@jdoviedo.com. Mail: 5900 Balcones Dr Ste 100, Austin, TX 78731.