Skip to content
1Namecard

Capture

Capture the lead.Keep the consent.

A form on every card that stores the exact wording and version the visitor agreed to, with the placement it came from.

The visitor's formSample data

Share your details with Dana

Your name

Mia Fischer

Company

Harbourline Freight

Work email

m.fischer@harbourline.example

Phone(optional)

Note(optional)

Pricing for 20 reps

I agree that Kestrel Labs may contact me about this request. See the privacy notice.

Send my details to Dana

Stored with the lead: this wording, its version (3), the time and the placement dw27-badge.

In short

1Namecard lead capture is a form on each digital card that records a visitor's name, company, work e-mail and role with the consent wording and its version. It also stores the placement the visitor came through and the buttons they tapped. It sets no cookies and uses no captcha. It gives you the evidence trail. Compliance still depends on your own purposes and notices.

Last updated

What it does.

  • A short form on the card.

    The form asks for Your name, Company, Work email, Phone (optional), Your role and Note (optional), with a consent box. The thank-you screen offers Save contact.

  • Consent, stored with the lead.

    The box uses your wording from Branding. Each lead stores the wording and version the visitor saw, and whether the box was ticked. The lead page shows Consent given and Consent wording shown.

  • Placement and actions come along.

    A link with ?s=badge carries badge to the form, and the lead stores it as its placement. The card remembers which buttons the visitor tapped for the length of the visit, in the browser's session storage rather than a cookie, and sends them with the form.

  • Spam handling without a captcha.

    An invisible bot check runs when the form is sent, so there is no puzzle to solve. Each network address can send 5 submissions in 10 minutes, and a submission that fills in a hidden trap field is not stored. The same e-mail sending the same kind of submission to the same card within 24 hours gets the normal thank-you, and nothing is stored twice.

  • A meeting request in the same flow.

    Book a meeting and Book a call create a lead too, marked Meeting request and scored higher. See scheduling.

  • An alert when a lead arrives.

    The card's owner gets a Telegram message, and an organisation can post to Slack. A follow-up e-mail goes only to visitors who ticked the consent box, only if you switch it on under Email, and only after the visitor confirms their address from a short e-mail.

  • A Leads list you can work.

    Search by name, company or e-mail, filter by card, owner, score band, source and dates, and press Export CSV. Members see only the leads of their own cards. Viewers read but cannot change or export.

No cap

on leads, on any plan

0

cookies and no captcha

50,000

rows per CSV export file

How it works in three steps.

  1. Step 01

    Write your consent wording.

    Edit Consent text and Privacy notice URL. Saving creates a new version.

  2. Step 02

    Test the form.

    Send a test lead from your phone and check the lead page for wording, version and placement.

  3. Step 03

    Work the lead.

    Open Leads, sort by score, set an owner and a next action.

A lead in the adminSample data
MF

Mia Fischer

Head of Sales, Harbourline Freight

Meeting

75

Hot

Lead score out of 100

  • Requested a meeting+30
  • Saved your contact+20
  • Tapped other card actions+10
  • Company is not yet a customer+10
  • Gave a phone number+5
  • Consent wording, version 3, stored with this lead.
  • Owner Dana Reyes. First contact 12 minutes after the lead arrived.
  • Next action: call, Thursday 09:00.

Who it is for.

Limits by plan.

  • Included: No plan caps the number of leads. Leads and meetings are kept until you delete them.
  • Included: A CSV export stops at 50,000 rows per file.

What it does not do yet.

  • Not included: The form's questions are fixed. You can change the consent wording and privacy link, but not add questions.
  • Not included: We do not read organiser badges. Keep the organiser's scanner if you have one.

A GDPR lead capture app: what it gives you, and what it does not.

  • The exact consent wording and version, kept with every lead.
  • Erasure for one person. An admin presses Delete all data for this email on a lead, which removes every lead, meeting request, note and history entry for that address from the live database. With a CRM connected it also asks the CRM to delete the contact, once. Backups taken earlier are not changed, and alerts, e-mails and webhooks already sent cannot be recalled.
  • No cookies on the card, data stored and processed in the EU, and each organisation's data kept apart.
  • The visitor's IP address and browser string stay on the lead or meeting record as evidence, visible to admins only, and are included in backups.

It does not give you a legal basis, a privacy notice or a retention policy. Those are yours. The guides on GDPR at events and consent wording for lead forms explain the basics. They are not legal advice.

A trade show lead capture app that runs on the visitor's phone.

Nothing is installed. The visitor scans, reads the card and types their own details, so there is nothing to retype after the show. The consent line sits next to the button that sends the data.

Questions about this feature.

Is 1Namecard GDPR compliant?

No tool is compliant on its own. 1Namecard stores the consent wording and version with every lead, stores and processes data in the EU, sets no cookies on cards and lets an admin erase one e-mail address. Whether your use is lawful also depends on your purposes, notice and retention. This is not legal advice.

What do you store when someone sends the form?

Name, company, work e-mail, phone, role and note, the consent wording and version, whether the box was ticked, the placement, the buttons tapped and the time. The IP address and browser string are kept too, visible to admins only and included in backups.

Do you use a captcha?

No puzzle. An invisible bot check (Vercel BotID) runs when the form is sent, alongside a limit of 5 submissions in 10 minutes per address, a hidden trap field and a 24 hour duplicate check.

How do I answer a request to delete someone's data?

Open one of the person's leads as an admin and press Delete all data for this email. It removes their leads, meeting requests, notes and history for your organisation from the live database, and asks a connected CRM to delete the contact once. It cannot be undone. Backups taken earlier are not changed.

Try it on your next show.