Hacker News Reader

Comment by deadbabe | Hacker News Reader

Digging deeper, it seems like the user just did it themselves. Didn’t properly verify their account. That’s the end. What do you expect?

View on HN

For a customer, who paid 10 years, I'd expect a long enough grace period to allow customer to verify the account, while data would stay intact.

During early AWS days, customers who didnt want to sign up with a CC (usually because a corp policy) would quit registration at the CC confirm, and then contact AWS CS directly for bypass effectively not completing registration and still having an account.

Just knowledge, do what you will.

You can be a 10 year customer and one day a company decides they no longer want your business. I don’t see why people think being a long term customer entitles them to anything.

> July 10: AWS sends verification request. 5-day deadline (including weekend).

> July 14: Form expired. I contact support. Simple question: “What do you need from me?”

> July 16-20: Four days of silence. Then: “We’re escalating to the appropriate > team.”

> July 20: New form finally arrives.

> July 21: I submit ID and utility bill (clear PDF). Response time: 10 hours.

> July 22: AWS: “Document unreadable.” The same PDF my bank accepts without question. > July 23: Account terminated. My birthday gift from AWS.

If I understand the timeline, how were they going to verify themselves properly?

July 10: Fill out the form.

July 14th, at first glance falls within the stated 5 day deadline.

Depending on the user’s time zone, it could already be July 15th somewhere (where the form is hosted) when the user is still in July 14th.

I'd expect them to abide by their stated policy.

"The post-closure period is 90 days—during this time, an account can be reopened and data is retained."

Reply on news.ycombinator.com