The USPS is also losing money at an unheard rate, even amongst VC backed startups in Sv - $60+ billion in the past 10 years.
403 karma · joined August 16, 2011
So founders, former employees, and earlier investors probably lost out...
Come help us build and scale Privacy.com! In less than a year since launching, we've moved millions of dollars and protected tens of thousands of users.
About us:
We’ve built a new way to transact without giving away your personally identifiable information (PII) or credit card number. We're a small team, generating significant revenue, and backed by top-tier investors. As one of our first full-time engineering hires, you’ll have the opportunity to make a impact on both the product and culture of the company.
Current technical challenges:
- Building out mobile/web features as fast as our growing customer base demands
- Improving our browser extension checkout detection and auto-fill accuracy towards 100%
- Applying learning algorithms towards towards detecting anomalous behavior and preventing fraud
- Updates to our real-time Visa transaction processing system where requests must be responded to in milliseconds
What we’re looking for:
- Ability to write clear, maintainable, thoughtfully commented code
- Proficiency with javascript preferred but not required (our stack is angular, node, react native, with some java / c++)
- Solid background in algorithms, systems, and design
- Can-do mentality, with the willingness to wear a sysadmin or devops hat when necessary
- 3+ years of real-world experience shipping code
If you're interested drop me a line: bo@privacy.com!
You're not wrong. But this comment completely lacks substance and doesn't even attempt to address the post.
I don't fully agree with Slava, but at least he makes some thoughtful points. You just typed out a handful of platitudes which sound like they came straight off a Startup Vitamins poster.
Come help us build and scale Privacy.com! In just a few months since launching, we've moved millions of dollars and protected tens of thousands of users.
About us:
We’ve built a new way to transact w/o giving away your personally identifiable information (PII) or credit card number. We're team of 5, generating revenue, and backed by top-tier investors. As one of our first full-time engineering hires, you’ll have the opportunity to make a significant impact on both the product and culture of the company.
Current technical challenges:
- Building out mobile/web features as fast as our growing customer base demands
- Improving our browser extension checkout detection and auto-fill accuracy towards 100%
- Applying learning algorithms towards towards detecting anomalous behavior and preventing fraud
- Updates to our real-time Visa transaction processing system where requests must be responded to in milliseconds
What we’re looking for:
- Ability to write clear, maintainable, thoughtfully commented code
- Proficiency with javascript preferred but not required (our stack is angular, node, react native, with some java / c++)
- Solid background in algorithms, systems, and design
- Can-do mentality, with the willingness to wear a sysadmin or devops hat when necessary
- 3+ years of real-world experience shipping code
If you're interested drop me a line: bo@privacy.com!
This is something we've been working to improve over the past few months. If this happens again can you shoot us a note support@privacy.com with the details?
Anyway, thanks for bringing it up. We've pushed the updated terms.
If we took routing / account numbers, you'd have to preload your account and wait up to 3 business days. It's something we're definitely looking into though as well though.
However, that doesn't mean what we're doing isn't meaningful. We just think that you just shouldn't have to share your personal info with a random merchant you want to buy something from.
This notion that passing along your billing info is going some how substantially cutting down on fraud is ridiculous. It's anti-privacy in the guise of being anti-fraud.
And yes, it's fair, if you skip out on a gym contract, you do risk getting taken to collections. We're mostly talking more about the ticky tack, deceptive recurring billing fraud. We can do better. We'll make the language clearer on our home page.
It's a long story, but there's probably a good blog post in this.
It's anti-privacy in the guise of being anti-fraud.
Yes, we do have to comply with subpoenas.
The numbers can be one-time use (burners) or re-usable at the same merchant.