Privacy Policy

1. Who we are

The controller responsible for your personal data is Memorecs For Digital Solutions, a company registered in Egypt under commercial registration no. [11070 02000 54453], with its registered address at [[6th of October, 9 Yasmeen Street, Al-Kafrawi Axis, P 1880, District 8]] ("Memorecs", "we", "us"). We process personal data in line with Egypt's Personal Data Protection Law No. 151 of 2020 and its Executive Regulations.

2. Whose data this Policy covers

Different people use Memorecs in different ways. The data we hold depends on how you use it.

3. Our role, and the role of Owners and businesses

We are the controller for the data we need to run Memorecs. This includes accounts, Codes, orders, security, and support.

Owners decide what goes on their Memories and who they share them with. A Guestbook Owner decides what to do with the contributions Guests send them. When individuals use Memorecs for personal or household purposes, such as gifts, family events or personal keepsakes, they are responsible for having permission to include other people (Terms, Section 8).

Businesses that use Memorecs as a record are controllers of their clients' data. An example is a pharmacy explaining a prescription. We act as their processor. We handle that data only on their instructions and under a data-processing agreement. Questions about such records should go first to the business that created them.

4. Information we collect

4.1 Content you add

When you create a Memory or contribute to a Guestbook, we collect and store what you add:

• voice and audio recordings, videos, photographs and images.
• text and notes, documents, links, captions and names. and
• the date and time each item was added.

Photos and videos can contain hidden details (metadata), such as the place and time they were taken and the device used.

4.2 Account information

If you create an Account, or sign in with [Apple / Google / Facebook], we collect:

• your name and email address.
• your phone number, if you give it.
• your password, which we store only in hashed form, or your sign-in provider identifier.

4.3 Code and Memory information

For each Code, we keep:

• its identifier and activation date.
• which Account or device controls it.
• its settings, such as its type, contribution limits, and whether it is password-locked (we store Memory passwords only in hashed form).
• basic view counts.

4.4 Guest and device information

Guests do not need an account, and we do not ask for their name. Guests may choose to type a name or message. Guestbook Owners often limit contributions to one per device to stop duplicate or unfair submissions. To enforce these limits, we use:

• a session cookie and an identifier stored in your browser.
• technical characteristics of your device and browser, such as its type, operating system, browser version, screen size, language, and time zone.

From these, we create a pseudonymous device identifier. We use it only for:

• enforcing contribution limits.
• detecting abuse, such as one device sending many reports or submissions.
• securing the services.

We do not use it to identify you by name, to track you across other websites, or for advertising. We do not treat IP addresses as device identifiers, because many guests at one venue often share the same Wi-Fi.

4.5 Reports and moderation

If you report a Memory, we collect:

• the reason you choose and any details you write.
• the time of the report.
• your device identifier, which we use to stop one device from sending many reports.

We do not tell the Owner who reported their Content. We also keep records of the steps we take on reported Content, notices we send, and appeals.

4.6 Orders and Business Customers

When you order Products, we collect:

• Contact names, company name, phone, email, and billing and delivery addresses.
• Order details, invoices and payment status.
• The artwork, logos, names, and messages you supply for customisation.
• Our correspondence with you.

Payments are handled by [Cash/Check/Bank Transfer]. We receive confirmation of payment, but we do not receive or store your full card details.

4.7 Support and communications

When you contact us by email, phone or WhatsApp, we keep the messages, call notes and any files you send, so that we can help you and keep a record of what was agreed.

4.8 Technical and usage information

When anyone opens memorecs.com or a Memory, our systems and content-delivery network automatically log:

• IP address, browser and device type, and operating system.
• Errors and performance data.

We use this to deliver Content, keep the Services secure and fix problems. Cookies are covered in Section 12.

5. How we use information, and our legal basis

We use personal data only for the purposes below. Each purpose has a legal basis under Egyptian law.

Where we rely on consent, we ask for it separately and clearly, in Arabic and English. You can withdraw it at any time. Withdrawing consent does not affect processing we carried out before you withdrew it.

6. What we do not do

• We do not sell or rent personal data or Content.
• We do not use Content for advertising profiles or targeted ads.
• We do not run facial recognition, voice identification, or other biometric analysis on Content.
• We do not use Content to train AI models.
• Our staff does not have access to your content, except for:
• Providing support you ask for.
• System reports.
• Investigating security or abuse.
• Complying with the law.

We keep a log of this access.

• Our automated processing is limited to:
• Converting files so they play on all devices.
• Creating thumbnails.
• Scanning text for abusive words
• Spotting abuse patterns.

7. Who can see your Content

Memorecs is designed for sharing, so please read this carefully.

