Cookie Policy

1. What this policy covers

This policy covers:

• the public pages of yielde.dev, such as the home page, pricing and our legal pages;
• chat-widget preview pages on yielde.dev (addresses that start with yielde.dev/embed/preview/), where people can try a platform customer's chat widget before it goes on the customer's own website;
• sign-in and the client dashboard on yielde.dev, used by Yielde platform customers;
• our payment pages on yielde.dev: the card step when you start a platform trial in the dashboard, and the page for paying a custom-build invoice (addresses that start with yielde.dev/pay/).

It does not cover:

• cookies or browser storage on a customer's own website, or in a customer's own automation. That includes the Yielde chat widget once a platform customer adds it to its own website: there, the widget keeps the conversation in the visitor's browser on that website. The customer's own privacy and cookie notices cover that, because the customer is the responsible party for its end-users' and leads' personal information and Yielde acts only as its operator (POPIA section 21). The preview page on yielde.dev is covered in section 4;
• Paystack's own website. Paystack's own notice covers it (section 7); and
• personal information we process through the platform for a customer. Our Privacy Policy and the customer's Data Processing Agreement cover that.

2. Cookies and browser storage, in plain words

A cookie is a small text file a website places in your browser. Your browser sends it back to that website with each request.

Browser storage (localStorage and sessionStorage) is a similar place in your browser where a website can keep small pieces of information. localStorage stays until you clear it. sessionStorage is cleared when you close the tab. Unlike a cookie, browser storage is not sent to our servers with each request. Our code can still read a stored item and send it to us on purpose. Sections 4 and 5 say when that happens.

In this policy, "cookie" means only a cookie. When we also mean browser storage, we say so.

• First-party cookies and stored items are set by Yielde, on our own address, yielde.dev.
• Third-party cookies are set by another company, on its own web address, while you use our page. We set no third-party cookies ourselves. The only third-party cookies on our pages are Paystack's, on our payment pages (section 7).

3. The short version

• Our public pages set no cookies. They save nothing in your browser's storage, except that a "page not found" page may save your light or dark look (section 4). If you don't sign in or open a link we emailed you, yielde.dev sets no cookies.
• We use no advertising or marketing cookies and no cross-site tracking. We set no third-party cookies ourselves. Paystack sets its own cookies on our payment pages (section 7).
• Signing in to the dashboard sets strictly necessary cookies that keep you signed in and keep sign-in links safe.
• The sign-in and sign-up pages, the platform checkout and the dashboard save your light or dark look in your browser's storage when they load. The dashboard also keeps a few preferences, and your AI Chat conversations, in your browser's storage.
• A chat-widget preview page keeps the preview conversation in your browser's storage once you send a message. An AI model outside South Africa writes the widget's replies (section 4).
• Error monitoring (Sentry) sets no cookies and stores nothing in your browser. It does receive your IP address and a short record of each page load, and a report when something breaks (section 8).
• We don't use visitor-analytics or advertising tools. The only monitoring data our site sends to another company is the error, session and page-speed data that Sentry receives (section 8). Vercel Web Analytics and Speed Insights are built into our code but switched off (section 9).

Every cookie we set is strictly necessary. The items we keep in your browser's storage only remember your settings and your conversations on your own device, or carry an item from one dashboard page to the next. Nothing we set or store is used for marketing or tracking, so we don't ask for cookie consent. Section 11 gives our legal grounds.

4. Public pages of yielde.dev

Our public pages set no cookies. They save nothing in your browser's storage, except that a "page not found" page may save your light or dark look.

When any page on yielde.dev loads, it reads the appearance items below, if your browser already holds them, so that it can show the look you chose. The sign-in and sign-up pages, the platform checkout and the dashboard save yielde-theme, and a "page not found" page may save it too. Only the dashboard's appearance settings save the other two.

These items hold only a setting, such as "dark" or a number. They don't identify you, and your browser does not send them to us.

Chat-widget preview pages. A platform customer can share a preview page (an address that starts with yielde.dev/embed/preview/), so that people can try its chat widget before it goes on the customer's own website. The preview page sets no cookies. Once you send a message, it keeps the conversation in your browser, as the real widget does.

Each message you send goes to our servers, and on to that customer's automation workspace, so that the widget can reply. That workspace runs on the Yielde platform. It sends your message through OpenRouter to an AI model outside South Africa, which writes the reply (section 12, and Privacy Policy sections 9 and 10).

Who is responsible for these messages depends on whose workspace the preview shows. If it is a Yielde customer's workspace, that customer is the responsible party for the messages that reach it, and we process them as its operator under our agreement with it (Privacy Policy section 10). If it is Yielde's own demo workspace, we are the responsible party (Privacy Policy section 4.6).

The old chat assistant. Earlier versions of our public pages had a chat assistant that stored yielde-chat:session, yielde-chat:messages and yielde-chat:consent in your browser. We have removed it, and the site no longer reads or writes those items. If you visited our site before, some of them may still be in your browser until you clear site data for yielde.dev.

