Privacy Policy

This Privacy Policy explains how JoyZap processes personal data when you use our websites, applications, public pages, digital gifts, payment flows, support channels, and related services. It also covers limited information we receive about a person who does not yet have an account, such as an external gift recipient or a guest Public Zap sender.

Joy Company LTD, Varna, Bulgaria is the controller of personal data described in this Policy. Contact us at contact@joyzap.net.

Depending on the features you use, you may provide your name, email address, password, date of birth, gender, profile photo, city, country, preferences, referral information, and communications with us. Passwords are stored as security-protected hashes rather than readable passwords.

You may also provide event details, gift titles and messages, images, videos, URLs, cards, time capsules, reactions, battle photos, reports, and other content. Avoid including unnecessary personal or sensitive information and do not provide another person's data without a lawful reason and appropriate notice.

We process identifiers, activation and recovery tokens, account status, authentication events, and session information to create, secure, and manage accounts. When Google or Meta (Facebook) sign-in is configured and you choose it, we receive the provider identifier and profile information the provider makes available for the sign-in flow, such as name, email address, and profile image.

The sign-in provider processes information under its own privacy notice. JoyZap does not receive your provider password. Available sign-in methods may change, and this Policy will be updated when a provider is removed or added.

We process the content and metadata needed to provide profiles, events, follows, followers, relationships, gifts, delivery schedules, messages, reactions, rankings, notifications, mystery matching, Joy Battles, reports, and activity history. Metadata can include sender and recipient identifiers, event identifiers, timestamps, delivery status, content type, and moderation status.

Joy Received, Joy Sent, Joy Dollar balance changes, and ranking records are kept separate according to their product purpose. We use these records to deliver gifts, show history and rankings, prevent duplicate transactions, reconcile balances, and investigate misuse.

Stripe processes payment details when you buy Joy Dollars or send a paid Public Zap. JoyZap receives and stores limited transaction information such as a Stripe customer, Checkout session, payment, or event identifier; purchase or gift description; amount and currency; payment status; timestamps; and limited customer details returned for reconciliation, fraud handling, support, refunds, and accounting.

JoyZap does not receive or store your full payment card number, card security code, or online-banking credentials. Stripe may process device, payment-method, identity, and anti-fraud information as an independent controller or processor according to its role and privacy notice.

We process technical information needed to operate and protect the Service, which may include IP address, request and security logs, browser or app type, operating system, device and push-notification identifiers, connection and session data, error information, and timestamps. We may derive coarse location or risk indicators from an IP address.

During profile completion, the current implementation may ask an IP-based location provider to suggest an approximate city and country. You can correct the suggestion. We do not describe this approximation as precise GPS location.

A JoyZap user may provide your email address or phone number to address an external-recipient gift to you. We receive that information from the sender and use it to create and deliver the invitation, prevent duplicate or unsafe delivery, let the sender manage the delivery, and allow an eligible recipient to claim the gift.

If you do not want us to use contact information for an external gift, follow the instructions in the delivery notice or contact us. We may keep a non-reversible suppression value so the same raw destination is not used again after an objection or account deletion without retaining the contact detail itself.

Other users may also create content that refers to or depicts you. You may report content or contact us to exercise applicable rights. We will consider the rights and lawful interests of everyone involved.

When you use the Contact Us form, we process the name you choose to provide, your email address, your message, delivery metadata, and later correspondence so we can receive, investigate, and answer the inquiry. The form sends the message through Amazon Web Services email infrastructure to the JoyZap support mailbox; it does not create a DynamoDB submission record.

• create and manage accounts, authentication, profiles, settings, and account deletion;
• provide events, social connections, content, digital gifts, schedules, delivery, reactions, rankings, battles, history, and notifications;
• process and reconcile Joy Dollar purchases and paid Public Zaps with Stripe;
• communicate about transactions, security, support, legal terms, service changes, and user requests;
• protect users, moderate content, enforce rules, prevent fraud and abuse, secure the Service, and maintain reliable operations;
• comply with accounting, tax, consumer, privacy, child-safety, law-enforcement, sanctions, and other legal obligations; and
• understand and improve performance and usability using data that is proportionate to that purpose.

For first-party product analytics, JoyZap collects page-group visits, named product actions and outcomes, coarse dwell-time buckets, device class, and immediate navigation transitions. Anonymous events are cookieless and have no persistent browser identifier. For authenticated events, the server derives a pseudonym from the existing user identifier; the client does not send the identifier or pseudonym, and admins see aggregate reports only.

Product analytics excludes entered content, names, email addresses, identifiers for JoyZap users, products, gifts, calendar events, or other product records, raw URLs and query strings, IP addresses, free-form error text, session replay, and heatmaps. Each analytics event has a random per-event analytics idempotency key; it is not a browser, session, or user identifier and is not reused across events.

We rely on performance of a contract or steps you request before a contract when data is needed to create an account, provide a selected feature, deliver a gift, process a purchase, or answer a service request.

We rely on legal obligations for required accounting, tax, consumer, privacy, safety, and authority-response records. We rely on legitimate interests for proportionate security, fraud prevention, service reliability, support, moderation, legal claims, and product improvement after considering effects on your rights. We rely on consent only where the relevant processing genuinely requires it, such as optional device permissions or communications, and consent can be withdrawn without affecting earlier lawful processing.

