jump-ship-privacy

Thank you for switching over to Pastebin.

So yes, that's completely understandable; you're basically relying on the personal integrity of the person running the service.

I will use "I" and "we" almost interchangeably here; when I use "I", I mean me, myself. When I use "we" or "our," I'm talking about the Jump Ship company (including myself).

We care about user's privacy; it's one of the core reasons our service exists, helping you move from an online platform to an offline solution where you own your own data.

We have our privacy policy here that we're always improving: https://docs.jumpship.net/privacy_policy/ This was also included in your PayPal invoice.

In terms of other people having concerns, I think people have different thresholds for trust; you can review our forum thread as I'll usually ask for a testimonial after generation. I think what happens is that users try it out with a few notes of their own, they learn my character, and then they go through with their whole workspace—that is obviously not something that can scale.

We do want to eventually go into more of the technical details about how we keep users' data secure, that's clearly something we will need to introduce soon.

I think you more than anyone would understand that the reason we can't open-source or go local-only is because it destroys our business model. Staying online has its advantages though, in that it means you're not having to take up resources on a computer. We are device-blind, you could generate on your Apple Watch if you were so inclined; you can start generating on one device and come back to another device to download the workspace. You're not having to leave your computer running overnight, potentially over multiple days.

As per our privacy policy:
1. Attached to your account, we store access tokens and other information relevant to accessing and reading your Notion workspace.
1b. This information is used only by our service when retrieving your workspace for generation.
3. Generated Notion Workspaces are stored in a secure server.
3b. We do not review a user's generated workspace without express permission from the user.

To expand on 3a, if you click the "remove from list" button, everything from our servers about your workspace is deleted: access keys, generated files, etc. It's as if that workspace was never there in the first place.

Admins can spoof a user's screen, though the download button is disabled; you are unable to download the workspace if you are not the user. There's encoding on the values in the database, as well as file names stored on our S3 server, which makes it a little more convoluted to read the data unless you have the private key and the necessary decoding algorithm.

The point of this all is to avoid accidental breaches of user privacy.

We do have errors. This usually gives no information, and if any information does come through it's only for the specific block that errored, and only because I'm specifically logging that information in the code in order to debug it. Users also get a basic understanding of the block that errored there, as well as the error message.

I'm eventually planning to make it so the user has to report the error before you are able to read that error, though that seems like it would slow down development during beta testing, plus we would run into the same problem where a malicious actor could just decode and read the error anyway. Errors are also rare these days, we've been in development for a while and have become more and more stable.

I've been very conscious about the whole privacy aspect of the service throughout development, though we definitely need to improve the communication of how that works in practice. It's also an area where there is always room for improvement. This is something we need to be more transparent about, and something I'm planning on creating an entire section on in our documentation website.

If there is anything in our privacy policy that you feel could be worded better, or any privacy aspects you feel we could improve upon, we would love your feedback on this. You can review this here: https://docs.jumpship.net/privacy_policy/