Posteo · Terms of Service

Posteo terms of service

Read from Posteo's own page on 2026-11-10. 9 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Effective date

Current as of January 2013

Permitted use

summary: Sending and receiving email
Ability to send and receive emails
Read from Posteo's own page on 2026-11-10

Prohibited use

summary: Sending spam
not to send any spam (and no more than 500 emails per hour and/or 1000 emails per day)
Read from Posteo's own page on 2026-11-10
summary: Commercial advertising or mass standardised emails
The customer will not use the email service to send out advertisements for commercial purposes by email or to send standardised emails to a multitude of recipients.
Read from Posteo's own page on 2026-11-10
summary: Breaking German law or child protection rules
not to break German laws not to break regulations regarding protection of children.
Read from Posteo's own page on 2026-11-10

Caching

The page states nothing on this.

Redistribution

The page states nothing on this.

Attribution

Governing law

jurisdiction: Federal Republic of Germany
The complete legal relationship between Posteo and its customers is exclusively governed by the law of the Federal Republic of Germany.
Read from Posteo's own page on 2026-11-10

Liability cap

Liability applies as per the German law on product liability (Produkthaftungsgesetz).
Read from Posteo's own page on 2026-11-10

Termination notice

period: 14 days’ notice
It can be terminated by the customer or Posteo on a monthly basis with 14 days’ notice.
Read from Posteo's own page on 2026-11-10

Change notice

Customers will be informed of any changes.
Read from Posteo's own page on 2026-11-10

Rate or usage limits referenced

not to send any spam (and no more than 500 emails per hour and/or 1000 emails per day)
Read from Posteo's own page on 2026-11-10

Document

Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page