analogj / justvanish Goto Github PK

Tell databrokers to F#@% Off. Your data is your data, they shouldn't be monetizing your personal information without your knowledge.

License: MIT License

Go 100.00%

justvanish's Introduction

Hi there 👋

I'm a Devops/Automation guy, focused on building tools that help you automate & manage your servers. If you use letsencrypt/certbot you've probably used lexicon (which they depend on), a tool & library that lets you interact with DNS providers in a standardized way. Scrutiny is a Hard Drive health dashboard & monitoring solution, merging manufacturer provided S.M.A.R.T metrics with real-world failure rates. You can check my Pinned repos below for other popular projects I've built.

I'm currrently working on a project called Fasten Health - it's an open-source, self-hosted, personal/family electronic medical record aggregator, designed to integrate with 10,000's of insurances/hospitals/clinics

To ensure Fasten's long-term sustainability, we're exploring some funding options. While we're still deciding a long-term monetization strategy, I'm kicking off with a crowdfunding/fundraising experiment for the first 500 users (including a surprise desktop app):

Fasten Self-Hosted Lifetime License - $200

Got questions or want to learn more about our fundraising experiment? Click here to dive into the details & FAQs

justvanish's People

Contributors

Stargazers

Watchers

Forkers

sduibek

justvanish's Issues

DeleteMeNow, Reputation, and Removaly don't exist any more.

#10

Print a summary after send

The summary should include information about which databrokers we skipped, which were sent, and which failed.
Also useful for continuing failed sends: #8

embed organization unique UUID or "request id" in email subject and body

embed organization unique UUID or "request id" in email subject and body, which can be used when communicating with each data-broker.
This makes it easier to track responses from brokers

they can delete this or respond with a complete new email thread (no tracking associated with it).

https://stackoverflow.com/questions/23007197/how-to-cause-sent-emails-to-appear-threaded-in-gmail-recipients-view-with-messa

add retry/continue functionality

Gmail only allows a user to send ~500emails a day. We should detect SMTP send failures and stop. Then we should allow the user to continue where they left off (probably the next day)

how to (easily) track data-broker violations?

The new scenario looks like the following:

user runs justvanish, generating & sending 100s of emails
over the next ~40-60 days they get email responses intermittently from various data-brokers.
- some will be immediate approvals/responses with data
- some will be alternative instructions (use a website, phone number, different email address etc)
- some will be requests for more information
- some will be denials (with or without cause)
- some will not respond at all
for the "non-happy path", it'll be difficult for users to keep track of with organizations are ignoring them
- users have the ability to notify the govt agencies that a violation has occurred, but given how many emails they just sent out, it may be difficult to determine which organization is doing so

Possible solutions?

PRIVACY NIGHTMARE - something that parses your email, and watches for responses
PRIVACY NIGHTMARE - service that you can forward email to (like [email protected]) that parses your email and generates a table of known statuses.
PRIVACY NIGHTMARE - the paid options (DeleteMe, etc) use a unique email address when communicating with each data broker, ensuring that its easier to differentiate responses. Issue is that the law allows data-brokers to say they do not accept requests from third parties
embed organization unique UUID or "request id" in email subject and body, which can be used when communicating with each data-broker. (see #6)

nothing good here....