Privacy Policy

1. Who we are

This Privacy Policy explains how Make Someone Happy Or Not (the "Service", "we", "us") processes personal data when you create, purchase, receive or view a personalized digital surprise, use My surprises, or contact us.

The Service operator and data controller is BY JOANNA THE BEAUTY SPOT, registered at 18 Athinon Street, Rafina 190 09, Greece. Tax/VAT number: 157690893. Commercial registration (G.E.MI.): 164238603000. For privacy enquiries, email info@makesomeonehappyornot.com or use our Contact page.

2. Information we process

• Order and billing information: the purchaser's name and email address, billing country, street address, city, and postal code or state/province where applicable; order identifiers, amounts, currency, payment status and timestamps.

• Surprise content: sender and recipient names, messages, occasion/template, tone and customization choices, including selected text, emojis and music. Content may identify someone other than the purchaser.

• Payment and receipt records: payment-provider references and confirmation information, tax calculations, receipt identifiers and the billing details required for the receipt. Where a coupon is used, we record the redemption and discount information.

• Checkout acknowledgements: the applicable Terms and Privacy Policy versions and the time of the immediate-delivery acknowledgement. Checkout requires acceptance of the Terms and a separate immediate-delivery/withdrawal acknowledgement.

• My surprises access: the email address used to request access, an access-token hash, expiry and use timestamps, and the request's IP address and browser user-agent. The email, IP address and user-agent in these access-link records are encrypted in the application database.

• Sessions and security information: session identifiers, request IP address and browser user-agent where stored by the session system; temporary rate-limit information; and technical error and security records.

• Communications: the name, email address, subject and message you submit through Contact, any optional surprise URL, and information you send us in support, complaint or privacy correspondence.

• Optional analytics: consent choices and information about visits to eligible public pages, but only when analytics is enabled and you have accepted analytics cookies.

Information is supplied by you, by the purchaser who creates a surprise, through the operation of the Service, or by the payment and invoicing providers. Please do not include passwords, payment-card details, confidential information or unnecessary sensitive information in a surprise or contact message.

3. IP addresses and access to surprise links

We do not store the purchaser's IP address in the purchase record. This does not mean that IP addresses are never processed: the My surprises access-link system, database-backed sessions, hosting infrastructure and relevant third-party services may process them as described in this Policy.

For protection against excessive requests and attempts to discover surprise links, the application keeps temporary counters and keyed cryptographic hashes of IP addresses and attempted nonexistent link paths. These counters do not store the original IP address or full surprise URL. They expire after the relevant security window, and expired entries are subject to scheduled cleanup. They are not a permanent gift-viewer history.

The application does not maintain a per-surprise list of visitors or their IP addresses. Hosting and payment providers may separately keep access or fraud-prevention records under their own service terms.

4. How and why we use information

• Providing the purchase: to create the selected digital experience, confirm payment or coupon redemption, provide the purchased link, send transactional emails and maintain the disclosed access period.

• Customer access and support: to send private My surprises access links, display the purchaser's orders and available receipt links, resend a valid surprise link, and respond to enquiries.

• Accounting and legal obligations: to calculate and record the applicable tax treatment, issue receipts, maintain required accounting records and respond to lawful requests.

• Security: to protect accounts and links, limit suspicious traffic, reject spam submissions, diagnose faults and investigate reported misuse.

• Optional analytics: to understand traffic to eligible public pages when analytics consent has been given.

For purchaser data needed to provide an order, processing is based on the contract or steps requested before entering it (GDPR Article 6(1)(b)). Required accounting and legal processing is based on legal obligations (Article 6(1)(c)). Limited security, support, dispute-handling and recipient-content processing may rely on legitimate interests (Article 6(1)(f)), subject to the rights of the people concerned. Optional analytics relies on consent (Article 6(1)(a)).

The purchase contract is with the purchaser; it is not automatically a legal basis for all processing of a recipient's data. Accepting the Terms is not blanket consent for unrelated uses. Required checkout information is needed to complete the purchase, while analytics consent is optional. We do not subscribe purchasers to marketing emails merely because they placed an order.

5. Recipients and shared links

A purchaser may supply a recipient's name and personalized text. Recipients do not need an account or payment to open a valid surprise link. The purchaser is responsible for sharing the link appropriately and for having a lawful reason to submit information about another person.

Anyone with a valid surprise URL may be able to see its names and content. An unlisted, random link is not password-protected storage. Someone who receives it may forward it, take screenshots or copy the content. We ask search engines not to index surprise pages, but cannot guarantee that third parties will respect those instructions or keep a forwarded link private.

If a surprise identifies you and you have a concern, contact us with the relevant URL or enough information to locate it. Requests are reviewed manually, including the requester's identity, the content involved and any accounting or legal obligations. A purchaser's agreement does not remove a recipient's data-protection rights.

6. Payments and receipts

Payment details are entered on the active payment provider's hosted page, not in our payment form. Depending on the provider active at checkout, payments are handled by Stripe or Worldline/Cardlink. Cards and available digital wallets are processed by the payment provider. Our checkout does not collect or store full card numbers or card security codes.

We receive the payment status, amount and transaction references needed to verify the purchase. We do not send the personalized surprise message to the payment provider as the payment description. A 100% coupon redemption does not require a card payment.

When the receipt integration is enabled, WRAPP receives the purchaser's billing information, the order/service description, payment reference where applicable, amounts and tax information. If receipt emailing is enabled, WRAPP also receives the purchaser's email address to send the receipt. Accounting records may be shared with our accountant or competent authorities where necessary and lawful.