Where we process information received from a sender to deliver an external gift, the usual basis is the sender's requested service and our legitimate interest in completing a limited, expected delivery safely. We honor applicable objection and deletion rights and do not use that raw destination for unrelated advertising.

Depending on your actions and settings, your profile name and image, city or country, public events, follows, reactions, Joy totals and rankings, battle content, and selected gift information may be visible to other users or visitors. Public event pages and shared gift links can be accessible without signing in and may be reshared outside JoyZap.

Review content and audience choices before posting or sending. Privacy settings reduce visibility within the product but cannot make another person's copy or an already shared link disappear from systems outside JoyZap.

We disclose personal data only as needed for the purposes in this Policy. Categories of recipients include Amazon Web Services for hosting, storage, databases, serverless processing, email, and notifications; Stripe for payments and fraud controls; Google and Meta when their sign-in services are configured and chosen; push-notification infrastructure such as Firebase Cloud Messaging; the current IP-based location provider; and professional advisers or support suppliers under appropriate duties.

We may disclose information to competent courts, regulators, tax or law-enforcement authorities when legally required or reasonably necessary to protect rights and safety. We may transfer relevant data during a merger, financing, reorganization, or sale, subject to confidentiality and applicable law. We do not sell personal data for money.

Some providers may process data outside Bulgaria or the European Economic Area. Where the destination does not benefit from an adequacy decision, we use an available lawful safeguard appropriate to the transfer, such as European Commission standard contractual clauses, and supplementary measures where required. A provider may also process information under a legal exception that applies to a specific transfer.

We retain account and service data while the account is active and then delete or anonymize it according to the account-deletion process, subject to limited records needed for another user's delivered content, transaction integrity, fraud prevention, legal claims, or law. Backups and point-in-time recovery copies are isolated and expire on their controlled rotation schedule; deletion controls must be reapplied if a backup is restored.

We retain raw email addresses or phone numbers supplied to deliver an external-recipient gift for up to 12 months, after which the destination is erased and only a non-reversible display mask or narrowly required transaction record may remain.

We normally retain resolved contact and support correspondence for up to 24 months. We may retain a specific exchange longer when reasonably necessary for an active dispute or legal obligation.

Payment, Joy Dollar, tax, and accounting records are restricted and retained only for the applicable statutory period. Certain Bulgarian accounting records may require retention for up to 10 years. This does not justify retaining an entire profile. Reports, fraud indicators, and legal evidence are kept only for a documented period proportionate to safety, limitation, or authority requirements.

Raw events and aggregate counters used for product analytics currently have no automatic expiry.

JoyZap uses cookies, local storage, and similar device technologies for essential sessions, security, theme preference, unfinished flows, payment return state, and product preferences. Some integrated services may set their own technologies when you choose or use them. Blocking essential storage can prevent sign-in or another requested feature from working.

Our first-party product analytics does not set an analytics cookie or store an analytics identifier or queue in local storage, session storage, IndexedDB, or another persistent browser store.

If we introduce advertising or other non-essential device technologies that require consent, we will present the required choice before using them and update this Policy.

We use technical and organizational measures designed to protect personal data, including encrypted transport, access controls, credential hashing, limited service permissions, transaction idempotency, logging controls, and managed AWS infrastructure. Payment card details are handled by Stripe rather than stored in JoyZap's application database.

No internet service can guarantee absolute security. You should use a unique password, protect your devices, and notify us promptly if you suspect misuse. We assess personal-data incidents and notify affected people and authorities when applicable law requires it.

Subject to applicable conditions and exceptions, you may request access to and a copy of your personal data; correction; deletion; restriction; portability; or information about processing. You may object to processing based on legitimate interests, withdraw consent for future processing, and object to direct marketing at any time.

Profile controls let you update certain information and preferences. The Delete Account flow permanently removes the account and starts deletion or pseudonymization of associated data. Some narrowly required financial, transaction, safety, recipient, backup, or legal-claims records may remain for the periods described above.

Send a request to contact@joyzap.net. We may ask for proportionate information to verify identity and authority. We normally respond within one month, subject to lawful extensions for complex or numerous requests. Exercising a right is free unless a request is manifestly unfounded or excessive as defined by law.

JoyZap accounts, Joy Dollar purchases, and paid Public Zaps are for people aged 18 years or older. We do not knowingly permit a child to create an account or make these purchases. If we learn that an ineligible minor provided personal data, we will restrict the account and delete the data unless limited retention is legally required for safety, fraud prevention, or another obligation.

Contact contact@joyzap.net if you believe a minor is using JoyZap or personal data about a child appears in the Service. Child sexual abuse and exploitation and CSAM are prohibited without exception under our Child Safety Standards.

Questions, rights requests, and privacy complaints can be sent to Joy Company LTD at contact@joyzap.net. You also have the right to complain to the Bulgarian Commission for Personal Data Protection or another competent supervisory authority, particularly in the country where you live or work or where you believe an infringement occurred.

We may update this Policy when the Service, providers, or law changes. We will post the new version and effective date and provide additional notice when a material change requires it. Earlier versions remain applicable to disputes about processing that occurred while they were effective where required by law.