I’m an engineer on the Identity team. There are two somewhat separate questions here. (1) Whether the business should ever have access to this data. And (2) how exactly the business should access that data and the security properties around it.
On (1) this data is fundamentally the user’s, and there are often important compliance reasons as to why the user needs access to the raw data because of obligations that they themselves are subject to. It’s important to remember that you should trust both Stripe and the business that’s asking you to verify your identity. They are in control of explaining to you how they are using this data and giving you an option to opt out—or lose you as a customer.
On (2) we’re working on a way to restrict access via secret keys very soon.
How large percentage of Stripe
Identity customers do you foresee actually are required by legal regulation to retain all this information, as opposed to verifying certain aspects of an individual, as opposed to wanting it and likely handling it in ways violating GDPR and similar regulation?
I’d argue that before Stripe sends any PII other than validation results to a customer, it needs to verify that the business indeed is under regulatory requirements to gather this data, and only sell the required part.
Alternatively, you could invert the process, allowing integrating businesses to send documents to Stripe, who replies if they’re legit or not.
Finally, if there is a need for sharing data with customers for e.g. KYC, shouldn’t this be priced significantly higher than verification/validation, so that Discords and Clubhouses can’t justify it from a business perspective?
What is the reasoning for doing neither of the above?
Thanks! Yes, we were really inspired by how Figma has helped designers and their teams collaborate. In the same way that Figma has invited more non-designers into the design process, I feel Flux will invite more non-hardware people into the product development process.
Yep, exporting and importing from KiCAD and other software is critical for many workflows. We are continuing to add more import/export capabilities according to demand from our private beta users.
Databook | Web lead/Frontend/Fullstack | Palo Alto, CA | Full time | Onsite
Databook is looking for a full-time onsite front-end developer to join its growing team. Join us in our Palo Alto offices (California Avenue).
# About Databook
At Databook, we're committed to making financial insights available to all. We've taken our deep expertise of understanding how large companies make decisions and created a software platform that allows anyone to quickly get accurate insights on any public company.
We've built an engine capable of ingesting company filings, extract relevant information and feed it into a system capable of scoring, describing and visualizing performance as well as provide recommendations.
Our team is located in Palo Alto and London, with team members all over the globe in Uruguay, India, Canada and the UK.
Use your extensive knowledge of web technologies to improve the Databook webapp, a SPA that allows users to access and interact with the Databook platform. You will work with interactive charts, real-time data streams, REST and GraphQL APIs and other modern technologies. You will collaborate closely with the founding team to spec, build, test and deploy new features.
Use your knowledge of web technologies to improve the Databook webapp. You will work with interactive charts, real-time data streams, REST and GraphQL APIs and other modern technologies. You will collaborate closely with the founding team to spec, build, test and deploy new features.
BONUS POINTS
- UX and design sensibilities. We're looking for someone able to translate designs that might not be fully specced out.
- Experience with AngularJS, React, Vue.js or similar.
- Experience in small startup environments or similar work settings. You should be able to work in a fast paced environment. Requirements might change quickly so we're looking for someone that is adaptable and independent.
REQUIREMENTS
- US citizenship.
- 2-3 years experience developing complex web applications with modern technologies.
- Ability weigh several and often conflicting constraints to make rapid decisions in a fast-moving environment.
Please kindly apply by emailing inigo@trydatabook.com
