Skip to content

Transfer register

Kept by the Information Officer, Ashley Verhulp, and given to anyone who asks.

It lists every provider that stores or processes personal information for Axiom Logic outside South Africa, where, and the ground in section 72 of the Protection of Personal Information Act 4 of 2013 (POPIA) that the transfer relies on. Where a fact has not been confirmed, it says so. It is not legal advice.

Providers

Provider
Lovable
What it does for us
Hosting the website and portals; building the software. Until it is removed (fact 28), our former database, unused after the move
What it receives
What the website and portals handle as they run: requests, pages, and data passing between a person's browser and our database; one cookie, __dpl. From revision 20 it no longer stores the database, accounts or files, except the former database kept unused until it is removed
Where
Hosting on its own network (see Cloudflare). To record: fact 29. Former database in Frankfurt, Germany (European Union), until it is removed
Section 72 ground
No binding agreement is in force. Lovable's data processing agreement opens: "If you're on a Business or Enterprise plan, your usage includes our Data Processing Agreement (DPA)", and says it "forms part of the Terms of Service ordered by the Customer under an Order Form" (its page, last updated 6 November 2025, read 11 October 2026). This account is on the Pro plan (Lovable's own workspace record, read 11 October 2026), so that agreement does not apply. The database is in Germany, where the EU General Data Protection Regulation applies; whether that law alone meets s72(1)(a) is for the attorney's review. For questionnaire answers, the visitor's consent, s72(1)(b), by tick box. For readings from a site in testing, the site owner's written consent, s72(1)(b) (legal/trial-site-consent.md).
Standing
Open. Location confirmed from the database address. Closed by a data processing agreement in force for this account, which Lovable offers only through its Business or Enterprise plan (fact 20). The same agreement is the written contract POPIA section 21 requires with an operator. From revision 20 the database is with Supabase.
Provider
Supabase
What it does for us
Our database, account records (including the secret keys of two-step sign-in) and file storage; its own backup copies of the database
What it receives
Everything the website and portals record, including site readings, profile photos, support ticket files and documents a workspace uploads; passwords only as scrambled values
Where
Ireland (European Union), region eu-west-1, project epqsrfbanxlnrnwhiwxf, organisation "Cynvest Investments (Pty) Ltd." on the Pro plan (Supabase connector, read 24 October 2026)
Section 72 ground
Binding agreement, s72(1)(a): Supabase's data processing agreement, accepted by the operator (stated, 19 October 2026; fact 27). For readings from a site in testing, also the site owner's written consent, s72(1)(b) (legal/trial-site-consent.md).
Standing
Open: fact 27. Backups kept 7 days on the Pro plan. Supabase's AI data option switched off by the operator on 19 October 2026 (read back the same day); its SQL and log assistant options, which can send database structure and logs but not table data, remain on.
Provider
Cloudflare (the network that delivers the site for Lovable)
What it does for us
Delivers pages and protects the site
What it receives
Connection address, pages requested, one security cookie
Where
Its network, in and outside South Africa
Section 72 ground
Through Lovable, which has no data processing agreement in force with us (see Lovable)
Standing
Open. Follows Lovable. To record: confirmation in Lovable's terms that Cloudflare is bound as a sub-processor.
Provider
Cloudflare (Turnstile, on our own account)
What it does for us
Checks that a person, not a program, is using the sign-in page and our public forms. Not in use until it is switched on.
What it receives
Directly from the visitor's browser: technical signals of the browser and device, and the connection address. From our server: the one-time result of a check, to confirm it.
Where
Its network, in and outside South Africa. To record: where checks are processed.
Section 72 ground
To record. Expected: binding agreement, s72(1)(a): Cloudflare's data processing terms.
Standing
To record: the terms accepted and their date; what Cloudflare keeps from a check and for how long. To record before it is switched on: whether any cookie is set in the visitor's browser, measured in a real browser.
Provider
Microsoft (Microsoft 365)
What it does for us
The company mailbox
What it receives
E-mails sent to us and our replies
Where
To record: read the mailbox location from the account.
Section 72 ground
To record once the location is known. If outside South Africa: binding agreement, s72(1)(a).
Standing
Open.
Provider
Anthropic (Claude)
What it does for us
Private business tools; drafting and analysis
What it receives
Business contacts and consent choices; text we give it to work on
Where
The provider states that data is stored in the United States and that traffic may be routed through the United States, Europe, Asia and Australia (its privacy centre, read 6 October 2026).
Section 72 ground
To record. Expected: binding agreement, s72(1)(a): the provider's data processing addendum of 24 February 2025, which applies to accounts under its commercial terms.
Standing
Open. To record: which terms the account is under, and whether the addendum therefore applies.
Provider
Mailgun, through Lovable's e-mail service
What it does for us
Carries account e-mails sent from notify.axiomlogic.ai
What it receives
The recipient's e-mail address and name, and the message: an invitation, a reset or a notice
Where
European Union service, read from the subdomain's mail records on 5 October 2026
Section 72 ground
Through Lovable, which has no data processing agreement in force with us (see Lovable)
Standing
Closed at revision 20: the sign-in service's e-mails go through Resend. Mail sent before then stays under Mailgun's retention (fact 10).
Provider
Cloudflare R2
What it does for us
Off-site backup copies of the database. Not yet in use.
What it receives
When in use: everything the database holds
Where
European Union jurisdiction. The bucket axiom-logic-backup was created by the operator on 6 October 2026.
Section 72 ground
Binding agreement, s72(1)(a): Cloudflare's data processing terms
Standing
Not in use until the backup build (programme step 7.2). To record: the date and version of the terms accepted; how long each backup copy is kept.
Provider
Anthropic (AI features of the portal)
What it does for us
The AI model behind "Explain this result", "Read with AI", the Ask page and, from privacy notice revision 13, the AI analyst in the portal. It replaced OpenAI on 6 October 2026, in the build that carries privacy notice revision 8. From privacy notice revision 20, also "Draft the mapping" for a connection (HTTP API client revision 4, §6a; payload specification revision 6, Annex D).
What it receives
What a member sends by pressing one of those buttons: the envelope asked about and its reasons; the pages of a document being read; a question with passages from that workspace's own documents. From privacy notice revision 10, where AI reading is on for a workspace, also the pages of each document uploaded to it, as it is uploaded and without a further press. A document's pages can hold personal information of the customer's own people and of third parties. AI reading is off for a workspace until an owner or administrator switches it on; while it is off, nothing is sent from a document. From privacy notice revision 13, a member's question to the AI analyst with the evidence gathered from that workspace: its declared assets and roles, measured readings and their summaries, alarm records (which can name the member who acknowledged or closed an alarm), and passages of documents already read with AI. From privacy notice revision 14, also the published rates of the tariff the workspace has declared for its point of delivery, each with the document and page it is printed on; published rates are not personal information. From privacy notice revision 20, when a member presses "Draft the mapping": one body that a connection of that workspace received, exactly as it was kept, and nothing else (not the connection's address, headers or credential). A body is what a device, gateway or outside service sent; it is usually readings, but it can hold anything the sender put in it, including a person's name or e-mail address. The model only proposes a mapping; a member saves it, and no AI takes part when readings are then taken in. Each request carries one workspace's information and no other.
Where
From revision 19 our server sends each request directly to Anthropic's API, to its model Claude Sonnet 5, using the company's own API key (application src/lib/ai/anthropic.server.ts, at the backend move phase 3 commit). Anthropic states that data is stored in the United States and that it may route traffic to select countries in the United States, Europe, Asia and Australia (its privacy centre, page dated 15 June 2026, read 14 October 2026).
Section 72 ground
To record: fact 12. Expected: binding agreement, s72(1)(a): Anthropic's commercial terms and the data processing addendum that forms part of them.
Standing
Open on the ground only (fact 12). From revision 19, Lovable no longer receives or keeps AI requests. Anthropic deletes API inputs and outputs within 30 days, keeping them longer only to enforce its usage policy (up to 2 years) or where the law requires (its privacy centre, page dated 1 July 2026); it does not use inputs or outputs from its commercial products, the API included, for training by default (page dated 18 August 2026). No "do not store" request is made.
Provider
Resend
What it does for us
Sends the e-mails the portal itself sends from mail.axiomlogic.ai: invitations, password resets and password-change notices sent by the portal, staff and emergency-access notices, and notices to our own mailbox. From revision 21, also the e-mail confirming a member's acceptance of WhatsApp alerts and the e-mails to the members on a workspace's "When WhatsApp is down" list. From revision 20, also the sign-in service's own e-mails (sign-up confirmation, change of e-mail address, re-authentication, invitations and password recovery).
What it receives
The recipient's e-mail address and name, and the message
Where
Ireland (European Union), region eu-west-1, chosen for mail.axiomlogic.ai (stated by the operator, 19 October 2026). To record: fact 25.
Section 72 ground
To record: fact 26. Expected: binding agreement, s72(1)(a): Resend's data processing agreement.
Standing
Open: facts 25 and 26.
Provider
Apple
What it does for us
"Sign in with Apple" for invited accounts. Not switched on at this revision.
What it receives
To us: an identifier for the person's Apple Account, the e-mail Apple shares or a private relay address, and the name the first time. To Apple: that the person signed in to our service.
Where
Sign-in uses Lovable's managed Apple setup: "No Apple Developer account is required", and Lovable manages the configuration (Lovable's documentation, read 14 October 2026). So no Apple company contracts with us; the relationship runs through Lovable. Apple states that personal data collected worldwide is generally stored by Apple Inc. in the United States, and that the Apple company that controls a person's data depends on where they live (Apple Privacy Policy, updated 30 July 2025, read 14 October 2026).
Section 72 ground
To record. Through Lovable, which has no data processing agreement in force with us (see Lovable).
Standing
Not switched on. Recorded at revision 17 (facts 14 and 15). The operator decided on 14 October 2026 to keep Lovable's managed setup rather than her own Apple developer account. Open: whose name Apple shows a person at sign-in, which Lovable's documentation does not state; it is to be seen in a test before the button is shown. From revision 20 not offered: Lovable's managed setup serves only Lovable's own backend.
Provider
Mapbox
What it does for us
Address search and maps in the portal. In use from 11 October 2026, before this revision.
What it receives
From our server: the text a member types in the address box. Directly from a member's browser, when a map is shown: the connection address and a description of the browser and device. A site's coordinates.
Where
The provider states that it processes personal information in AWS in the United States, with content cached in other regions, and that its subsidiaries' staff may reach it from where they work; it keeps connection addresses in its logs for 30 days (customer privacy FAQ, last updated 22 August 2023).
Section 72 ground
No agreement is confirmed. Mapbox publishes a form of customer data processing agreement whose Schedule C carries the European Commission's 2021 standard contractual clauses; whether it is in force for our account is not recorded.
Standing
Open. To record: which Mapbox account the portal's token belongs to, the terms accepted and their date, whether the data processing agreement applies, and the section 72 ground.
Provider
WasenderAPI
What it does for us
Sends WhatsApp alarm notices and notifications from one WhatsApp number linked to it by a QR code; from revision 19 also the contact list's invitations (sent only after an owner or administrator confirms the person agreed), the confirmation after JOIN and the one reply after STOP; from revision 21 also the welcome message with the link to choose alarm groups, the grouped message that replaces alerts held back by a limit, and the message to a member after the tick box and Accept. It passes back replies (ACCEPT, COMPLETE, YES, STOP and the others of design/alarms-and-notices.md §9.2) and delivery receipts. It is not the official WhatsApp Business Platform: its terms say it is not affiliated with WhatsApp Inc. Used once, on 19 October 2026 at 18:24 UTC, for a test message to the operator's own confirmed number (read from the live database); alerts, invitations and joining are switched on only after this revision and privacy notice revision 24 are issued.
What it receives
The recipient's WhatsApp number; the message text (from the rule's placeholders: site, asset, metric, value, unit, limit, condition, time, priority, link); the recipient's replies. WhatsApp itself (WhatsApp LLC, a Meta company) also carries the message under its own terms.
Where
Not stated. Its pages give a London address (71-75 Shelton Street, London WC2H 9JQ, United Kingdom), name "WasenderApi" and "WasenderApi Inc." without a registered company, and do not say where its servers are (privacy policy and terms, both "Last Updated: January 1, 2023", read 15 October 2026).
Section 72 ground
No agreement. It offers none. The ground relied on is the person's consent (s72(1)(b)): a member's when they switch WhatsApp on; a contact's when they reply ACCEPT or YES to an invitation, or write JOIN and receive the confirmation, each of which names WasenderAPI and that it is outside South Africa and gives the address of the privacy notice.
Standing
Open. To record: facts 23 and 24.
Provider
Open-Meteo
What it does for us
Weather readings and forecasts for a workspace's declared sites. In use from 11 October 2026: one connection per workspace, checked every hour or less often; forecasts kept 7 days.
What it receives
A site's coordinates. Nothing about any person. Coordinates identify the company that owns the site.
Where
To record: where Open-Meteo is run from and where it serves requests.
Section 72 ground
To record.
Standing
Open. In testing the free service is used. Its terms, read on 13 October 2026, allow the free service for non-commercial purposes only and count integrating it into a commercial product as commercial; whether testing before any paying customer falls inside that is still not confirmed with Open-Meteo. The operator decided on 13 October 2026 to keep the free service while in testing (fact 21). The paid service is to be taken before weather is offered to a paying customer.

