❌ Software Removal | Soverin Email Provider #1759

New Issue

2020-03-05T01:02:22Z

Zenithium commented

2020-03-05 01:02:22 +00:00

(Migrated from github.com)

Description

Soverin requires disclosing a phone number on registration.

Why I am making the suggestion

This is against the criteria:

"Don't require personally identifiable information (PII) besides username and password."

## Description Soverin requires disclosing a phone number on registration. ## Why I am making the suggestion This is against the criteria: - "Don't require personally identifiable information (PII) besides username and password."

👍 4 😕 1

5a384507-18ce-417c-bb55-d4dfcc8883fe commented

2020-03-05 02:18:07 +00:00

(Migrated from github.com)

Mmm, this is some big shit. I wonder if sending an e-mail to them may do something to change this.

Zenithium commented

2020-03-05 02:32:53 +00:00

(Migrated from github.com)

@5a384507-18ce-417c-bb55-d4dfcc8883fe @dngray said he would mail them to see what can be done about this but I doubt anything will come of it. The phone number requirement is spread all throughout their policies and by their wording they seem to consider it essential for providing the service. Hoping that they resolve this though, supposedly they require it for password recovery but it seems like a nonsense half-truth. One other reason would be spam prevention but the service is already pay-to-use so I don't see any reason why they need a phone number as mandatory for registration.

👍 4

5a384507-18ce-417c-bb55-d4dfcc8883fe commented

2020-03-05 13:53:49 +00:00

(Migrated from github.com)

I think they deserve to be delisted if they won't change that, CTemplar is going to be added soon (I think) and there are quite a few providers that even give you free tiers, so I don't think they deserve it, if you keep in mind that most SIM cards are literally tied to you ID.

dngray commented

2020-03-07 13:47:01 +00:00

(Migrated from github.com)

I've sent them an email, we'll see if we can get some more details.

👍 3

blacklight447 commented

2020-03-26 10:22:54 +00:00

(Migrated from github.com)

@dngray Any word from them so far?

dngray commented

2020-03-26 19:02:19 +00:00

(Migrated from github.com)

I sent them a follow up reply, I guess we will see where it goes.

I'm happy to be lenient for the time being given the state of the world at the moment.

I sent them a follow up reply, I guess we will see where it goes. I'm happy to be lenient for the time being given the state of the world at the moment.

dngray commented

2020-03-27 03:29:00 +00:00

(Migrated from github.com)

I did get a reply, apparently they are "looking into it".

👍 3

fabianski7 commented

2020-04-17 16:35:37 +00:00

(Migrated from github.com)

up

blacklight447 commented

2020-05-05 07:37:48 +00:00

(Migrated from github.com)

@dngray any updates?

dngray commented

2020-05-05 08:59:04 +00:00

(Migrated from github.com)

@dngray any updates?

Unfortunately no, they haven't gotten back to me since before. I will poke them again on this.

> @dngray any updates? Unfortunately no, they haven't gotten back to me since before. I will poke them again on this.

👍 1

dngray commented

2020-08-23 06:14:42 +00:00

(Migrated from github.com)

Last I heard from them was on Mar 26, 20:34 CET 2020 when they said they were looking into it.

I contacted them again on 5th May 2020 and then finally on 15th Aug 2020 and got no reply.

Last I heard from them was on Mar 26, 20:34 CET 2020 when they said they were looking into it. I contacted them again on 5th May 2020 and then finally on 15th Aug 2020 and got no reply.

This repo is archived. You cannot comment on issues.