Privacy Policy

1. Controller, processor and scope

Loyvero is operated by Rick Anker, a sole trader established in Malta, trading under the name Loyvero. Registered address: 24, Triq ix-Xambekk, Baħar iċ-Ċagħaq, NXR 5072, Malta. VAT number: MT29351227. Loyvero’s legal and privacy contact is hello@loyvero.com.

This notice describes the Loyvero website, merchant enquiry and support features, and the loyalty technology. When a merchant runs a customer programme, the merchant is controller of its customer data and Loyvero is processor acting on the merchant’s documented instructions. Loyvero is controller for its own website enquiries, platform security, first-party funnel measurement and legal obligations. A merchant must provide its own store-specific notice before collecting a customer’s email or creating a reward account; its controller identity and contact details are shown in the store experience when configured.

This notice is factual product information, not legal advice. It does not turn an unconfigured merchant privacy notice into a configured one.

2. Data, purposes and choices

For a customer reward account and sign-in, the store may require an email address. It is used to identify the account, send a requested one-time sign-in code or magic link, issue and display rewards, and maintain reward activity. Without it, the account and ordinary reward flow cannot be provided. The store decides the lawful basis and must explain it in its notice.

Reward claims and redemptions create reward, campaign, stock and event records needed to issue, display and validate the reward. They are required for the programme. A pseudonymous identifier derived from your network address may be processed for fraud prevention; a raw network address is not intentionally stored as the reward-account identifier. Browser user-agent information is received with some claim requests and may be stored with the account event. These identifiers are not described as anonymous.

Optional profile information can include first name, mobile number, birthday, town or city and marketing preferences, where the relevant store enables those fields. A customer can leave optional fields blank without losing ordinary reward-account access, unless the store clearly explains a feature-specific consequence.

Email and SMS marketing preferences are separate choices. They are not required to claim or redeem an ordinary reward. Withdrawing a marketing choice stops future marketing for that channel, subject to messages already in delivery. You may also object to direct marketing at any time.

3. Birthday Rewards boundary

Birthday Rewards are optional and available only when a merchant has enabled and configured the feature. The implemented customer input is a day and month, used to determine when to issue the configured birthday reward. An automatic service email may be sent when that reward is ready; it is separate from general marketing consent and must not contain unrelated promotions or commercial offers.

You can change or remove the birthday later. Removing it prevents future birthday processing; an already-issued reward remains subject to the displayed validity and the merchant’s programme rules. The current evidence does not establish a complete auditable history for every birthday explanation, change, removal, issuance and exact email-template version, so that evidence requirement is a publication and implementation blocker rather than a promise in this notice.

4. Website enquiries, support and measurement

The public partner form collects a public business/store name, preferred Loyvero store name, country, city or locality, business type and a website, ordering-page or relevant platform URL so an application can be reviewed and a private draft prepared. It collects legal company name, company registration number and registered business address when the applicant says the business operates through a registered legal entity; VAT number, postal code and business telephone number remain optional. It collects the primary contact name, role or position, business email and preferred language. Sole-trader details and named contact details may be personal data. We use these details to review the application and, if approved, prepare the Loyvero merchant account. A submitted URL may be inspected for limited public business information using safety controls; retrieved content is untrusted and is not used as instructions. The form does not request payment-card or bank information. Not providing required fields means the application cannot be submitted; optional information is not needed to start the review.

The support form collects name, reply email, message, selected language and form context; business name is collected in the homepage contact variant. The message is sent to hello@loyvero.com through the configured email provider and is not added to the customer rewards database. The form cannot answer a request without the required name, email and message.

The public website records four aggregate first-party funnel events: homepage views, homepage CTA clicks, form starts and successful form submissions. Each event uses an opaque one-time event ID held in memory during the component visit and a language setting. It does not include cookies, local storage, a persistent visitor identifier, IP address, user-agent, URL, query string or form values. Raw events become eligible for purge when they reach 90 days; the current implementation purges eligible rows only during a subsequent event or maintenance operation, not on a verified scheduled timer. No consent banner is used for this non-storage measurement.

5. Other purposes and legal bases