Payment providers may also act as independent controllers, for example for their own fraud prevention and legal obligations. Their privacy notices explain that processing.

7. Service providers

Information needed to operate the Service may be processed by:

• Hostinger: hosting and related infrastructure services.

• Stripe or Worldline/Cardlink: the payment provider active for the relevant purchase.

• WRAPP: receipt and accounting processing when that integration is enabled.

• Resend or the configured email service: transactional emails, including order confirmations and private access links. Our support and privacy correspondence is also processed by the email providers used by the sender and our mailbox.

• Google Analytics: optional analytics on eligible public pages when enabled and accepted.

• hCaptcha: the Contact form's security check when enabled. Its verification can involve the request IP address, browser information and the security-check response. See the hCaptcha Privacy Policy.

An integration listed here does not receive data merely because the application supports it; it must be used or enabled for the relevant activity. We may also disclose necessary information to professional advisers or authorities for lawful purposes. We do not sell personal data.

8. Cookies and analytics

Essential cookies support sessions, security and requested functions. We also use cookies to remember the cookie notice and analytics choice; these preference cookies have a seven-day lifetime.

When enabled, Google Analytics is loaded only after analytics consent on eligible public pages, such as the creator's initial page, FAQ and information pages. Our application does not load its Google Analytics tag on surprise links, payment pages, My surprises or Admin pages, or on pages containing sensitive submitted form context. It does not send names, email addresses, personalized messages or private surprise URLs to Google Analytics as configured analytics events.

You can change your choice through Cookie settings. Withdrawing analytics consent stops future loading by our application, clears accessible analytics cookies and reloads a page if its analytics tag has already loaded. It does not automatically erase data already processed by the analytics provider. Payment providers use their own technologies on their hosted pages. See our Cookie Policy for more information.

9. Social media and promotional use

Purchasing a surprise is not permission for us to publish its names or message in advertising or on social media. The Service does not automatically publish purchased surprises and does not currently collect promotional permission through a checkout checkbox.

Any separate proposal to feature identifiable user content requires its own review and appropriate permission. Permission from the purchaser alone does not necessarily authorize publication of another person's information or copyrighted material. Privacy concerns about content under our control can be sent to our privacy contact.

10. International processing

Some providers and their subprocessors may process data outside the European Economic Area, including in the United States. The applicable providers' data-processing and transfer terms describe the safeguards for their services, which may include standard contractual clauses or an applicable adequacy framework. You can contact us for information about the providers and transfer arrangements relevant to your data.

11. How long information is kept

Purchased surprise links are normally available for 30 days after successful payment or coupon redemption, unless a different access period is shown before purchase. Promotional links may have a different period.

Link expiry does not automatically delete the underlying surprise content, order or receipt. At present, removal of stored gift content is handled through administrative review or an approved privacy request, rather than automatic deletion on the day the link expires. The public link is no longer available after expiry, even if associated records remain stored.

• Surprise and order data: retained while needed to deliver the purchased access, handle related support or lawful claims, and comply with accounting duties. Requests to remove unnecessary personal content are reviewed separately from records that must be retained.

• My surprises access-link records: access tokens normally expire after 15 minutes and are single-use. A new eligible access-link request removes earlier unused tokens for that email. Daily cleanup removes token records that have been expired for more than one day.

• Sessions and security counters: sessions expire under the configured inactivity limit; temporary security counters expire after their applicable rate-limit window. Expiry and physical cleanup are not always simultaneous.

• Application logs: retained according to log rotation and cleanup settings. Different log types can have different retention periods; a current log file is not necessarily removed by the cleanup for old files.

• Contact and privacy correspondence: processed through our email systems and retained as needed to respond, follow up, handle complaints or meet legal requirements. The application does not maintain a separate Contact-message database.

• Receipts and accounting records: retained for the period required by applicable law. Approved removal of gift content does not automatically delete legally required billing or receipt records, including records held by WRAPP.

• Backups and provider copies: may remain until the relevant backup rotation or provider retention period ends. Their retention is separate from expiry of the public link.

12. Security

The application uses access controls, administrator authentication, request validation, rate limits and restricted access to private pages. Selected personal fields and cached gift content are encrypted at rest, and the public Service uses HTTPS. Technical security rules can reject suspicious submissions or temporarily limit excessive requests.

No online service can guarantee absolute security. Keep private access links confidential and report suspected misuse through our Contact page. Do not send passwords or card details with a report.

13. Your rights

Subject to the GDPR and applicable exceptions, you may request access, correction, deletion, restriction, portability where applicable, or object to processing, including processing based on legitimate interests. You may withdraw consent without affecting processing that was lawful before withdrawal.

Send requests to info@makesomeonehappyornot.com or through Contact. We may ask for proportionate identity verification. Requests are reviewed manually; we normally respond within one month, with extensions where the law permits. We will explain any lawful limitation, including retention of required accounting information.

You may complain to the Hellenic Data Protection Authority or another competent data-protection authority.

14. Children and policy updates

Purchases are intended for adults aged 18 or over. The Service does not ask for a purchaser's date of birth or operate a separate age-verification process. Users should not include sensitive or unnecessary information about children in a surprise. Contact us if you believe a child's information has been used inappropriately.

We may update this Policy when the Service or its data-processing arrangements change. Related documents are our Terms of Use, Cookie Policy, Refund & Cancellation Policy and Acceptable Use Policy.