• Anyone who can scan or open a Code can see its Memory, unless it is password-locked. This includes anyone who finds, borrows, or photographs the Product.
• Journals are readable in full by anyone who scans them, unless they are locked or have a password.
• Guestbook contributions go to the Guestbook Owner, who may share them, for example, in an event album or on a screen at the venue.
• The person who received a gift can see the Message. They do not control it. The Owner can still edit (within limits), lock, or delete it (the Owner of the Digital Code is the first one who claims it).
• Viewers can make copies by taking screenshots or recordings. Deleting a Memory cannot remove copies that other people have already made.

Please do not add ID numbers, financial details, passwords, addresses, or health or legal information to an unlocked Code.

8. Who we share information with

We share personal data only as described below.

• Service providers that work for us under contract, under confidentiality obligations, and only on our instructions:

• The Guestbook Owner receives Guest contributions.
• The authorities, when Egyptian law or a valid order from a competent authority requires it, or when needed to protect someone's life or safety. Where the law allows, we will tell you.
• A buyer or successor of our business, if we merge, are acquired or sell assets. They would be bound by this Policy, and we would notify you.

We do not share your Content or personal data with the shops, event planners or other Business Customers who sold you a Product.

9. International transfers

Our main infrastructure is provided by Amazon Web Services. Your data may therefore be stored or processed outside Egypt, and some service providers may process it in other countries. We transfer personal data abroad only as Egypt's Personal Data Protection Law allows, which includes:

• Holding the licence or permit required from the Personal Data Protection Center.
• Choosing providers that protect data to a standard no lower than Egyptian law requires.
• Using contractual, technical and organisational safeguards, including encryption.

10. How long we keep information

11. How we protect information

We use technical and organisational measures appropriate to the sensitivity of the data. These include:

• Encryption. All traffic to our website is encrypted with HTTPS, and browsers are instructed to always use it. Stored files and data are encrypted at rest.
• Passwords and codes. Account passwords are stored only as salted hashes, never in readable form. Passwords that protect a Memory are stored the same way. Email verification codes and password-reset links expire quickly, can be used only once, and are stored only in hashed form.
• Account protection. New accounts must confirm their email address before they can sign in, including accounts created through Google, Apple, or Facebook. We limit repeated sign-in, verification, and password-reset attempts.
• Abuse protection. We use rate limits and reCAPTCHA to block automated abuse of our forms.
• Staff access. Access to our administration tools is restricted by role, following the least-privilege principle. Staff actions that change data are logged.
• Reported content. Content removed after a report is moved to restricted storage that the public cannot access.
• Maintenance. We apply security updates regularly and keep backups.

No online service can be perfectly secure. If a personal-data breach occurs, we will:

• notify the Personal Data Protection Center within 72 hours of becoming aware of it. and
• notify affected people within three working days after that, as Egyptian law requires.

You can help keep your data safe. Use a strong password, protect unused Products as you would cash, and password-lock private Memories.

12. Cookies and similar technologies

We use a small number of cookies and browser-storage items.

You can also delete or block cookies in your browser. If you block essential cookies, parts of the Services, including Guestbook contributions, may not work.

13. Your rights

Under Egyptian law, you have the right to:

• Know whether we hold your personal data, and get a copy of it.
• Have inaccurate or incomplete data corrected.
• Have your data erased when it is no longer needed or was processed unlawfully.
• Restrict or object to certain processing.
• Be told about a breach that affects you.

How to use your rights. If you have an Account, use your dashboard or email [privacy@memorecs.com]. We may need to check your identity before acting on a request, so that we never hand someone else's Memory to the wrong person:

• Claimed Codes. We may ask you to prove you control the Code, for example by a verification email you claimed it on.

We respond within [30] days. Requests are free unless they are clearly excessive.

If you appear in someone else's Memory without your permission, report it using the Report option or email us. We will review it under our Terms (Section 10).

You also have the right to complain to Egypt's Personal Data Protection Center. We would appreciate the chance to resolve your concern first.

14. Sensitive personal data

We do not ask for sensitive personal data, such as health, biometric, religious, political, or financial data. Please do not add it to a Memory unless you are permitted to.

When a business, such as a clinic or pharmacy, uses Memorecs to give health information to its clients, the business must have the person's explicit written consent and lock the Memory with a password (Terms, Section 12). We process that data only on the business's behalf, with extra safeguards, and only where we hold the permit Egyptian law requires.

15. Marketing

We send marketing messages by email, SMS or WhatsApp only if you have given prior explicit consent. Every message identifies Memorecs and includes an easy way to opt out. Even if you opt out, you will still receive essential service messages, such as order updates, security alerts, and changes to our Terms.

16. Links to other services

Memories can link to or embed other services, such as video or music platforms. When you open those links, the other service's own privacy policy applies, and we are not responsible for its practices.

17. Changes to this Policy

We may update this Policy. When we do, we will change the "Last Updated" date. For significant changes, we will notify Account holders by email or in the Service before the changes take effect. Where a change requires your consent, we will ask for it.

18. Contact us