mirror of
https://github.com/chatmail/relay.git
synced 2026-05-19 04:18:09 +00:00
also change privacy policy to circumscribe iroh-relay services
This commit is contained in:
@@ -2,12 +2,13 @@
|
|||||||
|
|
||||||
## untagged
|
## untagged
|
||||||
|
|
||||||
|
- deploy `iroh-relay` (requires new "iroh.{mail_domain}" DNS entry),
|
||||||
|
also update "realtime relay services" in privacy policy.
|
||||||
|
([#434](https://github.com/deltachat/chatmail/pull/434))
|
||||||
|
|
||||||
- add guide to migrate chatmail to a new server
|
- add guide to migrate chatmail to a new server
|
||||||
([#429](https://github.com/deltachat/chatmail/pull/429))
|
([#429](https://github.com/deltachat/chatmail/pull/429))
|
||||||
|
|
||||||
- deploy `iroh-relay` (requires new "iroh.{mail_domain}" DNS entry)
|
|
||||||
([#434](https://github.com/deltachat/chatmail/pull/434))
|
|
||||||
|
|
||||||
- increase `request_queue_size` for UNIX sockets to 1000.
|
- increase `request_queue_size` for UNIX sockets to 1000.
|
||||||
([#437](https://github.com/deltachat/chatmail/pull/437))
|
([#437](https://github.com/deltachat/chatmail/pull/437))
|
||||||
|
|
||||||
|
|||||||
@@ -54,18 +54,18 @@ We have appointed a data protection officer:
|
|||||||
|
|
||||||
## 2. Processing when using chat e-mail services
|
## 2. Processing when using chat e-mail services
|
||||||
|
|
||||||
We provide e-mail services optimized for the use from [Delta Chat](https://delta.chat) apps
|
We provide services optimized for the use from [Delta Chat](https://delta.chat) apps
|
||||||
and process only the data necessary
|
and process only the data necessary
|
||||||
for the setup and technical execution of the e-mail dispatch.
|
for the setup and technical execution of message delivery.
|
||||||
The purpose of the processing is to
|
The purpose of the processing is that users can
|
||||||
read, write, manage, delete, send, and receive emails.
|
read, write, manage, delete, send, and receive chat messages.
|
||||||
For this purpose,
|
For this purpose,
|
||||||
we operate server-side software
|
we operate server-side software
|
||||||
that enables us to send and receive e-mail messages.
|
that enables us to send and receive messages.
|
||||||
Allowing the use of the e-mail service,
|
|
||||||
we process the following data and details:
|
|
||||||
|
|
||||||
- Outgoing and incoming messages (SMTP) are stored for transit
|
We process the following data and details:
|
||||||
|
|
||||||
|
- Outgoing and incoming messages (SMTP) are stored for transit
|
||||||
on behalf of their users until the message can be delivered.
|
on behalf of their users until the message can be delivered.
|
||||||
|
|
||||||
- E-Mail-Messages are stored for the recipient and made accessible via IMAP protocols,
|
- E-Mail-Messages are stored for the recipient and made accessible via IMAP protocols,
|
||||||
@@ -74,9 +74,15 @@ we process the following data and details:
|
|||||||
|
|
||||||
- IMAP and SMTP protocols are password protected with unique credentials for each account.
|
- IMAP and SMTP protocols are password protected with unique credentials for each account.
|
||||||
|
|
||||||
- Users can retrieve or delete all stored messages
|
- Users can retrieve or delete all stored messages
|
||||||
without intervention from the operators using standard IMAP client tools.
|
without intervention from the operators using standard IMAP client tools.
|
||||||
|
|
||||||
|
- Users can connect to a "realtime relay service"
|
||||||
|
to establish Peer-to-Peer connection between user devices,
|
||||||
|
allowing them to send and retrieve ephemeral messages
|
||||||
|
which are never stored on the chatmail server, also not in encrypted form.
|
||||||
|
|
||||||
|
|
||||||
### 2.1 Account setup
|
### 2.1 Account setup
|
||||||
|
|
||||||
Creating an account happens in one of two ways on our mail servers:
|
Creating an account happens in one of two ways on our mail servers:
|
||||||
|
|||||||
Reference in New Issue
Block a user