548 karma · joined April 30, 2018
1. How can we identify if the user is based in Florida? 2. How can we determine their age? 3. How can we map the parent-child relationship here? 4. What will happen if the account was created in Argentina during traveling?
About two years ago, I was testing out the concept of the CRM build on top of Snowflake or any other DWH as a backend [0]. I can implement the core functions using existing drag-and-drop modular components, visualization elements, forecasting, alerting, etc. For basic CRM entities (contacts, deals, companies), tables are created in Snowflake via Unistore. CRM may maintain a separate database of their data containing application state, user permissions, and other metadata. Still, increasingly, the core data used to course through a system of record will be pushed/copied to the DWH.
For a data scientist to make forecasts, there is no need to upload data to the notebook; you can take Streamlit and build the necessary experience within the application. Any alerting logic can be described declaratively. An application or workflow can be created depending on its interaction with the product. The customization limits are almost limitless.
I love you're working in that direction. Reach me if you want to chat more – kidrulit at Twitter
[0] https://nonamevc.substack.com/p/how-snowflake-changes-the-wa...
I've been involved in the development of B2B SaaS solutions, and there are a few providers, such as ZoomInfo, Apollo, and Clearbit, that greatly assist the sales team in gaining a deeper understanding of customers. It seems that venture capitalists love those businesses.
Has anyone attempted to create similar companies that offer Data as a Service?
So it's kinda like a "first-world" toy for now.
[0] https://medium.com/@oseraryo/latest-updadats-japans-digital-...
How. that's related to developing an AI startup?
I wouldn't say fintech or neobanks are very trustworthy. Wise, a fintech platform, blocked my company's account for four weeks for "further investigation" right after the war as well. This caused me to miss bill payments.
I think the only way to mitigate the risk of a bank taking over your funds is to not store all your money in one account. Now, I have over 20 different accounts.
Come to Cyprus one day, you will get a flavor of undergrad tech of all kinds – gambling, adult tech, betting, etc. All these guys are legally operating in the dark mode and sitting on a ton cash of money without VC support.
I'd love to hear some legal or DPA opinion on this. From what I know, per the ePrivacy Directive in the version from 2009, any access or storage to information on the end user's device needs consent unless that access/storage is strictly necessary for a service explicitly requested by the user. This is known as the “cookie law”, but is not technology-specific and will also apply to equivalent client-side approaches such as LocalStorage, tracking IDs in URLs, or fingerprinting. The consent requirement is also independent of the question of whether the stored information qualifies as personal data.
The GDPR didn't change anything with these rules. It only changed the definition of consent, invalidating “implied consent” approaches like “by continuing to use this site, you consent to …”. Consent means opt-in. Consent must be easy to decline and withdraw, and users must understand what precisely they are consenting to. This has led to a decrease in the percentage of people who consent to the storage of analytics IDs.
So the question is whether we can be considered as a strictly necessary for a service
The GDPR mandates that the entire data processing cycle maintain a high standard of data protection. This implies that personal data transfers to non-European nations are allowed only if they ensure an adequate level of data protection. Otherwise, contractual agreements (SCCs) between data exporters and importers may translate GDPR's provisions into an enforceable agreement with the foreign importer, ensuring their processing aligns with GDPR.
The US had an adequacy decision termed "Privacy Shield," which was revoked due to concerns surrounding the rule of law vis-a-vis US mass surveillance laws. Due to similar reasons, contracts with US-based data importers may also be invalid. Additionally, using EU-based services from US-controlled companies is increasingly becoming worrisome.
Beam's approach relies on a weaker variant, which leverages a hash function to derive a pseudo-random ID from user-identifying information, such as the IP address. Although Beam's technique circumvents the need for a large lookup table, an unscrupulous server operator could log the daily key and use it to recover the original data from hashed IDs.
The flaw in this approach is that it still hinges on identifying data. While it serves as a good compliance and security measure, it doesn't alter anything significant from GDPR's standpoint. The same applies to competitive solutions like Plausible or Fathom.
Disclaimer: Consult with your legal; I am just a product guy. Explored the field to do a similar product a while ago.