Access
Secure sessions, hashed passwords and role separation.
Security
Security starts with simple, consistent choices in the application.
Secure sessions, hashed passwords and role separation.
Conversations and accounts stored with utf8mb4 encoding and prepared queries.
Public pages are indexable, private areas are noindex and admin is protected.
Server errors are logged without exposing details to visitors.
Application controls
FeedbackChat separates marketing pages, logged-in accounts, payment and administration. That separation reduces risk and makes audits easier.
Accounts use password_hash, HTTP-only sessions and session id regeneration after login. Private pages verify the session before showing account data.
MySQL queries use PDO prepared statements to reduce SQL injection risk. Connection failures are logged server-side and converted into readable user messages.
The superadmin folder is protected by HTTP Basic Auth through .htaccess and by a PHP fallback check if the server ignores Apache rules. Admin pages are noindex.
The payment page uses Stripe Payment Links so no secret key is exposed in the browser. Real keys and links stay in server configuration.
Public pages are indexable, while private and superadmin areas are excluded from robots.txt. Canonical tags prevent duplicates between old technical URLs and clean URLs.
MCP integrations should be limited to approved sources: CRM, product catalog, billing or documentation. AI assistants should receive only the data needed to answer.
Before production
This page explains the important practices for customer messaging software: account security, shared inbox protection, conversation privacy, Stripe payment, superadmin access, WordPress integrations, Joomla modules, MCP connectors and AI assistance. The content helps search engines associate FeedbackChat with SaaS security, customer chat and multilingual support topics.
Typing...