Loyvero processes merchant administration data to create, authenticate and support merchant accounts, configure campaigns, customers, rewards, stock, wallet passes and privacy settings, and provide the platform. In a merchant relationship Loyvero normally acts as processor for customer programme data and as an independent controller for its own account, support and security operations. The merchant determines the lawful basis for its programme; Loyvero’s own lawful basis depends on the specific activity and is not asserted here where the facts are not confirmed.

For a merchant application, Loyvero uses the submitted business and named contact details to review the request and take steps at the applicant’s request toward a possible merchant relationship; this is normally GDPR Article 6(1)(b). Legal acknowledgement evidence is processed under Article 6(1)(c) where a legal obligation applies or otherwise Article 6(1)(f) for accountable operation and dispute prevention. Optional contact permission is separate consent under Article 6(1)(a). Application data is available to authorised Loyvero staff and the providers listed in section 6 only as needed for hosting, database, security and merchant email.

Transactional emails include requested sign-in messages, reward notifications, rights-request messages and merchant communications. They are service communications, not general marketing. Fraud prevention, rate limiting, authentication, security and audit records are used to protect accounts and the platform. Legally required records are retained only where a legal obligation applies.

Billing functionality and a payment provider are not configured as confirmed facts in this public document. No payment collection, payment deadline, refund rule or billing retention period is stated here.

6. Recipients and providers

Data is shared only with the merchant responsible for a store programme, authorised merchant staff, service providers needed for the selected feature, and authorities or advisers where required by law. Loyvero does not sell store customer data or use it for cross-store advertising.

• Supabase: hosted PostgreSQL database, authentication support and object storage.
• Resend: transactional email delivery for sign-in, reward, rights-request and merchant messages.
• Replit: application hosting/runtime and, when configured, the connector proxy for email requests.
• Apple: Apple Wallet pass issuance and updates when enabled.
• Google: Google Wallet pass issuance when enabled.

7. International processing and transfers

The listed providers may process data outside the EEA depending on their current configuration. The current evidence confirms the provider categories and integrations, but does not confirm a particular processing location, adequacy decision, Standard Contractual Clause or other transfer safeguard for every provider. This notice therefore makes no unverified transfer-mechanism claim. Contact hello@loyvero.com to ask for the transfer information available for a particular provider; the answer will reflect the applicable provider configuration and agreement at that time.

8. Retention and deletion criteria

The confirmed retention criterion for public funnel events is eligibility for purge at 90 days, with actual purge performed during a subsequent event or maintenance operation. For merchant customer data, the merchant can configure inactive-customer retention in store settings; the applicable store setting and its current privacy notice govern that processing. Active accounts, active rewards and operational records remain available while needed to provide the configured programme. Redeemed or expired rewards, fraud-prevention records, security and audit logs, authentication logs, application or hosting logs, email-delivery logs, financial records, deleted accounts and backups may have different operational or legal criteria.

The implementation evidence currently does not establish a complete, authoritative duration or deletion criterion for each of those categories. We do not invent one here. Pending access, correction, deletion, restriction or objection handling may require relevant records to be preserved. Merchant-configured retention does not silently alter active reward outcomes.

9. Rights and objections

Depending on the role and legal basis, you may request access, correction, deletion, restriction of processing and portability, and may object to processing based on legitimate interests. You may withdraw consent at any time where processing relies on consent; withdrawal does not affect earlier lawful processing. You may always object to direct marketing, without giving a reason. Use the marketing controls in the store account, the store’s configured privacy contact, the data-deletion route or hello@loyvero.com. We may need to verify identity and will route store-programme requests to the responsible merchant.

The responsible merchant is controller for its customer programme and must identify itself, provide its contact details and handle the applicable request. Loyvero assists that merchant as processor. For processing where Loyvero is controller, contact hello@loyvero.com.

You have the right to complain to the supervisory authority competent for your circumstances. Malta’s Office of the Information and Data Protection Commissioner (IDPC) is a verified supervisory-authority contact where Malta is the relevant authority: https://idpc.org.mt/.

10. Automated decisions

Loyvero does not make decisions based solely on automated processing that produce legal effects or similarly significant effects within the meaning of Article 22 GDPR. Reward-tier or campaign configuration behaviour is a product feature, not a statement of legal approval; merchants must obtain appropriate legal review for their campaigns.

11. Contact and changes

Privacy questions and requests can be sent to hello@loyvero.com. The document identifier shown above is the version to quote in a request. Material changes will be reflected by a new document identifier and effective date.