5. Signing in and the client dashboard

These are set only if you sign in, or open a sign-in or digest link that we emailed to you.

Cookies (strictly necessary).

Browser storage in the dashboard.

What the dashboard sends to us. Your appearance settings and the side-panel setting stay in your browser and are not sent to us. When you continue an AI Chat conversation, the dashboard sends that conversation to our servers, and on to AI model providers, so that the AI can reply (section 12, and Privacy Policy section 10). An item you chose to ask the AI about goes with your next message. A digest link's access code is sent to our servers once, to open the review.

On a shared computer, sign out when you finish and clear site data for yielde.dev. That removes your AI Chat history and settings from that browser.

6. Venuo

If you use Venuo, our enquiry desk for wedding and function venues, its own privacy notice at https://venuo.co.za/privacy/ applies.

7. Payment windows

Paying on yielde.dev. Our payment pages (section 1) load Paystack's payment script. When you pay, Paystack's secure payment window opens on our page. Paystack, and the security service it uses (Cloudflare), may set their own cookies on Paystack's web addresses when the script loads and in the payment window. For example, when we checked on 27 September 2026, Paystack's servers set a cookie called __cf_bm, which lasts 30 minutes. Paystack's own privacy notice covers these cookies. We don't set them or read them. The platform checkout also saves your light or dark look in your browser (section 4).

8. Error monitoring (Sentry)

We use Sentry only to find and fix errors and slow pages on yielde.dev, including the dashboard.

• Sentry sets no cookies on our site and stores nothing in your browser.
• Each time a page loads, Sentry receives a short session record: a random session number, when the session started and ended, whether an error happened, the version of our site, and your browser's user-agent string. That string names your browser, its version and your operating system.
• Sentry also sees your IP address when your browser connects to it.
• When something breaks, Sentry also receives an error report: the page address, your browser and device type, and the technical details of the error.
• For about 1 in 10 page loads, it receives timing data about how the page loaded.
• Before an error report or timing data leaves your browser, our code removes secrets and cookies, masks email addresses, and masks phone numbers written in international format (+27…).
• Sentry keeps this data in its EU data region (Germany), for the period set in our Sentry retention settings.

We rely on our legitimate interest in running a secure, working service (POPIA section 11(1)(f)). You may object to this at any time, free of charge, on reasonable grounds relating to your own situation (POPIA section 11(3)(a)). To object, contact us (section 18). Section 14, and section 16 of our Privacy Policy, explain your rights.

9. Tools that are built in but switched off

The site's code includes Vercel Web Analytics, Vercel Speed Insights and a web-performance reporter. They are switched off. Their code is in the files your browser downloads from our site, but it does not run. Your browser never fetches their scripts, and they set no cookies, store nothing in your browser and collect nothing.

We don't use visitor-analytics or advertising tools. The only monitoring data our site sends to another company is the error, session and page-speed data that Sentry receives (section 8). We will not switch these tools on without first updating this policy and the Privacy Policy, and giving notice of the change as the Privacy Policy sets out. If we ever switch them on, we will use them only in aggregated, anonymised form, to spot and fix problems. We will not use them to build a profile of you or to track you across other websites.

10. What we don't use

• We don't use advertising or marketing cookies.
• We set no third-party cookies ourselves. The only third-party cookies on our pages are Paystack's, on our payment pages (section 7).
• We don't use error monitoring, or any cookie or stored item, to build a profile of you, and we don't track you across other websites.
• We don't sell personal information.

If this ever changes, we will update this policy and obtain your consent before any marketing or advertising cookie, or any similar stored item, is set.

11. Our legal grounds and consent

South Africa has no separate "cookie law". Cookies and browser storage are governed by the general rules in POPIA, and electronic communications by the Electronic Communications and Transactions Act 25 of 2002 (ECTA).

