Privacy Policy.

Who this policy covers and our privacy roles

This policy applies to RumbleForms, operated by Rumble Websites from Cape Town, Western Cape, South Africa. It covers visitors to forms.rumblewebsites.co.za, account holders, people completing RumbleForms-powered forms, and people whose details appear in billing or support records.

When RumbleForms decides the purpose

Rumble Websites is the responsible party for information used to run RumbleForms itself—for example account registration, authentication, platform security, service analytics, support and billing records.

When a customer business decides the purpose

For answers submitted through a customer’s form, that customer business generally decides what to collect and why. It is usually the responsible party, while RumbleForms acts as its operator by receiving, storing and delivering the submission under the customer’s instructions. Questions about why a particular business requested information should normally be directed to that business first.

Information we collect

The information depends on how you interact with RumbleForms and may include:

• Account information: email address, account status, selected plan, verification and last-login dates.
• Authentication and security: hashed login tokens, session information, IP address, browser or device information, rate-limit activity and security events.
• Form settings: form and business name, connected domains, receiving email, redirect URL, form status, builder fields and visual styling, access key, embed token, uploaded branding and per-form watermark entitlement.
• Submission information: the fields completed by the form visitor, sender email where supplied, subject, source domain, IP address, browser information and submission time.
• Communication and AI records: operational email jobs, delivery attempts, support messages, per-form AI conversations and approved AI action plans, AI credit usage, deliberately submitted experience ratings and optional feedback comments.
• Billing information: plan, submission- or AI-credit quantity, selected watermark-removal form, price, currency, PayFast transaction and subscription references, payment status, consent record, IP address and browser information.
• Usage and analytics: page or form viewed, referrer host, approximate country, locale, timezone, device type, browser family, operating system and a hashed visitor identifier.

Please do not submit information that a form does not reasonably need. A form owner can choose its own fields, so the form owner’s privacy notice should also be read before submitting.

Why we use information

We process information where it is necessary to provide the requested service, comply with law, protect legitimate operational and security interests, or act on consent where consent is required. Uses include:

• creating and securing accounts and sending time-limited sign-in emails;
• validating domains, access keys, quotas and form submissions;
• storing submissions, showing them in the dashboard and emailing them to the selected recipient;
• sending a submission acknowledgement to the form visitor where an email is supplied;
• processing plan subscriptions, cancellations, refunds, submission- and AI-credit purchases and per-form watermark removal;
• providing the optional per-form AI assistant, preparing user-approved design changes and drafting replies for the account holder to review;
• detecting spam, abuse, security threats, duplicate payments and technical failures;
• providing support, keeping audit records and resolving disputes;
• understanding broad country, device and usage patterns so the platform can be improved; and
• meeting tax, accounting, payment, legal and regulatory obligations.

We do not sell personal information. We do not use form-submission content for unrelated advertising, and RumbleForms currently does not place third-party advertising trackers on the service.

LandoBot AI assistant

LandoBot conversations are attached to one form and protected in the database. The account holder may clear that conversation, and deleting the form deletes its linked conversation. Ordinary RumbleForms administration does not display the conversation content. Usage and purchase ledgers may remain where needed for allowances, billing, fraud prevention and disputes.

In the builder, LandoBot is locked to the exact form currently open. Before preparing a response, the builder may save unsaved changes so that the submitted context reflects the latest visible form. RumbleForms may send the account holder’s message, the current form identifier, name, business and website context, fields, field order and widths, visual styling, and the specifically selected field to MiniMax. This lets LandoBot propose changes to that same form or ask a clarification question when the intended field or placement is unclear.

A proposed change is not applied until the account holder sees the action list and credit cost and explicitly approves it. Greetings, ordinary conversation and clarification questions do not use account AI credits. Stopping an in-progress response prevents it from being approved through that interrupted screen and does not itself charge account credits, but a request already transmitted may still finish processing at the provider or remain briefly as an unapproved plan until it expires.

Common support questions may be matched against a RumbleForms-controlled help guide before any request is made to MiniMax. If the account holder then chooses Contact support, RumbleForms collects the name, optional email address, optional phone number, support category and problem description entered into that form. At least one reply method is required. These details, plus the account and current-form identifiers needed to investigate, are queued to RumbleForms support through our email infrastructure and are not sent to MiniMax as part of the support handoff. Completed and permanently failed queue payloads are scrubbed through the normal mail-queue process.

