Draft awaiting legal review. This text is not final and is not legal advice.
Privacy policy
Last updated: 21.11.2026
MyCardly lets businesses run a digital business card. This page sets out what information we keep, why, who sees it and what rights you have.
Who we are
MyCardly is a product of MJGroup, the sole proprietorship of Mousa Jacoub. Business number: 200656858. Address: Burj A-Sukkar 1, Shefar'am 20200, Israel.
This policy covers the mycardly.me website, the dashboard and the public business cards.
What information we keep
No law requires you to give us information, but we cannot open an account without an email address and a full name.
- Account details: email, full name, phone and password. The password is stored as a hash and never as readable text.
- Session data: a login cookie, and a server record with the IP address and browser type.
- Business content: what you put on the card, such as text, contact details, services, hours and testimonials.
- Images: the images you upload. We re-encode them and strip location and camera data. The original file is not kept.
- Security event log: logins, failed login attempts, logouts, password changes and actions on the account and the business, with the user, the time and the IP address.
- Leads from the card form: the card shows the form unless the business turns it off. When someone sends a lead, we store the name, phone, any email and message, the time of consent and the notice version shown. The IP address is not stored with the lead.
- Visiting the site or a card: we run no analytics, tracking or advertising tools of our own. The IP address is used for rate limiting. Server logs record the IP address, the time, the request method and path without the query string, the response status, the bytes sent and the browser type (user agent). The logs are kept for 24 months (730 days). When a request fails, such as an oversize upload or the server failing to answer, the error log can keep the full request for the same period, including the query string and the referrer.
- A business's Meta Pixel ID: a business can add its own Meta Pixel ID to its card. We keep only that ID, in the business settings, and in the security log when it changes. The browser of the person visiting the card sends what the Pixel collects directly to Meta, and we neither receive nor store that information. Details are under "Who sees the information".
Why we use the information
We use the information only for these purposes, and never for advertising or profiling:
- To open your account and log you in.
- To show and publish the business card.
- To protect accounts and detect abuse.
- To answer you when you contact us.
- To store leads for the business that received them, if the feature is on.
Legal bases under the GDPR
This section applies to people covered by the GDPR. For leads, the business that receives them sets the legal basis.
For everything else, these are the bases under Article 6 of the regulation:
- Contract: opening the account, storing content and publishing the card.
- Legitimate interests: security, the event log and preventing abuse.
- Consent: marketing email and non-essential cookies, if we ever have them. You can withdraw consent at any time.
- Legal obligation: keeping or disclosing information when the law requires it.
Who is responsible for the information
For account details, sessions and the security log, MJGroup is the controller (בעל השליטה in the Israeli law).
For leads, and for information about other people that you put on a card, such as a name in a testimonial, the business is the controller and MJGroup is the processor that handles the information on its behalf.
Did you leave your details on a business card and want to see, correct or delete them? Contact that business. You can also write to us and we will point you to it.
Data processing terms between MJGroup and clients: for the content and leads a business collects through its card, the business decides what is collected, and MJGroup processes the information on its behalf, only to provide the service. Anyone with access to the information must keep it confidential. The service providers are Hostinger, Cloudinary and Google Drive, as listed under "Who sees the information". The information is deleted as set out under "How long information is kept".
Who sees the information
We do not sell personal data. The information reaches only these parties:
- The public: everything published on a card is visible to anyone who opens it. Anyone who has the address of an image on a published card can open it. The address keeps working after the card is unpublished or suspended, until the image is deleted, and for up to 30 days after that. Search engines and AI tools can read it, and our default also lets crawlers that collect data for model training read public cards.
- Search engines: when a card is published or changes, we may send its URL through IndexNow. Only the URL is sent.
- The system administrator: Mousa Jacoub can open any business, any client folder and any lead to give service and support and to look into complaints. Opening a business and reading leads are recorded in the log. At this stage clients do not see that log.
- Hosting provider: the service runs on a Hostinger VPS.
- Image provider: the images you upload are stored at Cloudinary, and on public cards the browser loads them directly from there. This means Cloudinary receives the IP address and browser type of people viewing a card.
- Backup provider: encrypted database backups are kept off the server, in Google Drive.
- Authorities: when the law or a court order requires it.
- Other services: the WhatsApp, Waze and social media buttons open a service run by another company, and its own privacy policy applies there.
- Meta, through a business's Meta Pixel: a business can run its own Meta Pixel on its public card. When it does, that business, not MJGroup, is the controller of the information the Pixel collects, and questions about that information go to the business. The Pixel loads only on that business's published card, never in the preview or the dashboard. The browser of the person visiting the card sends directly to Meta Platforms (Facebook): card views and the page address, clicks on WhatsApp, phone, email, save contact, Waze or Google Maps, the fact that the lead form was sent (without what was written in it), the IP address and details about the browser and device. Meta can also receive more if the business turned on such options in its own Meta settings, for example Automatic Advanced Matching, which can send hashed contact details from forms on the page. Meta handles this information under its own privacy policy. The Pixel can also store cookies in the browser, as set out in the cookie policy.
How long information is kept
Apart from backups and server logs, nothing in the system deletes information automatically by age today, so for now we delete it by hand when the period ends. This is how long information is kept:
- Account and business content: while the account is active, and for 12 months after it closes. You can ask us to delete them sooner.
- Images: stored at Cloudinary until you delete them from the dashboard, or until the account is deleted. After deletion, an image can stay reachable from Cloudinary's cache for up to 30 days.
- Leads: until the business deletes them, and for 24 months at most from the day they arrive.
- Session records: a login lasts up to 7 days. Expired records are deleted at the next login to the account.
- Security event log: 24 months from the event.
- Backups: every night we create an encrypted backup of the database only. Each backup stays on the server for 7 days, and off the server in Google Drive for 30 days. It is encrypted before it goes there. Information deleted from the database stays in existing backups until they age out, for up to 30 days.
Transfers abroad
The information is stored on a Hostinger VPS in France, except the images you upload, which are stored at Cloudinary. If that server is outside your country, your information travels there. Encrypted database backups are also kept off the server, in Google Drive.
The European Commission has recognized Israel as providing adequate protection for personal data, and it confirmed that again in January 2024. France is a member of the European Union and a party to Council of Europe Convention 108 on the automatic processing of personal data. For the transfer to the server in France we rely on regulation 2(8)(1) of the Israeli Privacy Protection (Transfer of Data to Databases Abroad) Regulations, 2001, which allows transfers to a database in a country that is a party to that convention. The backups are encrypted before they leave the server.
How we protect the information
Passwords are stored as hashes. The login cookie is httpOnly, so code on a page cannot read it. Clients see only their own businesses.
No system is immune, and we do not promise absolute security.
Your rights under Israeli law
Under the Protection of Privacy Law, 1981, you can:
- See the information we keep about you.
- Ask us to correct information that is wrong, incomplete, unclear or out of date, or to delete it.
- Complain to the Privacy Protection Authority.
Your rights under the GDPR
We have not appointed a representative in the European Union, because the service is aimed at businesses in Israel. Readers in the EU can write to us at into@m-j-group.co.il.
If the GDPR applies to you, you can:
- Get a copy of your information.
- Correct wrong information.
- Delete information.
- Restrict how the information is used.
- Object to use based on legitimate interests.
- Receive the information you gave us in a portable format.
- Withdraw consent.
- Complain to the supervisory authority in your country.
California residents (CCPA)
This section applies to California residents, to the extent the CCPA applies to us. We do not sell personal data or share it for targeted advertising, and we have not done so in the past 12 months.
We collect identifiers (name, email, phone, IP address), internet activity (browser type, request method and path, response status, bytes sent and security events) and content you upload, including images. The information comes from you, and its uses are listed under "Why we use the information".
You have the right to:
- Know what information we collected about you, where it came from, why we used it and who received it.
- Delete information we collected from you.
- Correct wrong information.
- Make a request through an authorized agent.
- Receive the same service after using any of these rights.
Children
The service is not directed at children under 13, and we do not knowingly collect information from them (COPPA). Accounts are for people aged 18 and over.
Public cards are open to everyone and have no age check.
If you learn that we received information from a child under 13, write to us at into@m-j-group.co.il and we will delete it.
Marketing email
Today we send no marketing messages from the system, and it has no service for sending email or SMS. Messages about your account, such as a password reset link, are not marketing.
If we start sending marketing messages, they will follow section 30A of the Israeli Communications (Telecommunications and Broadcasting) Law, 1982 and the US CAN-SPAM Act:
- Consent: we will send only to people who agreed in advance and explicitly, with a separate checkbox.
- Sender identity: every message will name MJGroup, a way to reach us and a physical address: Burj A-Sukkar 1, Shefar'am 20200, Israel.
- Labeling: the Hebrew word "פרסומת" (advertisement) will open the message, and in email it will open the subject line.
- Unsubscribe: every message will include a simple way to opt out. We will stop as soon as we can, and within 10 business days at the latest.
Changes to this policy
When this policy changes, we update the date at the top of the page.
How to contact us
For any privacy question or request: into@m-j-group.co.il, or by mail to Burj A-Sukkar 1, Shefar'am 20200, Israel.
Before acting on a request we may ask you to verify your identity. We will answer within the time the law sets.