Privacy notice

Who is responsible

The data controller is [FULL LEGAL NAME / TRADING ENTITY], trading as The Redesign Button. Contact: [VERIFIED EMAIL] and [REQUIRED POSTAL CONTACT ADDRESS]. Complete these details before launch.

What we collect

When you enquire, we may collect the selected project type, your existing website address (if supplied), business or project name, contact name, email, optional phone, goals, information about files or photographs you have, feature preferences and comments. We also record your authority confirmation, privacy acknowledgement and separate optional marketing preference. Limited technical data is processed for form security. Please do not submit passwords, API keys or confidential customer information.

When you use the AI chat, your message and the recent conversation context are sent to the Google Gemini service to generate a reply. The server temporarily holds recent chat messages in a PHP session to enable follow-up questions; there is no separate chat-history database in this build. Please do not enter passwords, payment information, customer records or sensitive personal information into chat.

Why we use it and our lawful bases

We use enquiry information to assess the requested website or development work, reply, discuss a quotation and retain reasonable records. Suitable redesign enquiries may also lead to a private homepage preview. [CONFIRM WHETHER PRE-CONTRACTUAL STEPS OR LEGITIMATE INTERESTS APPLY TO EACH ACTIVITY]. Optional marketing, where enabled, requires its own documented legal basis and unsubscribe arrangements.

AI chat messages are processed to answer visitor questions about our services. [CONFIRM AND DOCUMENT THE LAWFUL BASIS FOR AI CHAT PROCESSING BEFORE LAUNCH].

Who receives it

Necessary service providers may include [CONFIRM HOSTING PROVIDER AND LEGAL ENTITY], [CONFIRM BUSINESS MAIL/SMTP PROVIDER], and any approved specialist delivering the work. Secure invoice/payment-link providers apply only after separate acceptance. [CONFIRM PROCESSORS, TERMS, COUNTRIES AND TRANSFER SAFEGUARDS].

The optional AI assistant uses Google Gemini. Messages and recent conversation context are transmitted from our server to Google for processing when you ask a question. [VERIFY THE APPLICABLE GOOGLE TERMS, DATA USE, RETENTION, REGION AND INTERNATIONAL TRANSFER SAFEGUARDS FOR YOUR ACTUAL API PLAN BEFORE LAUNCH].

How long we keep it

Enquiry details: [SET RETENTION PERIOD AND DELETION PRACTICE]. If you become a customer, the contract and necessary records may be kept on a separate documented timetable: [PERIOD]. Security rate-limit identifiers are pseudonymised and normally expire within 48 hours; web server logs may be retained separately by the host: [CONFIRM].

Chat history is retained temporarily in the active PHP session and cleared after one hour of inactivity when the chat is next used; PHP session storage and hosting cleanup depend on server configuration. No permanent conversation history is intentionally written by this site. Google and the hosting provider may have their own retention practices: [VERIFY BEFORE LAUNCH].

Your choices and rights

Subject to the applicable UK data protection law, you may request access, correction, erasure, restriction, objection or portability where relevant. You can withdraw marketing consent at any time without affecting the handling of an existing enquiry. Contact [VERIFIED PRIVACY CONTACT]. You can complain to the Information Commissioner’s Office.

Cookies, security and changes

Our initial site uses no advertising or analytics cookies. The enquiry handler uses an essential short-lived security session cookie to protect form submissions. See cookies. We apply access controls, mail security and minimal operational logs, but cannot guarantee absolute security. Review date: [DATE REVIEWED].

The same strictly necessary PHP security session can be used when the AI chat is opened and messages are sent. Chat requests are initiated only when a visitor uses the assistant. No Google tracking widget is embedded in the page; messages are forwarded server-side to Gemini. Consult the cookies page for details.