Skip to content
Daybound
  • How it works
  • Free vs Pro
  • Screenshots
  • Pricing
  • FAQ
  • English
  • Español
Get it free

¿Prefieres español? Cambiar a español

Security Policy

Last updated: 2026-11-21

On this page

  1. Report a vulnerability
  2. What happens next
  3. Safe harbor
  4. Supported versions
  5. How we build Daybound

Daybound runs inside online stores that take real orders, so security is not optional. This page explains how we build the plugin and how to report a problem.

Report a vulnerability#

Please write to seguridad@usedaybound.com with the subject “Security”. Do not open a public forum thread for security issues. Include:

  • the plugin version and whether Pro is active;
  • the steps to reproduce the issue and its impact;
  • a proof of concept, if you have one.

Our machine-readable contact is also published at /.well-known/security.txt.

What happens next#

  • We acknowledge your report within 3 business days.
  • We confirm the issue and tell you how severe we think it is.
  • We aim to release a fix within 7 days for critical or high-severity issues and within 30 days for others.
  • The fix is shipped as an update to both the free plugin on WordPress.org and Pro, and the changelog marks it as a security release.
  • We credit you in the changelog if you want, once the fix is available.

We ask you to give us up to 90 days to release a fix before you disclose the issue publicly.

Safe harbor#

We will not take legal action against research done in good faith that follows this policy. Good faith means: test only on your own installation, never on stores you do not own; do not access or change other people’s data; and do not degrade services such as WordPress.org, Freemius or this website.

Supported versions#

Security fixes are released for the latest version only. Keep Daybound updated; WordPress can do it automatically for you.

How we build Daybound#

  • The server decides. Every delivery date is validated again on the server before it is saved, whatever the browser sends.
  • WordPress security APIs. All settings pages use permission checks and nonces. Database queries are prepared. All output is escaped.
  • Release gates. A release is blocked unless it passes the automated PHP and JavaScript tests, WordPress security coding standards (PHPCS), and a check of known vulnerabilities in dependencies.
  • Independent review. The code is reviewed for security before releases. The first audit (November 2026) found no critical issues, and the significant findings were fixed in version 1.0.1.
  • Least data. The free plugin has no telemetry. Customer delivery data never leaves your store. See our Privacy Policy.

Daybound

Delivery dates for the WooCommerce block checkout. Version 1.0.1.

Plugin

  • WordPress.org plugin page
  • Support forum
  • Pricing

Legal

  • Terms of Service
  • Privacy Policy
  • Refund Policy
  • Personal Data Processing (Colombia)
  • Security

Contact

soporte@usedaybound.com

© 2026 Daybound. WooCommerce is a trademark of Automattic Inc.; this plugin is not affiliated with or endorsed by it.