Hacker News Reader

Comment by yodon | Hacker News Reader

How does GDPR, etc. factor into this?

It is the very foundation of what we are building. We started as a data privacy company. When you authenticate with Rownd, the Rownd hub (on every website screen that uses Rownd), shows all of the personal data that has been collected by that app/site and you can turn it off with a button click. You can also go to mydata.rownd.io and self opt out of ANY data on any app that Rownd partners with.

We fundamentally believe that the end-user should control their data, we turn it into a feature.

Thanks for the question!

So the user/visitor (browser?) has a single identity within Rownd and the data is aggregated across any Rownd partners… and then the user can request a magic link to finalize the verification step per partner site? Domain?

And that checks a box to say they’ve authenticated with just that site? If the user has already verified their identity on a different partner then what’s actually happening for subsequent partners?

How is the data siloed across partners?

Could be neat to back into a shared payment identity like bolt if the user opts to share that info. ie they’re on a new site that recognizes their Rownd profile and they can autofill/share certain info.

I really like the idea of a single source for privacy/GDPR control across all the sites I use. I hope y’all get great adoption.

Yes, once you've added information to one Rownd partner, it _can_ become available to a second partner, but _only_ if the user consents to sharing it and only when the fields/data types match between the two apps. Typically, that occurs during the sign-in process.

We currently require verification on each partner site to ensure that the person signing-in is actually the holder of the email/phone. In the future though, we plan to allow a user that's authenticated at one Rownd partner to click a single button on a second partner site to simply pass the existing verification and account info across. In that case, no email/sms is needed as long as its done in the same browser/device.

Thanks for the question and your support!

Is this essentially a "Sign in with Rownd"? Similar to how "Sign in with Google" works? albeit with some anonymous user-tracking helpers at the front.

Google is kind of like "email verification" brought forward since they own 65% of the email market and even more of the browser market.

We also "verify" and authenticate, but that is where we diverge. We also help websites manage "profiles" and "accounts" and that data can be made available for customization and personalization. From what a user sees to how they interact with a site or app.

Finally, we give the user the ability to retroactively "revoke consent" to their data. When they turn it off, the site and app no longer have access to it.

>Could be neat to back into a shared payment identity like bolt if the user opts to share that info. ie they’re on a new site that recognizes their Rownd profile and they can autofill/share certain info.

Great idea. How would you want that connection to look like as a user? I'd image we could "link bolt to your profile" on bolt enabled carts...

I was thinking more along the lines of sharing my payment credentials with Rownd then just enabling payment when I log into one of your partners.

The actual processing could be handled by y’all rather than passing raw cc info to each partner.

I realize that’s pretty far from your mvp but as a user I’d rather save all personal data with one data store which can enable access or usage to selectively to apps.

As a partner, I’d like also like to have one spot to save user data. And if you’re streamlining onboarding it makes sense for that to include payment info or payment ability.

My rownd profile also becomes an auditable source of all my infos access and usage :clap:

Some day!

>And that checks a box to say they’ve authenticated with just that site? If the user has already verified their identity on a different partner then what’s actually happening for subsequent partners?

As of right now, the authentication spans apps/websites owned by the same customer. If a user goes from one Rownd customer to another, they will have to re-authenticate and enter their data.

We are visioning a world where end-user can go from Rownd customer to Rownd customer and we can just ask "do you want to continue as Harrison and share x, y, z" so they can experience customizations and personalizations faster on sites. But we just launched and are examining that use-case!

How do you know all the data an app has collected? Seems like much of that could be in separate JS or 3rd parties

We allow the app/website developer to add html attributes to the form to send it to the Rownd hub if they choose. In the future, we will be a bit smarter to get it all, but right now it is more manual. Of course, if you don't want Rownd Hub to store it, it does not have to.

What about the data they collect outside of your app. The point is that you cannot say anything about that, but it sounds like you do, which is false advertising.

A simple example is analytics

Reply on news.ycombinator.com