A customer submission is not included automatically. It is shared only when the account holder chooses one specific submission, confirms the disclosure and requests a reply draft. The draft is returned for review and is never sent automatically. The right-click menu can identify a selected builder field to LandoBot; direct edit, move, duplicate or delete actions performed through that menu stay within the normal builder and do not need MiniMax.

MiniMax acts as an external AI processing provider and may process request content outside South Africa under its own infrastructure and terms. Do not place passwords, payment credentials, confidential legal advice or unnecessary sensitive personal information into LandoBot. Optional experience feedback is sent directly to RumbleForms and is not automatically combined with AI conversations or customer submissions.

How form submissions are handled

When someone submits a connected form, RumbleForms checks the access key, form status, domain rules, rate limits and available submission allowance. If accepted, an inbox copy is stored against that specific form and account, and a separate email is queued for the form's selected notification address. Where the visitor supplies an email address, it may also be used for the automatic thank-you email.

The authenticated account holder can open the private per-form inbox, export or permanently delete its records, and reply to a visitor through RumbleForms. Replies are sent by the platform on behalf of the form owner and include RumbleForms identification. The business notification address is used as the reply address where supported.

Submission bodies and sender identifiers are not displayed in Rumble Websites staff or administrator tools, and staff are not permitted to read them as part of ordinary account support. Staff tools are limited to operational information such as counts, timestamps and delivery status. Infrastructure and email providers necessarily process information to host, protect and deliver the service, and narrowly scoped technical or legal handling may still be required where the law or a serious security incident requires it.

Form owners must not use RumbleForms as a hidden mailing-list tool. A submitted email address may be used to respond to the enquiry, but separate marketing requires its own lawful basis and opt-out process.

PayFast and payment information

RumbleForms uses PayFast for self-service payments. When you continue to PayFast, PayFast receives details needed to process the transaction, such as your account email, amount, currency, item description, payment reference and return or notification URLs.

Card or bank credentials are entered on PayFast’s systems. RumbleForms does not receive or store your full card number, banking password or CVV. We do retain payment references, amounts, status, subscription token, billing period, the purchased submission- or AI-credit quantity, the saved form selected for a watermark-removal purchase, and consent records so that we can activate the correct service, manage cancellation, reconcile payments and respond to disputes.

PayFast processes information under its own Privacy Policy and applicable end-user terms. Banks and payment-method providers may also process the transaction under their own policies.

Cookies, local storage and limited analytics

RumbleForms uses a secure session cookie to keep signed-in users authenticated. It is marked to reduce script access and cross-site use. The public site also uses browser local storage for:

• a random visitor identifier that is hashed before analytics storage; and
• the visitor’s chosen pricing currency.

Analytics records may include page path, referrer host, approximate country inferred from network headers or browser locale, timezone, device type, browser and operating system. We do not store the raw local visitor identifier in the analytics table.

The public pricing page may contact country.is to suggest a display currency and Frankfurter to obtain a currency conversion rate. Those providers receive normal web-request information such as your IP address. Displayed conversions are informational; PayFast charges remain in ZAR. The homepage may also load font resources from Google, which receives ordinary request information.

You can clear cookies and local storage through your browser. Blocking the session cookie will prevent dashboard sign-in; blocking local storage may reset analytics continuity and currency preferences but should not prevent ordinary public-page access.

Who information may be shared with

We share information only where reasonably needed for the service or required by law. Recipients may include:

• the RumbleForms account holder and the form’s selected notification recipient;
• PayFast, banks and payment-method providers for payments, refunds and fraud checks;
• hosting, database, security and email-delivery providers acting under service arrangements;
• MiniMax when an account holder chooses to use the AI assistant, limited to the form and conversation context needed for that request and any specifically authorised submission;
• limited analytics, font, country and currency-rate providers described above;
• professional advisers where genuinely needed for accounting, legal or security support; and
• regulators, courts or law-enforcement bodies where disclosure is lawfully required.

If the business or platform is reorganised or transferred, relevant information may be disclosed under confidentiality and data-protection safeguards. We will not sell a customer list or form-submission database as a standalone asset.

Processing outside South Africa

