Privacy-protection mutuality comparison
- or -
Post a project like this$600
- Posted:
- Proposals: 3
- Remote
- #2190445
- OPPORTUNITY
- Expired
Description
Experience Level: Expert
Estimated project duration: 3 - 4 weeks
I have an andriod application, which retrieves facebook chat of the user and process all the messages to calculate the similarity between two users. Some guy did a supreb job to develop this first version of my application and now I want an enhancements in it.
My application stores facebook credentials in the backend server and backend server is responsible for processing all the similarity comparisons. I want to secure the privacy of user at application level and backend should still remains the same as nothing should needs to be changed at backend. In simple words:
Currently: Goal
-Backend sees all comparison requests ====> 1. Backend shouldn't see comparison requests
-Personal texting data has to be submitted ====> 2. Only rough usage data has to be submitted
-Backend knows !! All pairwise similarities ====> 3. Backend shouldn't knows pairwise similarity
-Backend knows the base data for pairwise similaritiies ====> 4. Backend knows the base data for pairwise similaritiies
====> 5. Users shouldn't have to change comparison words
Interested people should come with an idea how to implement privcay protection at application level while keeping the backend implementation remains the same.
My application stores facebook credentials in the backend server and backend server is responsible for processing all the similarity comparisons. I want to secure the privacy of user at application level and backend should still remains the same as nothing should needs to be changed at backend. In simple words:
Currently: Goal
-Backend sees all comparison requests ====> 1. Backend shouldn't see comparison requests
-Personal texting data has to be submitted ====> 2. Only rough usage data has to be submitted
-Backend knows !! All pairwise similarities ====> 3. Backend shouldn't knows pairwise similarity
-Backend knows the base data for pairwise similaritiies ====> 4. Backend knows the base data for pairwise similaritiies
====> 5. Users shouldn't have to change comparison words
Interested people should come with an idea how to implement privcay protection at application level while keeping the backend implementation remains the same.
Ian W.
0% (0)Projects Completed
-
Freelancers worked with
-
Projects awarded
0%
Last project
26 Apr 2024
Pakistan
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies