Privacy notice
Draft, not yet reviewed by a lawyer. The closed pilot runs on this draft (owner answer 9, 4 November 2026); a lawyer reviews it before any public launch. This draft was written from the PEXN code as it stands on 3 November 2026 (the "cards first" model), not from instructions by a lawyer, and it is not legal advice. Every item in [SQUARE BRACKETS] is a fact the owner must supply. The questions this draft cannot answer by itself are listed for counsel in LEGAL-REVIEW-NOTES.md, "Cards first", and the plain map of where the data goes is docs/privacy-cards-first.md.
PEXN is a members-only business-introduction network. You photograph the business cards you are handed and keep them in a wallet. You post asks to the people whose card you have and who have yours, and members introduce each other by hand. This notice explains what we do with personal data, why, for how long, who else sees it, and what you can ask us to do about it.
We have tried to describe the system as it actually is, including the parts that are awkward. Where we keep something longer than you might expect, we say so and say why.
1. Who we are
| The company responsible for your data (the "controller") | [LEGAL ENTITY NAME] |
|---|---|
| Registered address | [REGISTERED ADDRESS] |
| Country of incorporation | [COUNTRY OF INCORPORATION] |
| Company registration number | [COMPANY REGISTRATION NUMBER] |
| Privacy contact | [PRIVACY EMAIL] |
| Data protection officer, if we are required to appoint one | [DPO NAME AND CONTACT, OR "WE HAVE NOT APPOINTED ONE"] |
| Our representative in the European Union, if we are required to appoint one | [EU REPRESENTATIVE NAME AND ADDRESS] |
| Our representative in the United Kingdom, if we are required to appoint one | [UK REPRESENTATIVE NAME AND ADDRESS] |
"Controller" means the company that decides why and how personal data is used, and is answerable for it. For everything that happens inside PEXN, that is us.
Membership is invoiced by a selling entity for your corridor. That entity may not be the same company as the controller named above; it is named on your invoice and listed at [BILLING ENTITIES PAGE OR CONTACT].
Our surfaces are the mobile app, the member website and public site at joinpexn.com, and a staff-only back office at pexn.developeroffice.com.
2. The short version
- Your wallet holds the cards you were handed. When you photograph a card, the photograph and what is printed on it are kept in your wallet, for you. That is true whether or not the person on the card is a member.
- A card of someone who is not on PEXN stays yours alone. No other member can see it, our staff cannot open it, and PEXN never contacts that person. Two things about it reach beyond your wallet, and both are internal: a one-way match key, and a clean drawing of the card that another holder of the same printed card may be shown. Section 5 explains both.
- A member's card can be passed on. Members agree, when they join, that others may keep their card and introduce them with it. If you hold a member's card, you can see its phone number and email. A member is told who holds their card.
- Every card you photograph is read by Anthropic's Claude, in the United States, as soon as you photograph it, and the clean drawing of a card is made by OpenAI, also in the United States. Section 6 lists every company that receives data.
- We never collect, infer or store your age, gender, ethnicity, religion or any similar attribute. The only grouping we keep is the month you joined.
- You can delete your account yourself. Some records are shared with other people, such as an introduction you were part of, and they are not rewritten. Section 9 says exactly what stays.
3. What we collect, and why
3.1 Your own card
- The photograph of your card, front and, if you add one, back. The real photograph is kept as the evidence that the card is yours.
- A clean drawing of your card, made from the photograph by OpenAI and checked twice before anyone sees it: its own reading of the card is compared with ours, and a second model compares the drawing with the photograph. A drawing that does not match is thrown away. The photograph is never replaced and is always available.
- The business fields printed on it: name, company, role, sector, country, city and website, which you confirm. Changing them later makes a new version of the card.
- The phone number and email address printed on it. These are encrypted at rest with a key held outside the database. We also keep one-way fingerprints of them, so the same number or address cannot open two accounts.
- The colours and layout of the card, as a description (for example "dark blue, white text"), so the card looks like yours in every wallet that holds it.
- The proof that the card is yours. To confirm your card, we send a code to the email address or mobile number printed on it (by email, or by SMS where we can), or a member of staff checks it by hand. We keep the result, the method and the number of attempts.
3.2 Your membership account
- Your sign-in address (an email address or a mobile number), stored encrypted with a one-way index so we can find you when you ask for a sign-in code.
- Your country, language, time zone if you set one, and your notification preferences.
- The month you joined. This is the only way we group members. There is no age, no date of birth, no gender, no photograph of you, and no demographic field anywhere in the system.
- Your agreements, each with a date: that you are 18 or over, that the card you confirm is your own, that other members may keep your card and introduce you with it, and that you keep the house rules.
- Sessions and devices: session records, single-use refresh tokens, and the push token of each device you sign in on.
3.3 Your wallet
- The cards you hold: for each one, when it came in and how (a photograph, a QR link, adding someone back, an introduction), whether it is pinned or put away, the stack you scanned it in, one optional line you wrote about the person, and whether the two of you met in person (both photographed the other's paper card within 14 days).
- For a card of someone who is not on PEXN: your photographs of it, what was read from it (name, company, role, website, country, city, the script it is printed in, whether it has handwriting, its colours), its phone number and email sealed so only your account can open them, and up to two match keys (section 5.2).
- For a member's card: a link to that member's own card, which they keep up to date.
3.4 What you do in the network
- Asks and offers you post, who they went to, and their translations.
- Answers and introductions: "That's me", a card handed on, an ask passed to someone, a direct introduction of two people, any line written with them, and the accept that opens contact details.
- Notes from the club: "X has your card", "X added your card back", "X is on PEXN now".
- Thank-you notes, gifts and their notes.
- "Did this work out?": your answers about an introduction you accepted (section 11.1).
- Reports, flags and disputes you raise, and appeals you make.
- A record of what happened, for later checks: which introduction came from which wallet, which cards were in front of you when you looked at your wallet, and which asks you were shown. This record holds identifiers and counts only, never text, names, images or contact details (section 8).
- Derived signals about behaviour, such as the same card image on two accounts, or two members accepting each other repeatedly. These are private, used for fraud review, and never shown to other members.
3.5 Money
Invoices, the amounts, the currency, the tax in them, payments recorded against them, grants, gifts, gifted months and your annual statement. The price band is set by the country on your confirmed card; we do not work it out from your phone number or anything else. Membership is a year, or month by month at one tenth of the year's price. We do not store your billing address or any card or bank details: today you pay by bank transfer against the invoice number, and a member of staff records that the money arrived.
3.6 Technical and security data
- Audit records of every opening of a contact detail, every staff action in the back office, and sensitive member actions such as requesting deletion. Each can carry the account identifier, the IP address, the browser or app, a request identifier and what changed.
- Rate-limiting counters. For logged-out visitors these use a one-way hash of the IP address; the IP address itself is not stored for this.
- Error reports, see section 6.
4. Why we are allowed to do this (lawful bases)
"Contract" means Article 6(1)(b) of the GDPR: we need to do it to give you the membership you asked for. "Legitimate interests" means Article 6(1)(f): we have a real interest, the processing is necessary for it, and we have weighed it against your rights. Where we rely on it, we say the balance.
| Purpose | What is used | Lawful basis |
|---|---|---|
| Running your account, your card, your wallet, asks, answers, introductions, accepts | Sections 3.1 to 3.4 | Contract |
| Reading the cards you photograph and keeping them for you | Card photographs and what is printed on them | Contract, for you. For the person on a card who is not a member: legitimate interests, see section 5 |
| Making and checking a clean drawing of a card | The front photograph; for your own card, both faces | Contract, for your own card. For a card of someone who is not a member: legitimate interests, see section 5 |
| Switching a held card to its owner's own card when the owner joins (the match key) | One-way fingerprints of a personal email or a mobile number with a name | Legitimate interests: members keep the cards they were handed, and a card's owner wants their own card, not a copy, in those wallets. Only one-way fingerprints are kept, and only for personal addresses and mobile numbers |
| Opening a member's contact details to the people who hold their card, and to both sides of an accept | The encrypted phone and email | Contract (members agree to it when they join) |
| Confirming that a card is yours | A code sent to the printed email or mobile | Contract |
| Membership, invoices, renewals, grants, gifts and gifted months | Section 3.5 | Contract; and legal obligation for tax and accounting records |
| Checking asks, answers and lines against the house rules; translating; suggesting who could help; the trust line before an accept | Ask and line text; trust facts | Contract |
| Fraud screening, flag triage, duplicate-account detection, abuse patterns, and the record of what happened | Text of asks, lines and flags; image hashes; one-way fingerprints; counts | Legitimate interests: one person, one identity is the base of a vouched network, and fraud is the main way such a network is abused. We use fingerprints rather than readable values, and a person reviews every block |
| Audit records | Section 3.6 | Legal obligation to keep personal data secure (Article 32); and legitimate interests in being able to show who saw what |
| Push notifications | Device token, notification text | Contract. Your device also asks you, and you can switch it off there |
| Email about money, claim codes and sign-in codes | Email address, the message | Contract; and legal obligation for invoices |
| Public price and coverage pages | Aggregate counts only; anything under 20 shows as "fewer than 20" | Not personal data once aggregated |
We do not ask for your consent as the basis for the core service, because consent you could not realistically refuse would not be real consent. The consents your device asks for, camera and push notifications, can be withdrawn in your device settings at any time.
We never process special category data (health, beliefs, biometrics, sexual orientation, trade union membership, and so on). A business card does not normally contain any, and nothing in PEXN asks for it or infers it.
5. Cards of people who are not on PEXN
This is the most sensitive part of PEXN, so we are direct about it.
5.1 What happens to a card you photograph
- It is photographed and uploaded. The photographs are stored in a bucket created with European Union jurisdiction, with public access switched off.
- It is read at once, before you decide to keep it. Both faces go to Anthropic's Claude in one request. A second, stronger model reads it again when the first is not confident.
- What was read is stored for you. The business fields are stored for your wallet. The best phone number and email are sealed so that only your account can open them.
- Up to two match keys are made (section 5.2).
- It is compared with members' cards. If it is a member's own card, your wallet holds that member's card instead (section 5.4).
- You keep it or not. If you choose not to keep it, the card and its photographs are deleted. The reading by Claude has already happened by then.
- It is drawn when you first open it. The first time you open a card of someone who is not on PEXN, its front photograph is sent to OpenAI, which draws a clean version of it. The back is never drawn for such a card. The drawing is checked twice, as in section 3.1.
Who can see it. Only you. The database enforces this: no other member, and no member of our staff, can open it. Its photographs are served only to you, through short-lived signed links, and every opening is audited. Nobody can see a match key, how many people hold a card, or whether a drawing was reused. PEXN never contacts the person on the card.
5.2 The match key
A match key is a one-way fingerprint (an HMAC) of a personal email address printed on the card, or of a mobile number printed on it together with the name. Role addresses such as info@ or sales@, and landline numbers, never get one. A match key cannot be turned back into the address or the number.
It is used for one thing: if the person on the card joins PEXN and proves their card with a code sent to that same address or number, every wallet holding a photograph of that card switches to the member's own card. A match counts only when exactly one person fits.
5.3 The reused drawing
If another member photographs the same printed card, they may be shown the drawing already made instead of a new one. This happens only when all of these are true:
- it is the front of the card;
- the reading found no handwriting;
- the card is printed in Latin script;
- the name, company, website, phone and email read from both photographs all match; and
- both readings passed their checks.
The drawing keeps a transcription of the business fields only: name, company, role, website, country and city. It does not carry the holder's photograph, line or contact details.
5.4 If the person joins
When the person proves their card, the wallets that held a photograph of it switch to their own card, and each holder gets one note: "X is on PEXN now". The new member's "Who has my card" then lists those holders. Each holder keeps their own photograph as their evidence.
5.5 Our position, and the notice problem, stated plainly
For these cards PEXN is the controller: we decide that the card is read, what is kept, that a match key is made and that a drawing may be reused. The member who photographed the card holds it as their own record of a card they were handed, as they hold the paper.
Article 14 of the GDPR says that when we obtain personal data about someone from someone else, we should tell that person. We do not contact the people on these cards, by design: PEXN never contacts a person who is not a member, and we usually have no way to reach them that they gave us. We rely on Article 14(5)(b), that individual notice would take disproportionate effort, and we take the measures that provision asks for: this public notice, the data kept to what the holder needs, nobody but the holder able to see it, and a removal route (section 5.6).
Our honest view: this is the part of PEXN most open to argument. It is listed for our lawyer in LEGAL-REVIEW-NOTES.md ("Cards first", CF-1 to CF-3), including whether the match key and the reused drawing need more than this.
5.6 If a card of yours is in PEXN and you are not a member
Write to [PRIVACY EMAIL] with the email address or mobile number printed on your card, and the name printed with it. A member of staff then:
- removes your match keys from every card in PEXN that carries them, so no wallet will ever be switched through them;
- stops any drawing of those cards being shown to another holder; and
- records those keys as forgotten, so a card of yours photographed later is not given a match key or a reusable drawing again.
The members who photographed your card keep their own photographs and readings of it, as they keep the paper card. That is our current position and it is one of the questions we have put to our lawyer. We will answer within one month. We may not be able to tell you *which* members hold your card, because that is their personal data too; we will decide that case by case and explain our reasoning to you.
6. Who else sees your data
6.1 Other members
- People who hold your card see your card, its phone number and its email. That includes anyone who photographed your paper card, added it from your QR link, was added back by you, or was given it in an introduction.
- You are told who holds your card. Once the holder's own card is proven, you get one note per holder, ever ("X has your card"), at most 30 a day from any one holder; and "Who has my card" lists every member who holds your card, including those who have put it away. It never shows what they did with it.
- Your QR link shows nothing personal to someone who is not signed in: only that the link works and how to join.
- An ask reaches the people whose card you hold and who hold yours, neither having put the other's card away, or the few of them you choose. Anyone they pass it to, or whose card they hand you, can read it too. So can our staff when they check it, and Claude, which checks every ask.
- An accept opens contact details both ways between the asker and the person introduced.
6.2 Companies that process data for us
We do not sell personal data, we do not share it for advertising, and no analytics tool receives card text or contact fields.
| Who | Where | What they receive | Why |
|---|---|---|---|
| Anthropic PBC (Claude) | United States | Both faces of every card photographed, member or not, before the holder decides to keep it; the photograph and the drawing side by side for the check; the text of asks, answers, lines, flags and thank-you notes; trust facts | Reading cards, checking drawings, checking and translating asks, suggesting who could help, fraud screening, flag triage, the trust line before an accept, screening lines and thank-you notes |
| OpenAI | United States | The front photograph of a card of someone who is not on PEXN, the first time its holder opens it; both faces of a member's own card [CONFIRM OPENAI DATA-RETENTION AND TRAINING TERMS; THE REQUEST SETS NO store PARAMETER] | Drawing a clean version of the card |
| Cloudflare, Inc. | United States company; the card-image store is created with European Union jurisdiction; database caching is switched off so one member's data can never be served to another | Hosting of the API, websites and back office; card images; a work queue that carries identifiers only; DNS, CDN and firewall | Running the service |
| Google LLC (Firebase Cloud Messaging) | United States | Your device's push token and the notification text, which never names anyone on the lock screen | Push notifications |
| Functional Software, Inc., trading as Sentry | United States | A stripped error report: route, method, request identifier, release and the error. User, headers, cookies, query string and body are dropped before sending, and the rest is redacted | Finding and fixing faults |
| [MAIL SERVER HOSTING PROVIDER] (our own Postal mail server) | [MAIL SERVER COUNTRY] | Email address and message: invoices, receipts, statements, membership notices, sign-in codes and card codes sent to a printed email | Sending the few emails we send |
| FitSMS | Sri Lanka | A mobile number and a code: sign-in codes and card codes sent to a printed mobile | Text messages in the Sri Lanka corridor |
| [DATABASE HOSTING PROVIDER] | Primary in Helsinki, Finland; standby in Germany | Everything in the database | Running the service |
| Backblaze, Inc. (encrypted database backups) | United States region | Encrypted backups of the database | Disaster recovery. This conflicts with our statement that European members' data stays in Europe; see section 7 |
| [BILLING PARTNER OR PAYMENT PROVIDER, PER CORRIDOR] | [COUNTRY] | Not engaged yet | Collecting membership |
6.3 Our staff
Staff see data in the back office according to their role. No member of staff can open a member's encrypted contact details, or any card of someone who is not on PEXN. Staff do read asks they check, flags and reports, "Did this work out?" answers, and the record of what happened (section 3.4). Every staff action is recorded.
We will also disclose data where the law requires it (a valid court order, a tax investigation, a regulator) and where we need to defend a legal claim. If an authority asks for member data, we will tell the member unless we are forbidden to.
7. Sending data outside your country
Our database is in the European Union (primary in Finland, standby in Germany), and card images are in a bucket created with European Union jurisdiction. Anthropic, OpenAI, Google, Sentry and Cloudflare's parent company are in the United States, and encrypted database backups are in a United States region.
For each of those transfers we rely on:
- the Standard Contractual Clauses adopted by the European Commission, in our contract with each company; and
- where the company is certified, the EU–US Data Privacy Framework [CONFIRM WHICH OF ANTHROPIC, OPENAI, GOOGLE, SENTRY, CLOUDFLARE AND BACKBLAZE ARE CERTIFIED]; and
- a written assessment of each transfer [TRANSFER IMPACT ASSESSMENT, TO BE COMPLETED], with the measures in this notice: contact details encrypted, nothing personal in error reports, and model decision records scrubbed of contact values before they are stored.
The backup conflict, stated honestly. We say European members' data stays in Europe, and our encrypted backups sit in a United States region. The key that protects contact details is not in them, but this is still a gap. It is a blocking item in LEGAL-REVIEW-NOTES.md, to be closed before this notice is published to European members.
Before we open a corridor to a new country we review it against the data protection law at each end, including the GDPR, Sri Lanka's PDPA and India's DPDP Act.
8. How long we keep things
These periods come from the running code, not from an intention.
| What | How long |
|---|---|
| Your own card: photographs, drawings, fields and hashes | While your account lasts; deleted when it is deleted. Older versions of a card you replaced are kept today; see LEGAL-REVIEW-NOTES.md |
| A card you photographed of someone who is not on PEXN (photographs, reading, sealed contacts, match keys) | No time limit. Until you remove it from your wallet, you delete your account, or the person joins and proves the card (your wallet then holds their card; your photograph stays as your evidence) |
| A card you photographed and chose not to keep | Deleted at once with its photographs (the reading by Claude has already happened) |
| A clean drawing of such a card | While any wallet uses it; deleted when none does |
| A match key a person asked us to forget | Removed from every card at once; the record that it is forgotten is kept, so it is never made again |
| Your encrypted phone number and email | Until your account is deleted |
| Sign-in and card codes, sessions | Codes a day after use or expiry; sessions and spent refresh tokens 30 days; all of it on deletion |
| "Did this work out?" answers | [RETENTION PERIOD]. Only staff can read them |
| The record of what happened (which introduction came from which wallet, wallet views, asks shown) | 24 months; on deletion your identifier is removed from it |
| Thank-you notes and replies | The text 30 days after it was written; the record that it happened stays |
| A note written on a gift | 30 days after the gift is delivered or declined |
| Notifications | 90 days |
| AI decision records (touchpoint, prompt version, model, confidence, a fingerprint of the input, the redacted output, cost) | 24 months, then reduced to the cost figures. Contact values are scrubbed out before anything is written |
| Behaviour signals for fraud review | Rebuilt continuously; stale ones deleted hourly; all purged when an account is deleted |
| Invoices, payments, receipts, gifts and gifted months | As long as tax law requires in the corridor: [RETENTION PERIOD PER CORRIDOR]; kept after deletion against an anonymous marker |
| Introductions, accepts and credit | Indefinitely. They are a shared record of what two people did; see section 9 |
| Email send records | No automatic deletion today. Our mail server also keeps the message for [POSTAL RETENTION PERIOD]. Both are open items in LEGAL-REVIEW-NOTES.md |
| Error reports at Sentry | [SENTRY RETENTION PERIOD] |
| Our security audit record | Indefinitely today, including the original account identifier and IP address. See section 9 |
9. Deleting your account, and the limits of it
You can delete your account yourself, from the app or the member website, confirming with a code sent to your sign-in address.
How it runs. We hold the request for 14 days, during which you can cancel it. On day 14 it runs, and deletion is complete within 30 days of your request. Images are removed from storage by a separate job, and deletion is not complete until that has run.
What is deleted:
- your cards, their photographs, their drawings and the details printed on them;
- your contact details;
- your whole wallet: every card you held, including every card of someone who is not on PEXN, its photographs and its match keys, and a drawing nobody else uses;
- your stacks, lines, notes from the club, notifications, devices, sign-in details and sessions;
- thank-you notes, replies and gift notes you wrote;
- your verification records and the behaviour signals we derived about you;
- any gifted months you had not used (they cannot be cashed or refunded).
Asks you posted are closed, and introductions waiting on you are dismissed.
What stays, and why.
- Members who photographed your paper card keep their own photograph of it, as they keep the paper. It becomes a card of someone who is not on PEXN in their wallet, with no match key.
- Introductions and accepts that already happened. They are a record other people share. Your place in them is replaced by an anonymous marker; the chains keep their shape.
- The credit those accepts earned, against the same marker.
- Invoices, payments and gift records, against the same marker, as long as tax law requires.
- The text of asks you posted, as context for the chains that hung off them.
- Our security audit record, including your original account identifier and the IP address you acted from. We think keeping it is justified for security and fraud investigation, but it is not complete erasure, and choosing a retention period for it is a recorded open item.
If you want an erasure that reaches the audit record, write to [PRIVACY EMAIL]. We will consider it and tell you our reasoning and, if we refuse, your right to complain.
10. Your rights
If you are in the European Union, the United Kingdom, or another country with similar law, you have the rights below. We answer within one month, at no charge.
| Right | What it means here |
|---|---|
| Access | A copy of what we hold about you. Write to [PRIVACY EMAIL]; this is not yet a self-service button |
| Rectification | Correcting what is wrong. Card fields freeze once you confirm them, so a correction makes a new version of the card |
| Erasure | Delete your account yourself, with the limits in section 9 |
| Restriction | Ask us to pause processing while a complaint or correction is resolved |
| Objection | Object to anything we do on legitimate interests: the match key, the reused drawing, fraud screening, abuse patterns, error reports. We will stop unless we can show reasons that outweigh yours, and explain either way |
| Portability | The data you gave us, in a machine-readable form |
| Not being subject to a decision made only by a machine | See section 11 |
| Withdrawing a device permission | Camera and push notifications, in your device settings |
| Complaining | To us at [PRIVACY EMAIL], and to a supervisory authority: [LEAD SUPERVISORY AUTHORITY AND ITS CONTACT], or the authority where you live or work |
If you are not a member and a card of yours is in PEXN, see section 5.6. You have the same rights.
11. Decisions made with AI, and where a person comes in
Claude, from Anthropic, reads cards, checks drawings, checks and translates asks and lines, suggests who could help, screens for fraud, triages flags and reports, and writes the trust line shown before an accept. OpenAI draws clean cards. Nothing is decided by a model alone:
- Your card. The model proposes what is printed on it; you confirm it. A drawing that does not match the photograph is thrown away, and the photograph stays.
- Low confidence escalates. Every decision carries a confidence score. Below 0.7 a stronger model runs again, and if it is still unsure, a person reviews it.
- Asks and lines. A borderline ask is returned to you with the reason and a suggested rewrite. A refusal names the rule it broke.
- Enforcement. Warnings, limits, suspensions and removals are decided by staff. Every flag and report goes to a person, with a 72-hour target.
So we do not believe anything in PEXN is a decision "based solely on automated processing" in the sense of Article 22. Even so, every automated refusal or enforcement step can be appealed to a person, and you are told the reason.
We log every model decision (touchpoint, prompt version, model, confidence, a fingerprint of the input and a redacted output) for 24 months. Contact values are scrubbed out before it is written. We do not use your data to train AI models, and our agreements with Anthropic and OpenAI say it is not used to train theirs [CONFIRM AGAINST THE SIGNED ANTHROPIC AND OPENAI TERMS].
11.1 "Did this work out?"
About a week after you accept an introduction, and once more about a month later if you said you had talked or not yet, we ask how it went. Your answer is never shown to the people involved, and it never appears as "a dispute is under review" to anyone. If you say something was wrong, a member of staff looks at it, helped by Claude. When you say which person it was about, the report may count in the private signals we use to spot fraud; when you are not sure, it is filed against no one and staff decide. A dispute you raise on an accept is a separate step, and that one is shown as under review while it is open.
12. How we keep it safe
- Contact details are encrypted, each record with its own key, wrapped by a master key held outside the database. A card of someone who is not on PEXN is sealed for its holder alone.
- Card images are never on a public address. They are served only through signed links that expire within minutes, and every opening is audited.
- The database enforces the rules, not only the app. Row-level security is on and forced on every table, so a bug in the API cannot show one member another member's data. Introductions, accepts, credit, gifted months and the audit record are append-only.
- Caching that could cross between members is switched off on the database connection pool.
- Sign-in is a one-time code, not a password. Staff passwords are strongly hashed with a secret pepper. Refresh tokens are single-use.
- No analytics tool, anywhere, receives card text or contact fields.
No system is perfectly safe. If a breach puts you at risk, we will tell the supervisory authority within 72 hours of becoming aware of it, and we will tell you.
13. Children
PEXN is a service for people in business, and you must be 18 or over to join. You confirm that when you join. We collect no date of birth and no age, so we cannot check it beyond that. If we learn that someone under 18 has joined, we will remove the account.
14. Cookies and tracking
The public site and member website use no advertising cookies, no tracking pixels and no third-party analytics. The member website sets a session cookie so you stay signed in; it is HttpOnly, Secure and SameSite, and scoped to the member area. The app stores your session on your device. Nothing in PEXN follows you to other websites.
15. Changes to this notice
If we change something that matters (a new processor, a new purpose, a longer retention period), we will tell members by push notification or email before it takes effect, and keep the previous version available on request. The version and date at the foot of this page is the authoritative one.
16. Complaints
Write to us first at [PRIVACY EMAIL]. We would rather fix it than argue about it.
If we do not resolve it, you can complain to a data protection supervisory authority. Ours is [LEAD SUPERVISORY AUTHORITY AND ITS CONTACT]. You can also complain to the authority where you live or work, or go to court.
PEXN — Progressive Exchange Network
Operated by [LEGAL ENTITY NAME], [REGISTERED ADDRESS].
Version: privacy-2026-11-03-cards-first-draft-1 (draft for the lawyer)
Last updated: 3 November 2026