RumbleForms is a company run under Rumble Websites and operated from South Africa, but some service providers or their infrastructure may be located in other countries. Where personal information is transferred across borders, we aim to use providers and arrangements that offer appropriate protection, contractual safeguards or another lawful basis recognised by POPIA.

A form owner who intentionally collects information from people in another country remains responsible for any additional local privacy rules that apply to its business and for telling RumbleForms if special processing arrangements are required.

How long information is kept

We keep information only for as long as reasonably needed for the purpose, the active customer relationship, security, disputes and applicable recordkeeping duties. Different records have different lifecycles:

• account and form-configuration records are generally kept while the account or form remains active and until deletion is requested or reasonably scheduled;
• dashboard submission copies are scheduled for automatic deletion after 15 days on Free, 30 days on Starter, 60 days on Premium and no more than 365 days on Professional;
• the account holder may permanently delete one, several or all dashboard submission copies sooner; delivery totals may remain as de-identified aggregate statistics;
• login links expire after a short period, although related security records may remain for audit and abuse prevention;
• queued email records may remain to show delivery attempts and diagnose failures;
• analytics records may be retained in hashed or aggregated form for platform trends and security;
• payment, consent, refund, tax and fraud records may be kept for the period required by law, payment-provider rules or a legitimate dispute; and
• per-form AI conversations remain until the account holder clears them or deletes the linked form; AI usage and purchase ledgers may remain for billing, abuse prevention and dispute records;
• security logs and limited residual backup copies may remain temporarily after ordinary deletion.

The dashboard copy is a convenience and recovery aid. Deleting or automatically expiring it does not delete a separate message already delivered to the form owner's external email provider, and RumbleForms cannot guarantee how long that provider keeps it. A new retention schedule may give older inbox records a reasonable transition period before their first automatic deletion so the account holder can review or export them.

When an account is permanently deleted, dependent forms, access keys, submissions and login records are designed to be removed from the active account database. Some provider-held payment records, legally required records, security evidence or de-identified statistics may remain.

How information is protected

RumbleForms uses reasonable technical and organisational safeguards appropriate to the service. These include encrypted HTTPS connections, hashed sign-in tokens, secure session settings, domain allow-listing, access controls, CSRF protection, rate limiting, bot checks, server-side payment verification and administrative audit records.

Access is limited to people and providers who need it for an authorised purpose. No online system is perfectly secure, so we cannot promise that a breach will never occur. If personal information is compromised, we will investigate, reduce the risk and notify the responsible party, Information Regulator and affected people where POPIA or another applicable law requires it.

Account holders should protect their email accounts and access keys, use only trusted devices, remove former staff access and contact us immediately if something looks suspicious.

Your POPIA choices and rights

Subject to POPIA and other applicable law, you may ask whether we hold personal information about you and request access, correction, deletion or restriction where appropriate. You may also object to certain processing, withdraw consent where processing depends on consent, or complain about how information was handled.

If you hold a RumbleForms account

Contact us from the account email. We may need to verify your identity before changing, exporting or deleting account information.

If you submitted a customer’s form

Contact the business named on that form first because it chose the questions and purpose. If you cannot reach it, contact us with the form website, approximate submission date and the email used. We will verify the request and assist the relevant business where reasonably possible.

Requests can be sent to info@rumblewebsites.co.za. We will respond within a reasonable period and will explain if a lawful exception prevents full compliance. POPIA objection and correction/deletion forms are available from the Information Regulator.

You may lodge a complaint through the Information Regulator’s complaints process if you believe personal information has been handled unlawfully.

Children and special personal information

RumbleForms accounts are intended for adults and authorised business representatives. The platform is not designed as a child-directed service. A form owner must not collect children’s information or special personal information unless it has a lawful basis, gives an appropriate notice, obtains any required consent and applies safeguards suitable for the risk.

Do not use ordinary RumbleForms fields to request payment-card credentials, passwords, one-time PINs, medical records or other high-risk secrets. Contact us before using the service for a purpose with unusual privacy or regulatory risk.

Changes to this policy

We may update this policy when the service, providers or legal requirements change. The latest version will remain available here with its update date. If a change materially affects how existing account or submission information is used, we will provide reasonable notice by email, dashboard message or another appropriate channel.