[{"data":1,"prerenderedAt":10},["ShallowReactive",2],{"legal:en:acceptable-use-policy":3},{"id":4,"title":5,"version":6,"effectiveDate":7,"language":8,"html":9},"acceptable-use-policy","Acceptable Use Policy","1.0.0","2026-08-17","en","\u003Cp>This policy is part of the \u003Ca href=\"\u002Fen\u002Flegal\u002Fterms-of-service\u002F\">Terms of Service\u003C\u002Fa>. It describes what\nyou may not do with Postqron, and what happens when you do it.\u003C\u002Fp>\n\u003Cp>Postqron sends HTTP requests to addresses you choose, on a schedule you choose, from\nour infrastructure and our IP addresses. That capability is useful, and it is also the\ncapability an attacker wants. This policy exists so that the difference between the\ntwo is written down rather than left to judgement.\u003C\u002Fp>\n\u003Ch2>1. Who this applies to\u003C\u002Fh2>\n\u003Cp>Everyone who uses Postqron, on every plan, including the free plan. It also applies to\nanyone you invite into your workspace: you are responsible for their use of the\nservice.\u003C\u002Fp>\n\u003Ch2>2. What you must not do\u003C\u002Fh2>\n\u003Ch3>2.1 Attack, overload or probe systems\u003C\u002Fh3>\n\u003Cp>You must not use Postqron to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>send requests to a system you do not own or are not explicitly authorised to test;\u003C\u002Fli>\n\u003Cli>generate load intended to degrade, exhaust or deny service to any system, including\nthrough high-frequency schedules, many jobs against a single target, or coordinated\nuse of multiple accounts;\u003C\u002Fli>\n\u003Cli>scan, enumerate or probe hosts, ports, paths or credentials;\u003C\u002Fli>\n\u003Cli>reach systems that are not intended to be publicly reachable, including private\nnetworks, loopback addresses, cloud metadata endpoints and internal services — ours\nor anyone else's.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Authorisation matters more than intent. Scheduling a request against a third party's\nendpoint is not made acceptable by calling it a health check.\u003C\u002Fp>\n\u003Ch3>2.2 Circumvent our controls\u003C\u002Fh3>\n\u003Cp>You must not attempt to bypass the technical measures that enforce this policy,\nincluding address filtering, rate limits, plan limits or execution ceilings. This\nincludes using redirects, DNS entries under your control, or proxies to reach a\ndestination we would otherwise refuse.\u003C\u002Fp>\n\u003Ch3>2.3 Use the service unlawfully or abusively\u003C\u002Fh3>\n\u003Cp>You must not use Postqron to break the law, to infringe someone's rights, to\ndistribute malware, to send unsolicited messages, or to process content that is\nunlawful in the jurisdictions where you or your recipients are.\u003C\u002Fp>\n\u003Ch3>2.4 Misrepresent origin\u003C\u002Fh3>\n\u003Cp>You must not present requests originating from Postqron as coming from someone else,\nor use the service to conceal the origin of activity.\u003C\u002Fp>\n\u003Ch3>2.5 Resell or expose the service as your own\u003C\u002Fh3>\n\u003Cp>You must not offer Postqron's execution capability to third parties as a service of\nyour own without a written agreement. Running jobs on behalf of your own clients\nwithin an Agency workspace is expected and permitted; building a product on top of our\nscheduler and selling it is not.\u003C\u002Fp>\n\u003Ch2>3. Shared resources\u003C\u002Fh2>\n\u003Cp>Outbound requests leave from IP addresses shared by all customers, except where a plan\nincludes a dedicated address. The reputation of those addresses is a shared asset: one\ncustomer's abuse degrades the service for everyone. We enforce this policy to protect\nother customers, not to police you.\u003C\u002Fp>\n\u003Cp>We may apply aggregate limits per destination host, and we may refuse or slow requests\nto a destination that shows signs of being targeted rather than served.\u003C\u002Fp>\n\u003Ch2>4. What we do about violations\u003C\u002Fh2>\n\u003Cp>Where the situation allows, we contact you first and give you a chance to fix it.\nWhere it does not — because harm is ongoing, because a third party is being attacked,\nor because we are legally required to act — we may act immediately and tell you\nafterwards.\u003C\u002Fp>\n\u003Cp>Depending on severity we may:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>throttle or block\u003C\u002Fstrong> specific jobs or destinations;\u003C\u002Fli>\n\u003Cli>\u003Cstrong>suspend\u003C\u002Fstrong> the affected jobs while leaving your account otherwise usable;\u003C\u002Fli>\n\u003Cli>\u003Cstrong>suspend the account\u003C\u002Fstrong>, stopping all execution;\u003C\u002Fli>\n\u003Cli>\u003Cstrong>terminate\u003C\u002Fstrong> the account.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>We suspend the narrowest thing that stops the harm. Suspension is not a refund event:\nsee the Terms.\u003C\u002Fp>\n\u003Cp>Where we suspend or terminate, you keep the right to export your data\nfor 30 days,\nunless doing so is unlawful.\u003C\u002Fp>\n\u003Ch2>5. Reporting abuse\u003C\u002Fh2>\n\u003Cp>If you believe someone is using Postqron to attack or abuse a system you are\nresponsible for, write to\n\u003Ca href=\"mailto:abuse@postqron.com\">abuse@postqron.com\u003C\u002Fa>.\nInclude the destination address, timestamps in UTC and, where available, the source IP.\nWe investigate reports and will confirm receipt\nwithin two working days.\u003C\u002Fp>\n\u003Ch2>6. Changes\u003C\u002Fh2>\n\u003Cp>We may update this policy. When a change materially restricts what is permitted, we\ngive you\n30 days'\nnotice before it takes effect, except where a shorter period is required to stop\nongoing harm or to comply with law.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>\u003Cstrong>Contact:\u003C\u002Fstrong> \u003Ca href=\"mailto:hello@postqron.com\">hello@postqron.com\u003C\u002Fa>\n\u003Cstrong>Operated by:\u003C\u002Fstrong> Apdsoftware di Carlo Zuffetti, Via C. Colombo 15, 24047 Treviglio (BG), Italy — VAT 03835250162, REA BG 431224\u003C\u002Fp>\n",1788438713274]