ZOE Connect — Stay connected. Anytime. Anywhere.ZOE CONNECTStay connected. Anytime. Anywhere.
Sign in
Secure HTTPS connection

Security at ZOE Connect

This page is maintained by ZOE Connect to answer common security and privacy questions about our service. It describes the controls that are active today — it is not an independent audit or certification of ZOE Connect.

Controls in place

HTTPS in transit

Connections to ZOE Connect are protected in transit using HTTPS.

Payments processed by Stripe

Card details are handled directly by Stripe and are not stored by ZOE Connect.

Protected accounts

Passwords are hashed, sessions are token-based, and your data is isolated per account.

Third-party fulfillment

Eligible digital products are fulfilled through Reloadly and applicable operators or brands.

Payment security

Payments are processed securely by Stripe. Card details are handled directly by Stripe and are not stored by ZOE Connect.

Stripe payment processing

Provider

Card details are handled directly by Stripe and are not stored by ZOE Connect.

ZOE Connect security

Self-described

Our security page describes current controls. It is not an independent certification or audit.

Encryption in transit

Every request to ZOE Connect is served over HTTPS. Our hosting provider protects connections in transit using HTTPS, and certificates are managed by our hosting provider. You can inspect connection details in your browser.

Card payments

Payments are processed securely by Stripe. Card details are handled directly by Stripe and are not stored by ZOE Connect. We retain only the payment reference and order details needed for your receipt and support.

Accounts and access

Accounts are protected by hashed passwords or Google / Apple sign-in. Sessions use short-lived tokens, and database access rules restrict every record to its owner. Staff back-office access is limited to named roles.

Data we store

We store the details needed to deliver and support your orders: recipient number or email, operator or brand, amount, status, and receipt history. Redemption codes are shown only to the purchaser and recipient. We do not sell your data.

Report a security issue

If you believe you've found a vulnerability or notice suspicious activity on your account, contact us and we'll respond as quickly as we can. Please avoid sharing full card numbers or passwords in your message.

support@jeromedigitalshop.com
FAQ

Frequently asked questions

Is the ZOE Connect website encrypted?

Yes. Connections to ZOE Connect are protected in transit using HTTPS. You can verify the connection information in your browser.

Does ZOE Connect store my card number?

No. Card numbers, CVCs, and expiry dates are submitted directly to Stripe through its checkout. We retain only the payment reference and order details needed to support the purchase.

How do you protect my account?

Accounts are protected by hashed passwords or Google/Apple sign-in. Sessions use short-lived tokens, and database access rules restrict every record to its owner. We also recommend using a strong, unique password and keeping your device secure.

What should I do if I notice suspicious activity?

If you believe your account has been compromised or you notice suspicious activity, change your password immediately and contact us at support@jeromedigitalshop.com. Please avoid sharing full card numbers or passwords in your message.

Is my recipient's phone number or email secure?

Yes. Recipient information is transmitted over encrypted connections and stored only as long as needed to deliver and support your order. We do not sell or share recipient data for marketing purposes.

Shared responsibility: the controls above cover the ZOE Connect service and its hosting and payment providers. Keeping your password private, your device secure, and your recipient details accurate remains your responsibility.

Citations

Sources & references

Claims on this page are backed by the primary sources below. Each link goes to the publisher, not to a summary.

  1. PCI Data Security Standard (PCI DSS)
    PCI Security Standards Council

    Definition of PCI DSS and Level 1 service-provider requirements referenced on our security pages.

  2. Stripe security and PCI compliance
    Stripe

    How card data is captured and tokenised by our payment processor.

  3. Recommendation E.164: The international public telecommunication numbering plan
    ITU-T

    The numbering rules we use to normalise and validate every recipient phone number.