Version of 7 November 2026. It describes what the application actually does on that date, and what is planned (marked “soon”).
1. In short
- Teewal is responsible for your data. European law (GDPR) applies, even when data is processed in Africa.
- We collect the minimum needed to carry out your job and keep the proof.
- Your contact details stay protected: the partner only sees the job.
- Each agent has an agent number (for example TW-A-7KQ4M2). Teewal only ever shows clients, their relatives and recipients this number, never the agent's name, photo, phone or email. Names written in the messages exchanged are not filtered. Only Teewal can link this number to the person.
- Teewal does not ask you for any health data; do not write any in discussions. For an appointment, Teewal only sells the accompaniment; any care and its booking take place with a third party (platform or clinic), which sends us nothing.
- Partners' identity documents are processed in Africa and deleted after the check. Teewal only keeps the result.
- No automated decisions: a person in the team decides.
- The Teewal Assistant is an automated assistant that runs on our own servers, in the European Union. It uses no external artificial intelligence service: your messages are sent to no other company. It does not keep your conversations after the end of your visit (unless you ask to speak to a person).
- Teewal local operators, bound to Teewal by contract, carry out checks on site and may receive and then hand over original documents, under seal, for 72 hours at most.
- No advertising, no sale of data, no advertising trackers.
2. Who is responsible
Data controller: Hakkilo SAS, which operates the Teewal brand, an SAS (société par actions simplifiée, a French simplified joint-stock company), registered office 122 rue Amelot, 75011 Paris, SIREN 131 536 047. Details in the Legal notice. Privacy contact: [email protected]. Data protection contact person: they answer at the privacy address above. At launch, the volume of identity data processed remains limited, and Teewal does not ask for health data: appointing a data protection officer (DPO) does not yet appear to be mandatory (GDPR, art. 37.1.c: processing “on a large scale”). Teewal will review this every year and as soon as the volume increases.
Teewal is the data controller for all the data described here, including data processed in Africa by its processors (GDPR, art. 3.1).
3. The people concerned
Clients · members of a family file · relatives accompanied or visited · referred friends · partners (agents, professionals) · Teewal local operators · partners' references · people who hand over or receive an original document · people met on site · visitors to the website and the demo.
4. What we do with your data, and why it is allowed
| # | Why (purpose) | What data | Legal basis (GDPR) |
|---|---|---|---|
| 1 | Creating and securing your account, signing you in | Email, language, sessions, sign-in logs; if you choose Google, Apple or Facebook: your account identifier with that provider, the email received and whether it is verified, first name (see below) | Contract (art. 6.1.b); legitimate interest in security (6.1.f) |
| 2 | Receiving your request, preparing a quote, carrying out the job | Need described, places (where you live, where to act), person to meet, references of a document, exchanges | Contract (6.1.b) |
| 3 | Payment, payment in shares, refunds | Amount, currency, status; Stripe or PayPal identifier. We do not see your full card number | Contract (6.1.b); legal obligation for accounting (6.1.c) |
| 4 | Invoices and accounting | Name, billing address, amounts | Legal obligation (6.1.c) |
| 5 | Proof of the job and vault | Dated photos and their fingerprint, signed reports, log of steps, documents you upload | Contract (6.1.b) |
| 6 | Job discussion and moderation | Messages, attachments, warnings, reports | Contract (6.1.b); legitimate interest: security, prevention of circumvention and fraud (6.1.f) |
| 7 | Family file | Organiser, members (email), relative followed (name and town), shares paid | Contract (6.1.b); the family's legitimate interest in organising itself (6.1.f) |
| 8 | Accompanying a relative to an appointment | Date, time of departure from home and time of return, agent number of the agent. Neither the type nor the place of the appointment: the agent receives the destination by phone | Contract (6.1.b) |
| 10 | Referral | Code (drawn at random or chosen), referrer–referred friend link (masked for the referrer, who sees an initial only), credits, number of invitations sent | Contract (6.1.b) |
| 10 bis | Referral invitations by email, on your initiative | Addresses you enter (5 at most): used for this sending only, then erased, never reused or kept; your first name and the initial of your surname appear in the message, together with Teewal's identity, a link to this policy and an opt-out link. An encrypted fingerprint of the pair (you, address) prevents the same person being invited twice within 12 months. You must only invite relatives who agree to receive it | Legitimate interest of the user and of Teewal in recommending the service (6.1.f), a referral practice accepted by the CNIL (the French data protection authority) when the sending comes from the user |
| 10 ter | Objection to invitations (“stop receiving invitations”) | Encrypted fingerprint of the address (HMAC with a secret key, kept outside the database), never the address itself: it is used only to stop sending invitations to that address | Obligation to respect the objection (21.2); legitimate interest (6.1.f) |
| 10 quater | Prevention of referral abuse | Encrypted fingerprint of the payment method (card fingerprint provided by Stripe, PayPal account), encrypted fingerprint of the IP address at sign-up with a code, referral log (without email address) | Legitimate interest: combating referral fraud (6.1.f) |
| 11 | Ratings and reviews (editable for 30 days, displayed for 2 years) | Rating, review, short name of the author | Contract (6.1.b); legitimate interest (quality of the network) |
| 12 | Partner verification | See § 6 | See § 6 |
| 13 | Partner payments (wallet, withdrawals) | Earnings, withdrawals, withdrawal method (number masked on display) | Contract (6.1.b); legal obligation (6.1.c) |
| 14 | Service emails | Email, content of the message (without the content of discussions) | Contract (6.1.b) |
| 14 bis | Notifications on the browser or the phone, if you turn them on | Browser: the browser's subscription address and keys (Web Push), browser type. iPhone or Android app: device token and device type (iPhone or Android). Quiet hours, time zone, preferences. The text sent stays neutral (type of event and job reference) | Contract (6.1.b) |
| 14 ter | Location, only when it is needed | "My position": coordinates of the place you indicate, only when you tap the button. Agents: location on arrival at and departure from a task, and place of proof photos. Never continuous tracking, never in the background | Contract (6.1.b); legitimate interest: proof of the job |
| 15 | Human help on WhatsApp | WhatsApp number, messages | Your choice to use this channel; legitimate interest (6.1.f) |
| 16 | Demonstration | Fictitious test accounts, technical log | Legitimate interest (6.1.f) |
| 17 | Defence in the event of a dispute | Elements of the file concerned | Legitimate interest (6.1.f) |
| 18 | Audience measurement | None at present | — |
| 19 | Teewal Assistant: answering your questions, helping you prepare your request, guiding the partner in their report (see § 5 bis) | Messages of the current conversation, page viewed, language; for the partner, the boxes ticked and the findings they enter themselves | Contract and pre-contractual measures (6.1.b) |
| 20 | Improving the Assistant and ideas for new services | Anonymous counters only: topic of the question, “question not recognised”, language, page. No text, no account, no IP address | Legitimate interest (6.1.f); anonymous data, outside the GDPR once aggregated |
| 21 | Receiving and handing over an original document (see § 7.2 bis) | Type of document (without its number), declared value, seal number, photos of the closed seal, name of the person handing over and of the person receiving, handover code, times and position at each step | Contract (6.1.b); legitimate interest: proof of custody (6.1.f) |
| 22 | Relationship with Teewal local operators | Identity, professional registration, insurance certificate, jobs, positions at the start and end of each job (no continuous tracking), payments | Contract (6.1.b); legal obligation for payments (6.1.c); legitimate interest: security and proof (6.1.f) |
No advertising profiling. No sale or rental of your data.
Signing in with Google, Apple or Facebook (optional). You can always sign in with a simple link received by email. If you prefer “Continue with Google”, “Continue with Apple” or “Continue with Facebook”:
- Purpose: creating your account and signing you in without a password (purpose 1 above; contract, art. 6.1.b).
- What we receive: your account identifier with that provider, your email address and whether the address is verified, your first name. Nothing else: no photo, no friends list, no contacts, no posts. The access token given by the provider is used only once, during sign-in, and is never kept.
- Apple: you can hide your address; we then receive a private relay address that forwards our emails. Apple only sends your first name at the first sign-in.
- Facebook, or any address that the provider does not host itself (for example a work address used with Google or Apple): we first send you a link to confirm your address; the account is only opened or linked after this link. If someone had opened an account at your address in this way, their sign-in methods are removed as soon as you confirm the address, and we tell you.
- Existing account: if the verified address matches a Teewal account, nothing is linked without your agreement, confirmed by a link sent to that address.
- Your choices: in “My sign-in methods”, you link or unlink each provider at any time (you always keep at least one way to sign in). Unlinking erases the identifier on our side.
- Only the provider you choose is contacted, at the moment you click. It processes your sign-in under its own policy (Google LLC / Google Ireland Limited; Apple Inc. / Apple Distribution International; Meta Platforms Ireland Limited), as controller of its own processing.
- Teewal team accounts sign in by email link (social sign-in is only open to them through an internal setting).
5. Health appointments: Teewal knows nothing about them
Teewal does not ask you for any health data; do not write any in discussions. For an appointment, whether administrative, banking, family or medical, Teewal only sells accompaniment by an agent: they come to collect your relative, accompany them and bring them back.
- We record neither the type nor the place of the appointment, nor the name of a professional. The agent receives the destination by phone.
- The proof is limited to: “Accompaniment completed: left home at such time, returned at such time”. No place of arrival, no photo of the place.
- To book a medical appointment, Teewal displays a simple link to an appointment platform of the country or a list of clinics. The link contains no data about you or your relative, and we record neither the click nor your choice. The platform or clinic is solely responsible for the booking, the care and the medical data; you pay it directly.
- Date reminders: only “Appointment”, with no further detail.
- On an accompaniment job, words that reveal care are masked before being stored. On other jobs, discussions are not filtered: if you still write health information there, it follows the duration of the discussion (§ 9), and you can ask us to remove it at the privacy address.
- The Teewal Assistant refuses medical information: if it recognises health information in a message, it asks you not to write it, does not carry it over into any form or report, and masks it if the conversation is passed on to a person in the team.
5 bis. The Teewal Assistant
What it is. An automated assistant: a program, not a person. It relies on a base of answers written by Teewal from the content of the platform, and on a small language-understanding model (an open-source artificial intelligence program) that is used only to recognise what your question is about. The whole system runs on our servers, in the European Union (Netherlands).
What it does not do.
- It sends your messages to no other company: no external artificial intelligence service (neither OpenAI nor any other). There is therefore no transfer and no processor specific to the Assistant, apart from our host (§ 7.3).
- It is not used to train an artificial intelligence model.
- It makes no decision about you: it does not set prices (only the quote issued by Teewal is binding), does not accept or refuse a request, does not rate partners and does not choose who carries out a job.
- It does not write the report in place of the partner: it presents them with a list of points to check (checklist); the partner ticks and writes their findings themselves, then signs.
- When a question falls outside its scope, it says so and offers you the chance to speak to a person.
Retention. The conversation is kept only for the duration of your session (24 hours at most), then it is erased. Only anonymous counters remain (row 20 of § 4). Exceptions:
- if you choose “Speak to a person”, the conversation (with health information masked) is passed on to the team and kept as an exchange with customer service (§ 9);
- what you send yourself (a request, a submitted form, a signed report) follows the retention period of the request or the job.
6. Partner identity verification
This part concerns agents. It does not concern clients.
6.1 Why. To protect client families and the people visited, prevent fraud and identity theft, and comply with asset-freezing measures.
6.2 The steps.
- Versioned agreement and declaration: trade, country, type of document, declaration of a prominent public function (politically exposed person, PEP).
- Phone and email.
- Trade documents (professional verification): for a surveyor, a notary or another regulated profession, registration with the professional Order or Chamber, diploma; for a driver, driving licence, vehicle registration document, insurance.
- Two references (outside the family), called by the team.
- Proof that the identity document is yours, at your choice:
- video call with the team, never recorded;
- or meeting with a confirmed agent (they only see your first name, the initial of your surname and your neighbourhood; they take a photo of the place, with no face or identity document);
- soon, and always optional: a selfie with a movement challenge (see 6.5).
- Screening against the official sanctions lists.
- Decision by a person in the team.
6.3 Place of processing and what we keep.
- At present, the application neither receives nor keeps any image of an identity document, nor any document number.
- When the “Teewal Vérif” service opens, your documents will go directly from your phone to this service hosted in Africa. They will be read in memory as far as possible. If a person needs to review them, they are kept encrypted in the same region, then deleted upon the decision, or at the latest 72 hours after upload. Each deletion is recorded in a log.
- Teewal only keeps the result: status, date, reason, score, signals (valid / to be confirmed), expiry date of the document, and “duplicate yes / no”. The only exception, described below: an encrypted fingerprint of the document number, kept in Africa, used only to prevent the same document from being used for two accounts.
- To detect that the same document is being used for two accounts, the African service keeps a secret-key fingerprint of the document number (HMAC). Without the key, the number cannot be recovered. It is nevertheless pseudonymised personal data, kept only to combat fraud. It is kept for the duration of the relationship and 1 year afterwards, or 5 years after a refusal for fraud.
6.4 Legal bases.
| Processing | Basis |
|---|---|
| Identity document, consistency, duplicates, references, visit, video call | Legitimate interest: safety of clients and of the people visited, fraud prevention (art. 6.1.f); pre-contractual measures (6.1.b) |
| Trade documents | Contract (6.1.b); legitimate interest (6.1.f) |
| Screening against the EU and French freezing lists (which incorporate the UN lists) | Legal obligation (6.1.c): any legal entity operating in France must apply freezing measures without delay (French Monetary and Financial Code (code monétaire et financier), art. L562-4) |
| Screening against the UN and OFAC (United States) lists | Legitimate interest (6.1.f) |
| Selfie and face comparison (soon) | Explicit and separate consent (art. 9.2.a) |
6.5 Biometrics (soon, optional).
- If you choose the selfie, a program compares your face with the one on the identity document and checks that you are actually present. This is biometric data (art. 9).
- We ask for your express and separate consent, which you can withdraw at any time.
- You can always choose the video call or the meeting instead, without losing time or access to jobs.
- Face templates are never stored: they are calculated, compared, then erased from memory.
- The program never refuses on its own: it assists the person reviewing.
6.6 Screening against sanctions lists. Your name is compared every day with the official lists: UN, European Union, OFAC (United States) and the national register of asset freezes of the DG Trésor (French Treasury). A similarity only gives a “possible match, to be confirmed”; we keep the score and the public reference of the list entry, not your date of birth. A match is only confirmed by two different people in the team; it results in the account being frozen.
6.7 Human decision and appeal. No refusal is automatic. A refusal or a confirmed sanction requires two reviewers and a reason. You may present your point of view and contest it within 30 days by replying to the decision message (GDPR, art. 22).
6.8 Informing references. The people you give as references receive a message before the call. Their name and phone number are erased 30 days after the decision.
7. Who receives your data
7.1 Within Teewal. Only the people who need it, with logged access. Verification reviewers have separate rights.
7.1 bis Agent number. Teewal gives every agent, operator or professional who carries out tasks a unique number (for example TW-A-7KQ4M2). The number is drawn at random: it does not come from the name, the email or the phone. It is pseudonymised data: only Teewal can link the number to the person. Head office does so only when needed (complaint, safety, accounting, request from an authority), and every search is written to the audit log. Country staff see an agent's name only for the jobs of their country. The agent's name appears only where the law requires it: their self-billing invoices (with their number), which the client never receives, the author's statement an agent signs electronically, which carries their name like any electronic signature, and the power of attorney a client signs: it names the person who will act on their behalf, that is the agent (their legal name, as verified by Teewal on their identity document, and their agent number) or the partner firm doing the job (its company name, profession and representative). This name appears only in the text of the power of attorney (the screen where the client reads it, the frozen PDF, then the signed PDF); it appears neither on the public verification page nor in the evidence log.
7.2 Between users (“minimum needed”).
- The partner sees the job: place, purpose, person to meet. Not your full name, nor your phone number, nor your budget, nor your other property. Your name appears only when the law requires it (power of attorney, official report (constat)).
- Teewal shows you about the partner: their agent number (“Agent TW-A-7KQ4M2”), trade, rating and “verified” status. Teewal never displays their name, photo, phone or email, whether in the application, on the shared link or on a delivery tracking page. Names written in the messages exchanged are not filtered. Exceptions: the statement they sign electronically carries their name, and the power of attorney you sign names them, or their firm (article 7.1 bis).
- Members of the family file: see the Terms of use, article 11.
7.1 ter Electronic signature. Report statements (and, once opened, powers of attorney) are signed with Teewal's own signing tool, without any outside provider. The document is frozen before signing and its fingerprint recorded; the person signs from their account (drawn signature or typed name), then confirms with a 6-digit code received by email (sent by our email provider, kept only in encrypted form, valid for 10 minutes). Teewal keeps an evidence log: the time, the account identifier, an encrypted fingerprint of the IP address (never the address itself), the browser used, the document fingerprint and the method; no name, no code. The signed PDF, sealed by Teewal, carries the signature and an evidence page. The public verification page shows only the type of document, the signing date and the code, never a name. Revoking a power of attorney: the client can revoke, at any time and from their account, a power of attorney they signed. Teewal then records the server's date and time on the power of attorney and adds a “revocation” event to the evidence log (account identifier, encrypted fingerprint of the IP address, browser; no name, no reason). The signed PDF is not changed; the public verification page shows that it is revoked and since when. The agent and the Teewal team following the job are told. This is a simple electronic signature.
7.2 bis Original documents. When a job includes receiving and handing over an original, the local operator who holds it sees the type of document and the names of the people who hand it over and receive it. They never photograph the content of the document; only the closed envelope and its seal are photographed, in the application. The person receiving the document is identified by a handover code and by showing their identity document, without any photo or copy of that document.
7.3 Processors (they act on our instructions, under a contract that complies with article 28 of the GDPR):
| Provider | Role | Data location | Safeguards if outside the EU |
|---|---|---|---|
| Railway Corporation (548 Market St Suite 68956, San Francisco, CA 94104, United States) | Hosting of the application, the database and the Teewal Assistant | servers in the European Union (Netherlands); company in the United States (possible access from the United States for support) | Standard contractual clauses (Decision (EU) 2021/914, module 2) included in Railway's data processing agreement, to be signed (it is not automatic) |
| Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, United States) | Public website, DNS, storage of vault files (R2) | Company in the United States | EU–US Data Privacy Framework (Cloudflare states that it is certified) and standard clauses |
| Plus Five Five, Inc. (Resend) | Sending emails (including referral invitations: Resend receives the recipient's address for sending) | United States (postal address not published; [email protected]) | Standard contractual clauses included in Resend's data processing agreement (DPA); Resend also states that it is certified under the EU–US Data Privacy Framework. Data stored in the United States; logs kept for 30 days. |
| Teewal local operators (independent contractors, one contract per operator) | On-site checks (visit to a partner, quality control, address verification), receiving and handing over original documents | Country of the job (West and Central Africa) | Standard contractual clauses (Decision (EU) 2021/914, module 2) attached to each operator's contract, and transfer impact assessment |
7.4 Payment providers (controllers of their own processing for fraud prevention and their legal obligations):
- Stripe (Stripe Payments Europe, Limited, Ireland) for bank cards;
- PayPal (PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg).
They receive your payment data directly. Please read their policies.
7.5 WhatsApp (Meta) if you contact us through this channel.
7.5 bis Sign-in providers (Google, Apple, Meta for Facebook), only if you choose to sign in with them: you identify yourself with them; Teewal only sends them the Teewal application identifier, the return address and the sign-in code to be exchanged. No job data is sent to them.
7.5 ter Notification services, only if you turn notifications on: your browser's service (Web Push), Apple (Apple Push Notification service) for the iPhone app, Google (Firebase Cloud Messaging) for the Android app. They receive the device token, a neutral title and text, and the page to open. No name, no place, no conversation content. Apple and Google process these sendings under their own policies.
7.6 Authorities. Only when the law requires it (courts, tax authorities, asset-freezing authorities).
7.7 Partner professionals. A notary, a lawyer or a commissaire de justice (French judicial officer) involved in your job receives what is necessary for the act (acte, the legal document they draw up). They are then the controller of their own processing.
8. Transfers outside the European Union
Some data is processed outside the EU:
- in the United States, by our hosts and technical providers, by the sign-in provider you choose and, if you turn on the app's notifications, by your phone's notification service (Google, Apple, Meta: companies certified under the EU–US framework); these transfers are covered by the European Commission's standard contractual clauses (Decision (EU) 2021/914) or by the EU–US Data Privacy Framework (adequacy decision (EU) 2023/1795) where the provider is certified under it;
- no transfer for the Teewal Assistant: it runs on our servers in the European Union and sends nothing to any other provider;
- in Africa, by the host of “Teewal Vérif”, by Teewal local operators and by the partners who carry out your job (the partner receives, in the country of the job, what is necessary for the task). These transfers are covered by the European Commission's standard contractual clauses (Decision (EU) 2021/914; module 2 with the host of “Teewal Vérif”, with each partner and with each operator, included in their contract) and by a transfer impact assessment. The derogations in article 49 of the GDPR (for example the performance of the contract you requested) are used only in addition, for occasional transfers.
You can obtain a copy of the safeguards by writing to [email protected].
9. How long we keep your data
| Data | Proposed period |
|---|---|
| Account (client or partner) | As long as the account is active. After 3 years without signing in, an email warns you; if you do not sign in again within 30 days, the account is closed and its files erased 30 days later (unless a job is in progress). Data that the law requires us to keep (invoices, payments) follows its own period |
| Deletion requested | Vault files erased and name, email and phone removed from the account 30 days after the request. What remains, with restricted access: invoices, self-billed invoices, payments and withdrawals, with the name and address they carry, 10 years; job, log and chats, 5 years, then pseudonymised; photos, reports and attestations, as in the lines below, with no copy in a vault; a keyed fingerprint of your email and phone, to find an archived report; verification and audit, as in the lines below. Your share links are revoked as soon as you ask. Reasoned refusal if a job, complaint, task, pending payment, balance or freeze is in progress, or if you are the last administrator of an active company. |
| Reports | Dismissed: 6 months after the decision. With a measure: 5 years after the decision, restricted access. Never decided: 5 years after filing. Blocks in a chat: 5 years after the end of the job. |
| Agents' arrival and departure locations, place of proof photos | With the job log (5 years); coordinates of a place you indicate: as long as the record exists |
| Sign-in links | Never stored in plain text; valid for a few minutes |
| Sessions | 30 days (24 hours for the demo), then erased by a daily task |
| Notifications (browser subscription, device token) | Until you turn them off or sign out, or until the service says the device no longer responds; erased at the latest with the vault files after the account is closed |
| Signing in with Google, Apple or Facebook | Identifier, email and “verified” indicator: as long as the provider is linked; erased when you unlink it, or with the vault files after the account is closed. Sign-in round trip: 10 minutes (deleted every day); sign-in awaiting confirmation: 30 minutes. Provider's access token: never kept |
| Requests and jobs | Duration of the relationship + 5 years after the end of the job (limitation period for bringing legal action, French Civil Code (Code civil), art. 2224), in a restricted-access archive. Afterwards the job is pseudonymised and kept without any time limit: it no longer has a direct link to you, but it remains personal data, because it can still be traced back to you. What stays: service, country, city, dates, amount, status and the masked task titles. Places, the request and the detailed log are removed. Invoices and payments keep their link to the job for their own period (10 years), with restricted access |
| Finding an archived file | An index keeps, without any time limit, the job reference, the agent numbers, a summary and a keyed fingerprint of your email and phone, never those details in clear. It is used to find a report at your request or on legal request. Only management and compliance can query it, with a mandatory reason; every search is logged, without the email or phone searched for |
| Invoices and accounting records | 10 years (accounting obligation) |
| Vault: your documents | As long as the account is open; you can delete them at any time (file erased from our servers, only the fingerprint remains in the job log) |
| Vault: reports and proof of a job | Protected until 30 days after delivery (complaint period), then deletable by you |
| Vault after the account is closed | Files erased 30 days after closure (time to change your mind and reopen the account) |
| Vault log (deletions, closure, decisions) | 5 years after the event (proof in the event of a dispute) |
| Job discussions | Closed 30 days after the end of the job: nobody writes there any more and the agent no longer has access, you can reread them. Duration of the job + 5 years (proof in the event of a dispute), in a restricted-access archive after 1 year: you can reread them, the agent and ordinary staff no longer have access, and only management and compliance can consult them, each consultation being logged. After 5 years, pseudonymised: only the text remains, in which contact details and identified health words are masked at that point, with no author and without any time limit; the original is erased |
| Job photos (no faces, no identity documents) | 1 year after the end of the job, restricted-access archive: you can view them again until 5 years, the agent and ordinary staff no longer have access, and only management and compliance can consult them, each consultation being logged. As long as the same property or the same relative has an unfinished job, the country team and the agent can still see them; the year then runs from the end of the last job for that property or relative. After 5 years, pseudonymised and kept without any time limit, with their date and fingerprint, with no direct link to you or the agent, no position and no metadata, with restricted access. The job's other documents (attached documents) are erased at 5 years, apart from the copy in your vault |
| Electronic signature: document to sign, drawing or typed name, code | Code: 10 minutes, kept encrypted. Frozen document, drawing and typed name: with the job, erased at 5 years (the signed PDF follows the line below) |
| Electronic signature: evidence log (no name, no code), including the revocation of a power of attorney | Kept without time limit to prove the signature (and its revocation), append-only |
| Job reports and attestations | Unchanged for 5 years, then in a restricted-access archive: they carry names, only management and compliance can consult them, and each consultation is logged. Erased 30 years after the end of the job, including the record of who signed |
| Powers of attorney | At the end of the job, the power of attorney only serves to prove that it existed; its trace is kept without any time limit. At the end of the job: on the record, the client's and the agent's identity document numbers become partly masked and the agent number is recorded; the signed PDF stays intact and accessible as before. At 5 years: the signed PDF is erased and replaced by a copy with masked numbers, which states that it is not the signed document, with restricted access; the full number no longer exists at Teewal. At 30 years: the copy is erased. What stays: the procedure, the office, the dates, the signed status and the agent number, with no name, number ending or reference, even if the agent has deleted their account |
| Copy in your vault, at 5 years | If your account is open 5 years after the end of the job, you keep in your vault your photos (original file), your reports and attestations, including the signed attestation, in which the agent's name is then readable, and your own documents, never powers of attorney. This copy is yours alone: the team has no access to it and it cannot be used to find the archived job. You can delete it at any time; it is erased 30 days after the account is closed. Account already closed at that date: no copy |
| Family file | As long as it exists; for a member who leaves: their paid shares remain linked to the payments (accounting period) |
| Family invitations | 14 days |
| Referral credits | Until they are used, at most 12 months after they are granted (expiry) |
| Addresses entered for a referral invitation | Not kept by Teewal: erased as soon as the message is sent (the outbox keeps the message without the address). Our email provider, Resend, keeps sending logs (including the address) for 30 days, and its backups for 7 days more, in the United States |
| “Already invited by this referrer” fingerprint | 12 months after the invitation: used only so that the same referrer does not invite the same person twice |
| Invitation opt-out fingerprint | As long as Teewal sends referral invitations (otherwise the objection would be forgotten) |
| Number of invitations sent | 12 months (sending limits and statistics) |
| Referrals, rewards and referral log | 5 years after the referral is closed (reward paid, refused or expired), period for complaints and proof (Civil Code art. 2224); entries linked to a payment follow the accounting period (10 years) |
| IP fingerprint of a sign-up with a code | Erased with the sign-in link, as soon as it is used or expires (scheduled purge task) |
| Service emails (outbox) | 12 months (proof of sending), then erased |
| Payment method fingerprint | 5 years after the payment |
| Demo | Test accounts: 24 hours; demo log purged regularly |
| Partner verification: | — |
| — images (identity document, documents, selfie) | Decision or 72 hours at most (African service) |
| — face templates | Never stored |
| — document number, date of birth read | Only for the time of processing, in memory |
| — anti-duplicate fingerprint | Duration of the relationship + 1 year; 5 years after a refusal or exclusion for fraud (limitation period for bringing action, Civil Code art. 2224) |
| — name and phone number of references | 30 days after the decision |
| — status, score, signals, reason, expiry date | Relationship + 5 years (proof that the verification was carried out, Civil Code art. 2224) |
| — audit log and purge log | 5 years after the event |
| — video call | Never recorded |
| Partners' wallet and withdrawals | 10 years (accounting) |
| Teewal Assistant: | — |
| — conversation | Duration of the session (24 hours at most), then erased |
| — conversation passed on to a person (“Speak to a person”) | 1 year after the last exchange |
| — anonymous counters | No limit (anonymous) |
| Original documents: | — |
| — the document itself | Held by the operator for 72 hours at most, then handed over or returned; never copied |
| — custody log (seal, photos of the seal, times, positions, names, handover code, declared value) | Duration of the job + 5 years (proof in the event of a dispute) |
| Local operators: | — |
| — contract, registration, insurance certificate | Duration of the contract + 5 years |
| — positions at the start and end of jobs | With the job log (duration of the job + 5 years) |
| — payments | 10 years (accounting) |
10. Security
Encryption of exchanges (HTTPS, HSTS), protected session cookies, sign-in links with limited use and never stored, files served only if their fingerprint matches, payments confirmed only by Stripe or PayPal, internal access limited and logged, append-only and chained audit log for verification; electronically signed documents sealed by Teewal, append-only and chained signature evidence. Verification service: per-file encryption, keys kept in the region, no backup of images.
In the event of a data breach presenting a risk, we notify the CNIL within 72 hours and, if the risk is high, the people concerned (GDPR, art. 33 and 34).
11. Your rights
You can:
- access your data and obtain a copy;
- have it rectified;
- request its erasure (unless we must keep it, for example for accounting or fraud prevention);
- request restriction of processing;
- object to processing based on our legitimate interest;
- receive your data in a reusable format (portability);
- withdraw your consent at any time (biometrics), without affecting what was done before;
- not be subject to a decision based solely on automated processing, obtain human intervention, give your point of view and contest the decision;
- give directives on what happens to your data after your death (law no. 78-17, art. 85). Without a directive, on your death, your legal heirs can only exercise the rights provided for by law (for example having your account closed), and your vault is erased according to the periods in § 9.
How. Write to [email protected] (data protection contact person). We reply within one month (which may be extended by two months if the request is complex; we will let you know). We may ask you to prove your identity if we are in doubt.
Complaint. You can refer the matter to the CNIL (3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07 · www.cnil.fr) or to the data protection authority of your country.
12. African data protection laws
Teewal works in several African countries. Their laws apply in addition to the GDPR for processing carried out locally or concerning their residents. Before opening in each country, Teewal completes the required formalities. Indicative list:
| Country | Law | Authority | To be arranged |
|---|---|---|---|
| Senegal | Law no. 2008-12 of 25 January 2008 | Commission de protection des données personnelles (CDP) | Declaration or authorisation; authorisation for biometrics and for transfers to a third country |
| Côte d'Ivoire | Law no. 2013-450 of 19 June 2013 | Data protection authority (ARTCI) | Prior authorisation of transfers outside ECOWAS; formalities for biometrics |
| Nigeria | Nigeria Data Protection Act 2023 | Nigeria Data Protection Commission (NDPC) | Transfer rules (s. 41 to 43); possible registration |
| Ghana | Data Protection Act 2012 (Act 843) | Data Protection Commission | Registration of the data controller |
| Cameroon | Law no. 2024/017 of 23 December 2024 | Autorité de protection des données personnelles (APDP) | Transfer abroad: equivalent protection and prior authorisation |
| The Gambia, Mali, Guinea, Benin, Togo, Burkina Faso, DR Congo… | National laws | National authorities | To be studied before each opening |
You can also exercise your rights before the authority of your country.
13. People met on site
During a job, a partner may meet other people (a relative, a seller, an administrative officer). Rules:
- no photo of a person without their consent; never a photo of a sick person;
- job photos show places and objects, not faces;
- the person may ask the partner for information about Teewal and exercise their rights at [email protected].
14. Minors
Teewal is reserved for people aged 18 and over. A job may concern a minor (for example visiting the child of a relative): it is carried out with the consent of their legal representative, and with no photo of the child.
15. Changes
We will notify you of any significant change by email or in the application. Date of last update: 26 October 2026.