Privacy Policy

Forgable is operated by [ to be completed: registered company name ], registration number [ to be completed: CIPC registration number ], of [ to be completed: registered / physical address ] (“Forgable”, “we”, “us”). We are the responsible party for the information described in clause 3.

Our Information Officer, registered with the Information Regulator as POPIA requires, is [ to be completed: Information Officer's full name ], reachable at [ to be completed: Information Officer's email address ]. For anything else, email hello@theappforge.app — a person answers.

Forgable builds and hosts apps for you. Two different sets of personal information are involved and they are not treated the same:

• Yours. Your account, what you ask the builder for, what you pay. We are the responsible party. This policy is about that.
• Other people’s, that you put in. Your customers in an app you built, your staff in the payroll tool, the contacts in your business workspace. That information is yours — you decide why it is collected and what happens to it, and you are the responsible party for it. We only store and process it so your app works, on your instruction. In POPIA’s language we act as your operator (section 21), we keep it confidential, we do not use it for anything of our own, and we tell you if we ever have reason to believe it has been accessed by someone who should not have. It is your job, not ours, to have a lawful basis for it and to tell those people what you are doing with it.

What we do not do

There are no advertising trackers, no third-party analytics, no advertising identifiers and no “data partners” in Forgable. We do not sell personal information, and we do not use your prompts, your code or your customers’ data to train AI models. We do not ask for your location, your contacts, or your card number.

Forgable runs on other companies’ infrastructure. Each is bound by its own contract with us, and each gets only what it needs:

Some of these are outside South Africa. POPIA section 72 allows that where the recipient is subject to binding rules or a contract that gives comparable protection; each of the above is engaged under its standard data-processing terms. If that matters to you, ask us and we will tell you exactly which sub-processors touch your account.

This deserves its own clause because people are surprised by it. When you ask Forgable for a change, we send the model your request, your app’s standing instructions, and the contents of the files in your app that it needs to read or write — which can include configuration and, if you put them there, real records. Build failures are sent too, so the model can fix them. Answers come back as file changes we commit to your app.

Do not paste secrets, identity numbers, medical information or anyone else’s private data into the builder chat, and do not ask the model to read a file full of live customer records. Nothing in your app’s database is sent to a model unless you specifically ask for something that reads it.

Under POPIA section 11 we process your information because it is necessary to perform the contract you entered into when you created an account; because we have a legitimate interest in keeping the service running, secure and paid for; and because some of it we are obliged by law to keep, such as records of payments. Where we rely on your consent — for example if we ever send you something that is not about your own account — you can withdraw it at any time.

• Your account and everything in it: until you delete it, or until the account is closed as described below.
• Free apps: an app nobody opens for 3 days has its database paused to save cost. After 23 days we email you a warning, and at 30 idle days the app and its database are deleted. This is stated on the pricing page too.
• Paid apps: databases are paused after 14 days of no use (30 on Business) and woken the moment somebody visits. They are never deleted for being idle.
• Financial records — what you paid, when, and for what — are kept for at least five years, as South African tax law requires.
• When an account is deleted we keep one record: the account id, the email address that asked, the dates, and how much there was — the number of apps, not their names or addresses. It is how we can prove the deletion happened and answer you afterwards. If one of our providers refuses a deletion, the name of whatever is still standing is kept as well, until a person has removed it by hand; then that goes too.

You can delete your Forgable account yourself, from inside the app (Account → Delete my account) or from forgable.app/delete-account, which you can reach without the app.

You are shown exactly what will be destroyed before you confirm, and you must type a confirmation phrase. Then: any monthly plan is cancelled immediately, so nothing more is charged. Your apps keep running for 7 days — long enough to change your mind, and long enough that a live business app does not vanish the moment somebody taps a button. You can cancel the deletion at any point in those 7 days by signing in and pressing “Keep my account”.

After 7 days, permanently and without further notice:

• each app’s Cloudflare Worker is deleted, so the app stops answering;
• each app’s database is deleted — the whole Supabase project for a paid app, or its schema on the shared database for a free one — including your app’s own users and everything they put in it;
• each app’s code repository on GitHub is deleted;
• any custom domain is released from our network, so you can point the name wherever you like (the name stays yours at your registrar);
• your account, profile, builder history, business workspace, credit ledger and payment records in Forgable are deleted.

Unused credits are forfeited, not refunded. If an upstream provider refuses one of those deletions we retry; if it still fails after several attempts your account is deleted anyway and a person finishes the leftovers by hand. Want your work first? Ask before you delete and we will hand over the repository and a database dump.

POPIA gives you the right to:

• ask what personal information we hold about you and where we got it (section 23);
• ask us to correct or delete information that is wrong, misleading, out of date, or that we no longer have a reason to keep (section 24);
• object to processing that rests on our legitimate interest (section 11(3));
• withdraw consent where consent is what we relied on;
• not be subject to a decision about you made purely automatically (section 71); we make no such decisions;
• complain.

Ask us first — hello@theappforge.app — and we will answer within 30 days. If we have not put it right, complain to the Information Regulator (South Africa), inforegulator.org.za, [ to be completed: the Regulator's current complaints email address — check it on their site before publishing ].

Every connection is encrypted. Each customer’s rows are separated in the database by row-level security, and the keys that let our server act on your behalf are held as secrets on the platform, never in the code and never in a browser. Credentials we push to your app’s build pipeline are encrypted to that repository’s own key before they leave us, and store signing keys are never stored in our database at all.

No system is perfectly secure, and we will not pretend otherwise. If a breach affects your personal information we will notify you and the Information Regulator as POPIA section 22 requires.

Forgable sets no advertising or tracking cookies. Your browser (or the app) keeps your sign-in token so you stay signed in, and your light/dark preference. The app also caches its own static files so it opens quickly. Clearing site data signs you out and removes all of it.

Forgable is for people running a business and is not intended for anyone under 18. We do not knowingly create accounts for children. If you believe a child has an account, tell us and we will delete it.

If we change this policy we update the date at the top, and if the change matters to you we will say so by email or in the app before it takes effect.