Privacy Policy
Privacy Policy
How Site Engine collects, uses, stores and shares personal information — for the organisations that run workspaces here, and for the people who interact with them.
Last updated: October 2026
Who this covers
Site Engine is a multi-tenant platform: every organisation gets its own workspace (we call the organisation a tenant). This policy applies in two directions:
- You are the platform. For workspace accounts, billing and platform operations, Site Engine is the data controller.
- You are a tenant's audience. For the content a tenant collects — donor details, event RSVPs, ticket purchases, store orders, form submissions, newsletter subscribers — the tenant is the data controller and Site Engine acts as their data processor. Questions about that data go to the organisation first; we support them in honouring it.
This policy covers everything a tenant workspace can see and use. It does not cover internal platform-administration systems, which are accessible only to Site Engine staff.
What we collect
Account & workspace data
- Registration: organisation name, owner name and email address, password (stored only as a salted hash).
- Members: name, email, role (including custom roles and their page/permission sets), status, suspension state and invite metadata for each person added under User Management.
- Security configuration: two-factor authentication secrets, password-policy settings, IP allowlists, forced-password-change flags, active sessions (device, IP, last activity — revocable from Settings → Security).
- Audit log: actor, action, timestamp and request context for changes made inside the workspace — retention configurable per workspace.
Billing data
- Plan, subscription status, invoice and payment history, tenant credit balances and proration adjustments.
- We never see or store card numbers. Payments are processed entirely by the gateway you connect (Stripe, Paystack or PayPal). For recurring billing we store only the gateway's reusable token/reference.
Data inside each feature
Content — blog, pages, media, pop-ups
- Posts, categories, authors, featured flags and publication times.
- Comments: the commenter's name, email and message, held for moderation.
- Media library files and any legal documents a tenant publishes.
Donations & campaigns
- Donor name, email, amount, currency, payment method and status, plus the campaign a gift is designated to.
- Offline payments: proof-of-payment files uploaded by donors, and refund-proof documents where a refund requires one.
- Receipt and thank-you email delivery records.
Events & ticketing
- RSVPs: name, email, response status (Going / Maybe / Pending / Declined) and approval state.
- Tickets: attendee name and email, ticket tier, QR code value, issue time and check-in time recorded by gate staff.
- Waitlist: name and email until the person is notified or removed.
- Attendee data can be deleted or anonymised per event; anonymised records keep sales totals without personal details.
Store
- Orders: customer name, email, items, amounts, status and uploaded proof of payment for manual methods.
- Refunds and their processing status.
Forms
- Whatever fields a tenant places on a form — these can include personal details, topic selections, checkboxes and uploads. The tenant defines them; we store submissions and forward notification emails to the addresses they configure.
Newsletter & email
- Subscriber email addresses and list membership.
- Campaign content and send records. Mail is sent either through the platform's mail service (subject to the tenant's plan quota) or the tenant's own SMTP account.
Analytics
- Workspace audit activity and usage metrics. If a tenant connects Google Analytics or Plausible, those services process their site traffic under the tenant's own accounts and policies.
Integrations & connected sites
- Stored credentials: payment-gateway keys, SMTP username/password, webhook endpoint URLs and signing secrets, analytics IDs, and the Content API keys a tenant uses to connect external websites.
- Connected external sites pull published content, events, pop-ups and forms through the tenant's API key — data flows out of Site Engine to the tenant's own domain under their control.
- Custom domain names and their DNS verification status.
How we use it
- Running the workspace: authentication, roles, module gating, tenant isolation, sessions and audit trails.
- Transactional email: password resets, member invites, RSVP confirmations with calendar invites, ticket delivery, donation thank-yous and receipts, form-submission notifications, waitlist notices, refund updates and billing notices.
- Billing: recurring subscription charges through the gateway token, proration credits, grace periods and non-payment locks.
- Delivering published content, event pop-ups and forms to the tenant's connected websites via the Content API.
- Enforcing plan limits — seats, custom roles, email quotas — and platform security.
We do not sell personal information, use tenant data for advertising, or mine workspace content for any purpose beyond running the service.
Third parties & sharing
- Payment gateways (Stripe, Paystack, PayPal): the full charge happens on the gateway's side under the tenant's own account and their terms; we store only references and tokens.
- Email delivery: the platform's mail provider, or the tenant's own SMTP host when configured — in which case mail goes through their provider, not ours.
- Infrastructure: application hosting on Render and managed Postgres on Supabase (EU region).
- OpenStreetMap / Nominatim: the venue text typed into the event form is sent as a lookup query for autocomplete suggestions; nothing else is shared.
- WhatsApp: "send via WhatsApp" buttons open a wa.me link — the share happens between the sender and WhatsApp.
- Analytics providers a tenant chooses to connect (GA4, Plausible) — these only load after the visitor accepts analytics in the consent banner.
- Payment gateways a tenant chooses to connect (Paystack, PayFast, Yoco, Stripe) — buyers are sent to the gateway to pay; card details never touch Site Engine.
- Email delivery: the platform's mail provider (Resend) or a tenant-connected provider carries outbound mail.
- Law: where disclosure is required by law or to protect the platform and its users from abuse.
Retention & deletion
- Workspace data is kept while the account is active. Audit-log retention is configurable per workspace.
- Event attendee data can be purged or anonymised per event; form submissions, RSVPs, orders and donor records can be deleted by workspace staff.
- Downgraded workspaces keep their data unless a purge is run — limits restrict creating more, not keeping what exists.
- Closing a workspace deletes its content and configuration after a short recovery window; billing records are retained as required for tax and accounting law.
- IP addresses are scrubbed automatically: security-log IPs after 90 days, order IPs after ~18 months (the longest card chargeback window). Audit entries recording financial events are kept at least 90 days regardless of the configured window.
- Children's data: workspaces are run by adults; organisations collecting children's information (e.g. youth programmes) are responsible for guardian consent under POPIA s34-35 and should say so on their forms.
Security
- TLS everywhere; passwords stored salted and hashed; 2FA and IP allowlists available per workspace.
- Every request is scoped to its tenant — data cannot cross workspaces — with role-based page and permission enforcement plus module-level gating.
- Secrets (gateway keys, SMTP passwords, webhook secrets) are write-only in the UI and masked on display.
Your rights
Depending on your jurisdiction — including POPIA in South Africa and the GDPR where it applies — you may have rights to access, correct, export, restrict or delete personal information, and to object to processing:
- Workspace staff: manage most data directly in the dashboard (members, submissions, attendees, donors, orders, subscribers). Your workspace admin or Site Engine support can handle the rest.
- Donors, attendees, customers, subscribers: contact the organisation you interacted with — they control that data. If you can't reach them, contact us and we'll route the request.
- Unsubscribe: every bulk email honours the recipient's removal; transactional mail (receipts, tickets, password resets) can't be opted out of while the service is used.
Security incidents
If a breach is likely to expose personal information we notify the Information Regulator and affected parties as POPIA s22 requires, and we alert workspace owners so they can meet their own obligations toward their customers.
Changes & contact
We may update this policy as the product evolves; material changes are announced in the dashboard and the "last updated" date above always reflects the current version. Questions or requests: contact us.
Questions about this policy?
Reach the team through the contact page — a human replies.