Million Dollar Script stores the information needed to reserve inventory, process payment, manage placements, and display approved advertising. Site owners remain responsible for configuring WordPress, payment providers, analytics, email delivery, legal pages, and retention practices for their jurisdiction and use case.
This guidance is operational information, not legal advice.
Privacy Responsibilities
- Publish accurate privacy, terms, refund, advertising, and contact pages before accepting orders.
- Collect only the customer and placement fields needed for the service being offered.
- Keep customer email addresses, order keys, manage tokens, API keys, license keys, payment references, and unpublished placement metadata private.
- Review each extension's privacy and retention settings. Extensions that collect submissions may add their own WordPress personal-data export and erasure support.
- Keep custom placement fields private by default. Publish a value in a grid popup or on an individual advertiser page only when the advertiser understands and permits that public use.
- Document external processors such as WooCommerce gateways, SMTP providers, analytics services, ImageGrid, map tiles, or hosted extension services.
- Use the WordPress privacy tools and provider dashboards that apply to the data being processed. A database or CSV export may contain personal information and must be handled securely.
Anonymous Version Analytics
Direct-download editions send a versioned, privacy-bounded analytics snapshot with the existing WordPress core update check unless Disable Anonymous Version Analytics is enabled in Million Dollar Script -> Settings -> System. No additional scheduled request is created.
The snapshot contains the Million Dollar Script generation and version, WordPress and PHP versions, update channel, and the slug, version, and active state of installed first-party Million Dollar Script extensions. It is limited to 64 extensions identified by an official milliondollarscript.com plugin or author URL. Other WordPress plugins, settings, content, customer records, license keys, API keys, and payment data are not included.
The service converts the normalized site address to a keyed one-way hash before storage, keeps only the current extension snapshot for that hash, reports extension use only as aggregate counts, and removes installation analytics after 365 days without an update check. Disabling analytics sends the opt-out header on later checks, omits the snapshot, and stops analytics storage without disabling update delivery.
Security Checklist
- Use HTTPS for WordPress administration, checkout, order management, extension-server connections, and hosted rendering.
- Give administrators and API clients only the capabilities or scopes they need.
- Revoke unused API keys, license activations, tester access keys, and staff accounts promptly.
- Keep WordPress, Million Dollar Script, maintained extensions, WooCommerce, PHP, the database, and the operating system updated.
- Use tested backups, malware monitoring, rate limiting, and an SMTP provider appropriate for the site.
- Never paste secrets into public support requests, screenshots, analytics, or email templates.
- Test checkout and renewal callbacks with provider sandbox credentials before accepting live payments.
Accessible Operation
Million Dollar Script uses labels, keyboard-operable controls, live status messages, responsive lists, and accessible names throughout its standard interfaces. Site themes and custom templates can still reduce accessibility.
Before launch:
- Complete an order using only a keyboard.
- Check focus visibility, error announcements, field labels, and logical tab order.
- Verify text and control contrast in both the selected light and dark appearances.
- Test the grid, order form, tooltips, account pages, legal pages, and extension forms at narrow mobile widths and at browser zoom levels up to 200%.
- Add meaningful alternative text to placement images. Avoid putting essential text only inside an image.
- Check custom popup templates and custom fields with a screen reader before publishing them.
If a theme overrides Million Dollar Script styles, keep the override scoped and preserve focus outlines, labels, status regions, and touch target sizes.
Incident Response
If a key, token, customer record, or private document may have been exposed, revoke the credential or access immediately, preserve relevant audit information, investigate the affected records, and follow applicable notification requirements. Report a reproducible Million Dollar Script security issue privately through the contact method on the official site rather than posting exploit details publicly.
Service Access Diagnostics
Open Million Dollar Script -> System Status and run Network diagnostics when extension discovery, updates, licensing, or hosted rendering cannot connect. Each endpoint is checked independently so an extension-catalog failure is not confused with an ImageGrid readiness or account problem. The report keeps only the endpoint path, result class, timing, and a provider request ID when one is returned; it does not store response bodies, API keys, license keys, or signed URLs.
A 401 or 403 result does not identify the cause by itself. It may come from missing authorization, account or payment policy, an operator WAF rule, IP reputation, a provider restriction, or a legally required trade-control decision. Keep the timestamp and request ID for support. Do not attempt to evade an access decision.
Public grids continue using Million Dollar Script's local renderer when ImageGrid is unavailable. Extension installation, premium entitlement checks, purchases, and hosted processing require their respective services and cannot be guaranteed in every region or during every provider outage. Keep current package backups and export important site data before a service change or account closure.