I guess you could use the users own password to encrypt the data, but then you're pretty stuffed if they forget it. Ideas?
In their FAQ regarding if they have access to account information... "Yes. But with 100s of people using the app, it's really not interesting to run after your details."
I would expect that in a lot of application's it is possible to pull out client data one way or another. The way this is written makes it sound like client details are sitting on a desk and the only reason they aren't rooting through your details is because you aren't interesting enough.
Well.. what happens when you apparently offend the designer on HN and become of interest.
The answer should be technically yes but no. A developer could engineer access or pull data from a client database. However, breaches like this aside, there is no formal way to access your account or see your data.
I do not know how this makes the app worthless. Honestly? Designer doesn't know what goes behind it so app is worthless.
Data is not encrypted because shipping a MVP was the main goal till now. But it's on the list yes.
Follow up does not say sensitive data. Follow up says if you're data is so interesting that everyone is after it pelase don't share.
Edit:
PS: Dude when you edit your original comment. do mention you edited it. In the comment itself.
I said it is worrying that the app has got this far and you do not know more about it. Your post sounded like you know little about the technical side of the application. This might not be the case and if is I apologise. I feel if there is a start up with 2 people. Both should have a good idea of what the site is built on and what technology stack you are using. You don't need to be a developer to know this stuff.
I said your app is worthless because of your FAQ. You effectively say you have access to all data I put in and if I have any sensitive data don't bother. I feel my financial data is sensitive so why bother? This is the key question.
It is how you come across in your FAQ which greatly devalues your application.
I do not think both people SHOULD know the stack or whatever.
As far as data goes, yes you're right. We should work on that a bit more.
Edit: You edited your comment, you can mention in the comment itself that you edited it instead of calling me "wrong"
You could have shut me up instantly by saying. "The FAQ is poorly written. There is no formal way to access client data... blah blah"
Instead you have no response. It doesn't seem to bother you that you suggest you can access any clients personal data at the drop of a hat.
Regarding knowing what your site is built on. You don't seem to understand that you aren't a designer. You are a co-founder. At least I thought you were. If not disregard what follows. As a co-founder you should know what is going on in your company. You should know what your website's technology stack is, you should know about your costs, your pricing and your marketing strategy. It is in your interest. This isn't about programming. It is about business ownership and knowing what the hell is going on with your product.
If you approached an investor and you couldn't answer a few questions about the technology used in your site you would be sunk moments after setting your foot in the door.
If none of this bothers you then fine. My boss knows no programming but he knows how many servers the company uses, the OS on the servers. The database system. He knows current storage (%) total vs available. he watches the technologies we use for updates. Yet he know's nothing about programming or design for that matter. He is a sales person.
It is in his interest to know these things because his product is a website and he doesn't want to look like a dick in front of his clients or financial backer.
That would be "Designers living in vaccum."
You need to decide if you are a designer or a co-founder, and if you are owning the product or merely contributing to it. Because designers shouldn't be making public comments on product privacy policies.
He mentioned I should know the stack. Privacy policy was not mentioned. Nor did I say being a designer has anything to do with Privacy Policy.
I said, being a designer I do not understand what stack it is and that doesn't make the app worthless.
BUT...
What else do you call a financial application which hasn't set its cornerstone as data protection.
I saw this app and thought it looked nice, I could see myself using it. I then read a bit more about it in the FAQ and I cannot use it. My financial data may not send the world into an economic downturn but it is something I care about and what to keep safe. If this application cannot do that then I cannot put my financial details into it...
If this was sorted out the app would look very promising. Such an apparent disregard for data protection isn't acceptable for a financial app and in its current state looks like it shouldn't be used.
[ To give these messages context. This comment could have been construed to say something else. I said 'what makes your app worthless is this' after taking about how he describes a lack of technical info and before I talk about the FAQ.
I later updated this line to make it clearer. I should have added an edit note but didn't. I apologise. I just added the edit note and this blurb at the beginning to give the rest of the conversation context.
This is why there is discussion about lack of designer's tech knowledge devaluing an application. This was down to my poor writing. Wasn't my intent. I hope everything is clearer now.
I will no longer be using the edit button on HN ]
-- END OF EDIT --
This is worrying:
> My co-founder is offline will ask him to add more details on tech used side.
You have already got this far. Why do >> you << not know this already?
This text in your FAQ, for me, makes your application worthless. [Edited -- Original line could have been read as lack technical information devalued the application. This was not intended]
> Do you have access to my account information?
> Yes. But with 100s of people using the app, it's really not interesting to run after your details. If your financial data can make world economy crash, please do not use the app.
What you have said is this. "Yes we have full access to your account information." Then to follow it up you effectively say this. "We may snoop on your account so if you have sensitive info do not use this application."
Its really really bad. Data security should be the most important thing you do. Especially as your app is to do with people's finances. User data should be encrypted. I don't understand why you need to have access to individual clients data. Can you explain please.