• Strictly necessary cookies (section 5) are set without asking first. They are essential to a service you have asked for: signing in to the dashboard, opening a link we emailed you, and keeping your session secure. We rely on grounds in POPIA section 11(1) other than consent: that the processing is necessary to perform our contract with you, where you are our customer (POPIA section 11(1)(b)), and our legitimate interest in running a secure, working site (POPIA section 11(1)(f)).
• Appearance settings and the dashboard's browser storage (sections 4 and 5). They are part of the dashboard service you use (POPIA section 11(1)(b), where you are our customer), and we have a legitimate interest in pages that remember your settings (POPIA section 11(1)(f)). You can delete them at any time (section 14). Appearance settings stay in your browser and are not sent to us. When you continue an AI Chat conversation, the dashboard sends that conversation to our servers, and on to AI model providers, so that the AI can reply (section 12). AI Chat is part of the platform service. The sign-in and account details that let you use AI Chat are ours to look after: we rely on POPIA section 11(1)(b) where you are our customer, and otherwise on section 11(1)(f). What you type into AI Chat is your business's content, and we process it as your operator under the Data Processing Agreement (Privacy Policy section 10).
• The chat-widget preview (section 4). We keep the preview conversation in your browser so that the preview works like the real widget. We rely on our legitimate interest in letting people try a customer's widget before it goes live (POPIA section 11(1)(f)). You can delete it at any time (section 14). Where the preview shows Yielde's own demo workspace, we also rely on our legitimate interest in showing people how the widget works (POPIA section 11(1)(f)) to send your messages to that workspace and on to an AI model that writes the reply. You may object at any time (Privacy Policy section 16 explains how).
• Error monitoring relies on our legitimate interest (section 8).
• Consent. If we ever need your consent for a cookie or stored item, we will ask before we set it, and your consent can be given electronically. Under ECTA section 13, an electronic indication of agreement is not without legal force merely because it is in electronic form. Silence, a pre-ticked box or a failure to opt out is never consent.

12. Transfers outside South Africa

Some of the services behind these cookies and stored items are outside South Africa.

• Sign-in: your session is checked against our sign-in database, Supabase, hosted in AWS eu-west-1 (Dublin, Ireland, EU).
• Hosting: Vercel serves yielde.dev from the United States and a global edge network.
• Error monitoring: Sentry's EU data region (Germany).
• AI Chat: when you continue a conversation, it goes to our servers. Our servers send each call to OpenRouter, which passes it to the provider of the model you chose. This includes AI Chat's web search and video generation. OpenRouter and these providers are in the United States and other countries (OpenRouter operates globally), so we treat every AI Chat message as a transfer outside South Africa (Privacy Policy sections 9 and 10).
• Chat-widget preview: your messages first reach the customer's workspace on the Yielde platform, which runs on Vercel (serverless) and Supabase (eu-west-1). From there they go through OpenRouter to an AI model provider in the United States or another country, as for AI Chat. For a customer's workspace, the transfer basis is the one in our agreement with that customer (Privacy Policy section 10). For Yielde's own demo workspace, it is the basis our Privacy Policy gives for our demos (section 9).

A transfer of personal information to another country is subject to POPIA section 72. South Africa has no published list of adequate countries and no standard contractual clauses from the Information Regulator. For Supabase, Vercel and Sentry we rely on their written data-processing terms (POPIA section 72(1)(a)). For AI Chat, and for a preview of a customer's workspace, we act as our customer's operator, and the transfer basis is set out in, and carried down through, the Data Processing Agreement. Our Privacy Policy (section 9) gives the basis for each flow and the level of protection in each destination, and our Sub-processor Register lists the providers.

13. How long cookies and stored items last

We keep cookie-related personal information only as long as we need it for the purpose it was set for, in line with POPIA section 14. The tables in sections 4 and 5 give each item's lifetime. Session storage is cleared when you close the tab. Items in localStorage stay until you clear site data. Sentry's session records, error reports and timing data are kept for the period set in our Sentry retention settings.

14. How to manage, change or delete them

• In your browser. You can block or delete cookies and site data in your browser's settings. Most browsers let you refuse all cookies, accept only first-party cookies, or delete existing ones. Clearing site data for yielde.dev removes your appearance settings, your AI Chat history and any preview conversation, and signs you out. You can delete Paystack's cookies in the same way.
• Strictly necessary cookies. If you block or delete the cookies in section 5, you won't be able to sign in or stay signed in to the dashboard.
• Your POPIA rights. To use your rights of access, correction, deletion and objection (POPIA sections 11(3) and 23 to 25) over personal information we hold as a responsible party, contact us (section 18). For personal information we process for one of our customers as its operator, contact that customer. We will assist the customer in responding.

15. Children

Our website and client dashboard are for businesses and the people who act for them, not for children. We do not knowingly set non-essential cookies that target children.

16. How this policy relates to the Privacy Policy

This policy is part of our wider privacy framework. For full detail on the personal information we process, our legal grounds, our service providers, cross-border transfers, retention, security, security compromises and your rights, read our Privacy Policy. If the two conflict on the subject of cookies or browser storage, this policy governs. On every other matter, the Privacy Policy governs.

17. Changes to this policy

We may update this policy when the cookies or storage we use change, or when the law changes. The effective date at the top of the page will change accordingly. We will update this policy before we add any new cookie or stored item.

18. Contact

Questions about cookies on our sites, or requests about your personal information, can go to support@yielde.dev, 063 611 2952, or Splice Computers (Pty) Ltd t/a Yielde, 55 York Street, George, Western Cape, 6529, South Africa.

You also have the right to lodge a complaint with the Information Regulator of South Africa: https://inforegulator.org.za, POPIAComplaints@inforegulator.org.za. Our Privacy Policy (section 17) gives the Regulator's full contact details.