Business cards your team can't run out of.

One link, one QR code, one source of truth. Your organisation controls the branding, your people control their own details, and nobody reprints a box of cards because a job title changed.

  • No card details to start
  • Cancel any time
  • Arabic and English included
YottaByte Creative Technologies
SA

Sara Ahmed

Head of Partnerships

Commercial · YottaByte Creative Technologies

Call
WhatsApp
Email
Save to contacts
Share
QR code

About

Ten years building channel partnerships across three continents. Usually somewhere between a client call and a boarding gate.

Tap العربية — the whole layout mirrors, not just the text.

Brand:

Want the real thing? Open a live card page

Reprinted

every time someone changes title, number or office — and the old boxes go in a drawer.

Untracked

you hand out two hundred cards at an event and learn nothing about what happened next.

Inconsistent

three departments, three printers, three slightly different versions of your logo.

Paper cards fail quietly. A digital card that your organisation actually controls fixes all three at once.

Everything a card needs to be useful

Not a link in a bio. A managed asset your organisation owns, in both the languages your customers actually use.

Bilingual, not translated

Name, title and bio each hold an Arabic version alongside the English. Switching flips the whole layout right-to-left and renders in a real Arabic typeface — not a Latin font guessing at glyphs.

Saves to the phone properly

One tap writes a real contact into iOS or Android, Arabic name intact. No app to install, nothing for the recipient to sign up for.

A QR code per person

On the card for screen-to-screen scanning at events, and downloadable as a PNG for badges, posters and slide decks. Scans are counted separately from link clicks.

On brand automatically

Set the logo and brand colours once. Every card inherits them, and text contrast is calculated so a pale brand colour never turns into unreadable white-on-yellow.

You can see what works

Views, contact saves, QR scans and shares — per person and across the team, with a 30-day trend and a save-rate per employee. Visitor IPs are hashed, never stored raw.

Offboarding takes one click

Deactivate a card and the link shows a clean “no longer active” notice instead of a dead page or a stranger's details. The seat frees up for the next hire.

Live the same afternoon

There is no implementation project here. Three steps, and your team is sharing.

  1. 1

    Set up your organisation

    Company name in English and Arabic, your logo, your brand colours. Two minutes, and it becomes the template every card inherits.

  2. 2

    Add your team

    One at a time, or upload a CSV straight out of your HR system. Ten people takes under two minutes, and duplicates are skipped rather than doubled up.

  3. 3

    They start sharing

    Every person gets a live link and a QR code immediately. Invite them and they can add their own photo, bio and links within the limits you set.

For HR and owners

The company owns the card, not the employee

Most digital card tools are built for individuals and bolt on an admin screen later. This one starts from the organisation: you decide what stays fixed, staff fill in the rest, and the limits are enforced in the database rather than just hidden in the interface.

  • Add, edit and deactivate any card in your organisation
  • Bulk import from CSV with per-row error reporting
  • Lock branding so cards stay consistent across the team
  • Let staff edit their own photo, bio and links — and nothing else
  • Invite people by email so they set their own password
  • Team-wide analytics plus a per-employee breakdown
  • Seats, invoices and payment method in one place
  • Pay in AED by card, with your TRN on the invoice

Tenant isolation at the database

One organisation's data structurally cannot be returned to another — enforced by row-level security, not by application code that could be bypassed.

Credentials encrypted at rest

Payment and mail credentials are encrypted before they are stored and never leave the server. Nothing sensitive is exposed to a browser.

Only card fields are public

The public card page reads through a narrow interface. Billing details and tax numbers are unreachable from a page anyone can open.

Questions worth asking

The things buyers actually ask before they commit a whole team.

An admin deactivates their card from the dashboard. The link keeps working but shows a clean "this card is no longer active" message instead of a broken page — so an old business card in someone's wallet never leads to a dead end or to a stranger's details. The seat is freed immediately for the next hire.

No. A card is a normal web page. They open a link or scan a QR code, tap "Save to contacts", and it lands in their phone's address book like any other contact. Nothing to install on either side.

The card holds both languages side by side — name, job title and bio each have an Arabic field. Switching flips the entire layout to right-to-left, not just the text direction, and Arabic renders in a proper Arabic typeface rather than a Latin font's fallback glyphs. If an Arabic field is left empty, that line falls back to English rather than going blank.

Both, and you choose the balance. Admins own the parts that represent the company — name, job title, department, branding. Employees can update their own photo, bio, phone and links. Those limits are enforced in the database, not just hidden in the interface, so an employee cannot rename themselves or change their card URL even by other means.

Download the CSV template, export from your HR system, upload. Column names are matched loosely — "Full Name", "full_name" and "name" all work — and rows whose email already exists are skipped rather than duplicated. You get a per-row report of anything that could not be imported.

Card views, contact saves, QR scans and shares — per employee and across the whole team, with a 30-day trend. QR scans are tracked separately from link clicks, so you can tell what your printed badges and event materials are actually doing. Visitor IPs are hashed, never stored raw.

Each organisation's data is isolated at the database level, not just in application code — a query from one organisation structurally cannot return another's rows. The public card page reads through a narrow interface that exposes only card fields, so billing details and tax registration numbers are unreachable from a page anyone can open.

Yes. Pricing is in AED, and billing is handled in your YottaByte account rather than here.

Stop reprinting. Start in ten minutes.

Fourteen days free, no card details, and your first cards are live before the trial even matters.