Plain-language privacy
User Data Privacy
The personalized-card workflow is designed to use as little user information as practical.
What you provide
A card may use the name and photo you choose to submit. No account, password or profile is required.
Why it is used
The information is used to prepare the requested card preview and JPG output.
What is not intended
FestivalCards365 does not intend to build a permanent database of submitted names, photos or personalized card files.
Your choices
You can leave the card maker without generating a card, choose a different authorized photo or avoid sharing the downloaded JPG when it contains information you prefer to keep private.
How a creation request moves
The selected photo is first displayed in the browser so you can crop it. When you press the create button, the name and cropped photo are sent to the website to compose the JPG response. No account profile is created, and the finished file is returned for the current download or sharing action.
Technical logs
The hosting provider may keep ordinary security and access logs, such as an IP address, browser information, requested URL, timestamp and error details. These logs support delivery, troubleshooting and protection of the service; they are different from a permanent gallery of submitted photos or cards.
Your device and other services
A downloaded card may remain in your browser downloads, photo library, backups or a sharing app according to your device settings. If you send it through another service, that provider's privacy terms apply. Delete local or shared copies through those services when you no longer want them.
Questions or concerns
Use the Contact page with the relevant card URL and a concise description of the privacy concern. Avoid attaching passwords, payment credentials, identity documents or an original private photo unless a necessary and secure verification step has first been explained.