Privacy & sharing

This page describes the starter eCardPage application. The site owner should keep it accurate when adding analytics, advertising, email services, or other plugins.

What the card app stores

When you create a sharing link, the site stores the card’s names, headline, message, design, optional photo, creation date, and expiry date. Group messages store the contributor’s name, message, approval status, and date. Private creator keys are stored as hashes on the server.

What stays in your browser

Your draft and recent creator links are stored in local browser storage. They are not synced across devices. Use “Clear saved draft” to remove your draft, or clear site data through your browser. Downloaded PNG files stay on your device.

Unlisted links

Anyone with a recipient link can open the card. These pages request that search engines do not index them, but unlisted links are not confidential or protected by recipient authentication. Do not include sensitive information.

Retention and deletion

Shared cards expire after 30 days in the default installation. The site owner can set a different period. Expired cards become unavailable immediately; a daily scheduled cleanup removes card records and group messages. Hosting backups may retain copies according to the host’s policy. A creator can delete a card using their private management link.

Abuse prevention

The plugin temporarily stores a salted hash derived from the request’s IP address to limit repeated submissions. These counters expire within an hour. Hosting infrastructure may also keep access logs under its own retention policy.

Contact messages

The contact form sends your name, email address, and message to the site operator using the configured mail service. Mail providers and mailboxes may retain these messages. The card plugin does not add you to a marketing list.

Cookies and other services

The card studio uses local storage. WordPress may use cookies for administrator sessions and other site features. Additional plugins or embedded services may introduce their own storage and policies. The site operator is responsible for describing them here.

Questions

Use the contact page for privacy questions. Do not send your private creator key unless you have independently verified the request and understand the access it grants.