Paid authority is checked
Supported paid operations rely on server-verified account authority and entitlement state rather than trusting a client screen or local flag.
Security principles
Control that assumes every boundary matters.
SEOPlexa is designed around explicit account authority, device-aware access and separated environments. Security controls reduce risk; they do not make any system invulnerable.
Device-aware access
Licensed-device allowance is part of the product access model. Customers should use the account and device-management flows provided by the product.
Fail closed for paid work
If a required authority check cannot be completed, supported paid execution should not proceed. Local and third-party systems may have their own independent state.
Environment separation
Development, staging and production are operated as distinct environments. Authentication and service configuration should remain scoped to the intended environment.
Provider credentials
Use provider-managed credential controls and keep API keys out of URLs, screenshots and shared logs. Third-party providers control their own account security and retention.
Encrypted transport
Customer-facing web traffic is served over HTTPS. Keep the operating system, local SEO tools and provider integrations current, and review access when a device is no longer used.