GDPR Policy

GDPR stands for General Data Protection Regulation. A new law enforced by EU to protect end user's personal data. This law enforces several aspects of data security.

Here we want to give a guideline how we protect your data, what is our responsibility and what is your responsibility. We strongly suggest you read all our documentation or other articles about GDPR and take the decision whether you want to use our application or not.

We are not responsible for any negligence or fault on data protection on your side or any third party side. Take your time to read documentation and act wisely, stay safe.

Any data owned by an individual is his or her personal data. It could be someone's name, image, email address, physical address, social media post, location, computer IP address etc. The ownership of user's personal data is absolute. That means wherever and however the data is saved it belongs to the user solely.

The data collector or data user (Facebook, YouTube) cannot show, save, share or perform any other activity with user's personal data without user's explicit or implicit permission. If an user gives permission to use his or her data on a specific type of action (data storing, data viewing etc.) then it can be used by the admin of the application.

To visualize this consider a hypothetical situation. You post a status on social media. Here you have given the implicit permission to show the post to your public or private contacts. Application admin is not responsible for any abusive comment to your post made by your contacts. This means that if you made your data public then it is your responsibility. But application admin does hold responsible for any data sharing with third party. If any data is shared it must be said explicitly in advance.

So we see how data uploading and showing depends on both app admin and user. Further details you will get upon reading the full documentation.

The safeguard of user personal data on application back end is the responsibility of developer. Developer is responsible for how the user data (name, telephone no. email etc.) and other info (like logs of user interaction with application) is stored on database and server.

We will describe in detail how the data you submit directly (name, email etc.) and indirectly (browser name, computer IP etc.) are saved on database and server. Once any data uploaded to server the security of data depends on security of server and sometimes the admin of application.

User will be notified about all the temporary (cookie and session) and permanent (data saved to database) data saving. User will get the option of all his or her personal data erasing permanently upon account deletion or service cancellation. We assure you that we do not keep logs of user activity and any other backdoor to extract user data.

Sometimes cPanel access and other credentials of app admin are needed by the developer to support and maintain the application for a short time before the application goes full online. We strongly recommend to app admin to change these credentials after the job gets done. Developer cannot be held responsible for any credential leak on this ground. Developer also cannot be held responsible for any unwilling security glitch on the application. After all, data shared online always has the risk of getting leaked. So we strongly suggest not to share any data that can compromise you or any other individual.

Application Admin has unrestricted access to the user personal data. Admin can access the database, server logs and any other info on admin's reach. Application admin can see and copy the data saved on database and server. App admin can share user's personal data to third parties.

How the user's data is used must be announced by the app admin explicitly before user registration. The admin should not allow anyone to extract data openly or under disguise of survey, fill the form or any other means.

The app admin enjoys most privilege on application. So admin has the highest responsibility of safekeeping of user's personal data.

It all depends on user. If user does not submit data then there will be no data breach. But this is not an option. The top most priority of user is to read all the documentation from both app developer and app admin then submit the data.

Safe keeping of user's own credentials is sole responsibility of user. Password and username may be encrypted on database but a dictionary word or too predictable password for a specific user can give easy access to user's account to hacker.

Change your credentials on any suspicious activity by unauthorized person or in case of you sharing your credentials to others for some inevitable reason. Always think before submit.