GDPR worries when you sell to cafes
Could you show where each contact came from if someone asked? Here is how people who sell to cafes fix it.
Could you show where each contact came from if someone asked?
Rules such as the GDPR expect you to know where personal data came from and to respect objections. With loose spreadsheets that is hard to prove.
It hits harder when you sell to cafes. Cafes are often owner operated with a small team, and the owner is usually behind the counter or the coffee machine. They buy coffee, milk, cakes and equipment regularly, and switching supplier depends on taste, service and a good personal relationship.
Uncertainty makes you hold back on outreach, or take risks you would rather avoid. A request to see or delete data becomes a scramble.
Source, date and opt-out on every record.
Riftjaw keeps the source and date on every record and has an opt-out register. Unsubscribed contacts are never mailed again, and you can export or delete a contact on request. Data stays on your account's own server; this is not legal advice, but it gives you the records to work with.
- Fields that fit cafes, such as coffee brand
- Email prefixes that fit, like hello@, info@, coffee@ and orders@
- Status, tags and a segment on every record
Fixing it in Riftjaw
- Import with a source. Every imported record keeps where and when it came in.
- Respect opt-outs. Unsubscribes land in the opt-out register and are skipped in every campaign.
- Handle requests. Export or delete a contact when someone asks.
Other walls when prospecting cafes
Cafes and restaurants blur together in scraped listings.
Use a field for business type and a saved filter so your cafe campaign only reaches cafes.
Owners reply by phone or in person, so email history is incomplete.
Add notes to the contact after every call or visit and update the status by hand.
You pitch the same cafe twice because two reps kept their own spreadsheet.
Everyone works in one database with duplicate checks on import and unlimited users on an account.
Fields worth recording for cafes
Any column in your import can become a field. These are the ones worth keeping for cafes.
| Field | Why it helps |
|---|---|
| Company name | The key field. Duplicates are checked on it or on the website. |
| Website | Needed to derive an email when the export has none. |
| Coffee brand | The roaster they use tells a roaster or machine supplier where they stand. |
| Food offer | Cafes that serve food buy from bakeries and food wholesalers. |
| Seats | Size shows likely volume of coffee and cups. |
| Machine | The espresso machine they run matters for service and replacement offers. |
| Takeaway share | High takeaway volume means more cups, lids and packaging. |
Questions people ask
Import a list of cafes from public listings, add fields for coffee brand and machine, and put the cafes not using your beans yet in their own segment. Then send a short campaign offering a tasting.
Yes. Add a note on the contact after each visit and change the status. Email history is logged automatically next to your notes.
If your file has an email column, that wins. If it only has websites, tick the prefixes you want, such as hello@, info@, coffee@ and orders@, and Riftjaw derives addresses from each domain. Derived addresses are good guesses, not verified, so start with small batches.
Yes. The Free plan runs the whole pipeline on one list with small campaigns, and you do not need a credit card. Move to Pro when you want more lists, segments and bigger campaigns.
Build a database you own
Create your account, import your first list and see it turn into records you can work.
No credit card · cancel any time · your data stays yours