Source
Privacy policy — found from the homepage — Fleep
Checked for Fleep on 30 Sep 2026
- Page
- https://fleep.io/privacy
- Checked
- 30 Sep 2026, 12:40 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e9fcaaecb6788f45c743020057c59edde6e87212147ae3a09e7e01658ca562f5
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Provider region Report an error
“your data is stored in servers hosted by Amazon Web Services, located in the territory of European Union”
-
Encryption at rest transit Report an error
“All messages and files are stored and transmitted in an encrypted form.”
-
Retention deleted messages Report an error
“The messages and files in a conversation will be deleted from the Service within 14 days after all recipients have deleted them or the deleted their Fleep user account.”
-
Account deletion contact Report an error
“You may withdraw your consent for further processing of your personal data by deleting your user account by sending a pertinent request to support@fleep.io.”
-
Retention policy Report an error
“We will retain your personal information only as long as you have an user account with Fleep.”
-
Fleep for business admin control Report an error
“The accounts (“Premium accounts”) and conversations (“Premium conversations”) created under Fleep for Business or transferred to the Fleep for Business are fully owned by the organization and its administrators have full administrative control over them.”
-
Cookie types Report an error
“We use both "session" cookies and "persistent" cookies in the Service.”
-
Data import email contacts Report an error
“If you allow, we may access and import your emails together with attached files from your email mailbox provided by Google or Microsoft or by other email providers and store the copy of them in the Service to map them into your conversations as messages.”
8 facts read from this page are not shown because they could not be confirmed on the page as captured.