What is still to be recorded

  1. Lovable: a data processing agreement in force for this account (through the Business or Enterprise plan; see fact 20), with its date and version. From revision 20 this covers hosting, and the former database until it is removed (fact 28).
  2. Cloudflare: that Lovable's terms bind it as a sub-processor.
  3. Microsoft: where the mailbox is stored, then the ground.
  4. Anthropic: where information is processed, then the ground.
  5. Recorded at revision 20: Supabase keeps daily backups of the database for 7 days on the Pro plan. Lovable Cloud's backups of the former database end when the operator removes it (fact 28).
  6. Lovable: written confirmation of what the __dpl cookie is for.
  7. Recorded at revision 19: requests go from our server directly to Anthropic's API under the company's own account. Anthropic stores data in the United States and may route traffic to the United States, Europe, Asia and Australia (recorded at revision 17).
  8. Recorded at revision 19: Lovable no longer receives or keeps AI requests. Anthropic deletes API inputs and outputs within 30 days, longer only to enforce its usage policy (up to 2 years) or where the law requires, and does not train on them by default (recorded at revision 17). Lovable's own use for training of other content: fact 22.
  9. Recorded at revision 13: the account is on the Pro plan, and Lovable's data processing agreement covers only its Business and Enterprise plans. Fact 1 stays open until an agreement is in force.
  10. Mailgun: that Lovable's terms bound it as a sub-processor, and how long it keeps mail sent before revision 20 and its logs.
  11. Cloudflare R2: the terms accepted, and how long each backup copy is kept. To be recorded before the backup is switched on.
  12. Anthropic: that the company's API account is under Anthropic's commercial terms, that its data processing addendum therefore applies, and the date.
  13. The message broker that relays site readings to the ingest point: who runs it, where it runs, and under what terms.
  14. Sign-in with Google is not built. Sign-in with Apple is to be built and switched on at the operator's choice of 6 October 2026: Apple is added to this register, with where it processes and the ground relied on, before the button is shown. Recorded at revision 17: sign-in uses Lovable's managed Apple setup, which needs no Apple developer account of ours. Whether Apple shows a person Lovable's name or ours is not stated in Lovable's documentation; it is to be seen in a test before the button is shown.
  15. Recorded at revision 17: no Apple company contracts with us, because Lovable's managed setup stands between us and Apple; the terms are Lovable's, as for fact 1. Apple states that it generally stores personal data collected worldwide with Apple Inc. in the United States. The section 72 ground stays open with fact 1.
  16. Open-Meteo: where it is run from and serves requests, whether its free terms cover testing, and the section 72 ground. To be recorded before a weather job is offered.
  17. Cloudflare Turnstile: the terms accepted and their date, where checks are processed, what is kept from a check and for how long, and whether any cookie is set in the visitor's browser.
  18. Mapbox: the account the portal's token belongs to, the terms accepted and their date, whether its data processing agreement is in force for that account, and the section 72 ground. Recorded at revision 14: the service was in use before it was entered here.
  19. Recorded at revision 14: Open-Meteo is in use (fact 16 stays open) and its forecasts are kept 7 days.
  20. Recorded at revision 15: Lovable's support replied in writing to the operator on 13 October 2026: "We do not sign the DPA for Pro accounts; it applies on Business and Enterprise only." Moving the workspace to Business "puts the DPA in force straight away", through the Terms of Service, with no Order Form, signature or return step, and the published pre-signed copy at lovable.dev/data-processing-agreement is the document of record. Its sub-processor list, with each provider's purpose and location, is at trust.lovable.dev/subprocessors and is the same on every plan. The operator decided on 13 October 2026 to stay on Pro for now, so fact 1 stays open. The sub-processor list is not yet read into this register.
  21. Recorded at revision 15: the operator decided on 13 October 2026 to keep Open-Meteo's free service while in testing (fact 16 stays open). On 13 October 2026 every scheduled weather call from the live site (10:58, 17:05, 18:05 and 19:05 UTC) was refused by Open-Meteo with HTTP 429 and stored no reading.
  22. Recorded at revision 17: Lovable states that the content of Free and Pro accounts may be used to train its own models from 9 September 2026 unless the account opts out under "Use my Lovable content for model training", and that data in an app's own database and storage is not used (its documentation, read 14 October 2026). The operator decided on 14 October 2026 to opt out and switches the setting off before this revision is issued.
  1. WasenderAPI: the legal entity that contracts with us, where it stores and processes messages and for how long it keeps message content, its sub-processors, and whether it will sign written terms under POPIA sections 20 and 21. Its privacy policy names none of these (read 15 October 2026).
  2. WasenderAPI: the account the API key belongs to, the plan and its date, and the WhatsApp number linked to it.
  3. Resend: the sending region for mail.axiomlogic.ai is Ireland (eu-west-1), stated by the operator on 19 October 2026. Still to record: where Resend stores sent mail and logs, and for how long.
  4. Resend: the terms accepted for the account, whether its data processing agreement is in force, its sub-processors, and the section 72 ground.
  5. Supabase: the data processing agreement accepted (stated by the operator on 19 October 2026), its version and date, Supabase's sub-processors (expected: Amazon Web Services in Ireland), and where its staff may reach the database from.
  6. Lovable Cloud: the date the former database is removed (planned about two weeks after the move), and that its exports and backups are deleted with it; a last export is downloaded and checked first.
  7. Lovable: where the application's server code runs once the database has moved.
  8. Recorded at revision 20: to rehearse the move, a copy of the database was restored into the Supabase project in Ireland on 19 October 2026 (8 accounts, no stored files) and on 21 October 2026 (9 accounts, no stored files), on the operator's decision, and cleared on 19 and 22 October 2026 (read back as empty by the build seat). Both were made before this revision named Supabase.

Sites sending readings for testing

A site's readings identify the company that owns it. Each owner signs the consent in legal/trial-site-consent.md before its site sends, and this table records it.

Site owner
To be named by the operator
Devices
Two generator feeds, two carbon-savings feeds, one energy tracker (five devices)
Sending since
5 October 2026
Consent signed
None on 6 October 2026
Standing
Open. The operator sends the letter to each owner. A feed with no signed letter 14 days after that document is issued is switched off.

The privacy notice and the PAIA manual say that these are still being recorded. Each is closed by a new revision of this register.