\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Examining a Norwegian Client's Response over Information Security and Privacy Policy},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2015-01-15 (revised: 15 January 2015)}
\def\TheID{\makeatother }
\def\TheDate{2015-01-15}
\title{Examining a Norwegian Client's Response over Information Security and Privacy Policy}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Murtaza Hussain  Shaikh}

             \affil[1]{  Member IEEE, Oslo Norway}

\renewcommand\Authands{ and }

\date{\small \em Received: 8 December 2014 Accepted: 3 January 2015 Published: 15 January 2015}

\maketitle


\begin{abstract}
        


The core purpose of this article is to investigate how different a Norwegian subscriber?s point of view about the terminology of understandability, technicality, importance and awareness of privacy policy. Indeed this research article has its demographic limits and was targeted for Norwegian clients but it may suggest a first step to reshape policy for better realization. The emerging ambiguity in information security has raised much privacy and trust issues that are context dependent. Therefore there are several uncertainties and risks seen today concerning the privacy policy & subscriber trust. It is a responsibility of services providers before amending their policy to notify their subscribers. Since if they do not take this initiative then it creates trust deficit for their subscribers and this affects their business and goodwill. For this article we have adopted a survey questionnaire methodology based on clients? own perspectives. Generally observed that, before accepting privacy policy, it`s hard to read these policies and understood by common user, and taking this prospect ahead, many policies & regulations have a difficult context to recognize.

\end{abstract}


\keywords{privacy; personal information; service providers; subscriber`s policy; issues; legislation; practices; information security.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
ore than a century ago, Warren \& Brandeis have defined privacy as "the right to let alone" and their concern about privacy was quite prompted \hyperref[b0]{[1]} . The emerging ambiguity in information society has raised many privacy and trust issues that are context dependent. These issues will pose many challenges for policy-makers and stakeholders because people's notion of privacy and trust are different and shifting \hyperref[b1]{[2]} . Policies are considered as a fundamental factor to provide security and privacy in applications such as, file sharing, web browsing, web publishing, networking, and mobile computing. Such applications demand highly accurate policies to ensure that resources remain available to authorized access but not prone to compromise. The policies of the past are not suited to deal with new challenges and we are probably entering into new era that would require developing more effective policies. There are lots of uncertainties \& risks today concerning our privacy \& trust. It is also seen that people are sometimes compelled in circumstances to surrender their personal data to gain something \hyperref[b1]{[2]} . Two non-expert groups of policy authors are on the rise. First are the non-technical enterprise policy authors, typically Author: Member IEEE, Oslo Norway. e-mail: terminate1@hotmail.com lawyers or business executives, who have the responsibility to write policies governing an enterprise's handling of personal information \hyperref[b2]{[3]} . Second are endusers, such as that wish to set up their own spam filter, share photographs, videos or important files with friends but wants to protect them from un-authorize access \hyperref[b3]{[4]} . It is important to continue researching better mechanisms for security \& privacy policies authoring and to establishing good guidelines; because to achieve the best security goals it's crucial to obtain high quality to ensure the intended policy. This work shows the current role of privacy policy in policy management, but it is still immature in making security analysis and assessments [5]   . Furthermore with this research, the interest to make the organizations flexible with respect to privacy matters, consistent over the design of policy language that could be enforceable. 
\section[{II.}]{II.} 
\section[{Background Realities and Issues}]{Background Realities and Issues}\par
This section is laid down to get a good basis for specifying the ground of this area and creates a sense about the level of clients` concerns on privacy policy. 
\section[{a) What are privacy policy and security trust issues?}]{a) What are privacy policy and security trust issues?}\par
Privacy policies are meant to protect the privacy of the user: they need to reflect current regulations and possibly promises made to the customers. "A privacy policy is a legal document that discloses some or all of the ways a party gathers, uses, discloses and manages a customer's data. The exact contents of a privacy policy will depend upon the applicable law and may need to address the requirements of multiple countries or jurisdictions" \hyperref[b5]{[6]} . While there is no exact universal guidance or recommendations for the content or text of specific privacy policies, a number of organizations provide example forms, templates or online consultant for this purpose \hyperref[b5]{[6]} . Privacy policies arise further issues in comparison to access control policies, as they require a more sophisticated treatment of deny rules and conditions on context information; moreover privacy policy languages have to take into account the notion of "purpose", which is essential to privacy legislation \hyperref[b6]{[7]} . "A subset of privacy policies are enterprise privacy policies which furthermore have to provide support to more restrictive enterprise-internal practices and may need to handle customer preferences" \hyperref[b6]{[7]} . This means that an enterprise level privacy policies plays a vital role to increase the loyalty with the users. 
\section[{Year ( )}]{Year ( )}\par
H b) Is a policy context difficult with typical legal jargon? Many researchers of system security are asking the question; why do few people read the privacy policies \hyperref[b7]{[8]} . One common fact is simply that policies are often written in a hard and complicated language which a common user or subscriber cannot understand [8], \hyperref[b8]{[9]} . In privacy notice research conducted by \hyperref[b9]{[10]} the research is conducted in 2001 and in that research, 29 percent of the respondents expresses their feelings that policy contents are very difficult to read and 45 percent of respondents said that it was difficult to understand them. Another good reason subscribers have given for not understanding the policy is that they contain a lot of legal and lawful jargon \hyperref[b9]{[10]} . In the survey by Milne \hyperref[b10]{[11]} , about 53 percent of the respondents agreed, or strongly agreed to, that privacy notices often use legal language which is very hard to understand or is confusing for most people. Same as described in \hyperref[b11]{[12]} those policies use certain statement and distinct vocabularies which made them very hard to understand, even for the experienced reader. 
\section[{c) What is the standardization of policy context?}]{c) What is the standardization of policy context?}\par
Lack of standardization of privacy policy contents is also a problem. Different websites use different ways for structuring the information in their policies. Many service operators claim that their security statement first explains what particular information they are collecting and then how they will use those details \hyperref[b12]{[13]} . Other service operators tells where on the website they would collect personal information, and then explain what they will do to protect this information \hyperref[b12]{[13]} . Some service operators post on their website F.A.Q (Frequently Asked Questions) format focusing on answering the most common questions that mostly asked by the users regarding their privacy \hyperref[b12]{[13]} . There is no particular standardization adopted across the organizations / companies for comparison [12]. The ability to compare policies could be helpful in many situations (e.g. where users have a chance to select a company /organization to fulfil its requirements on privacy and security). 
\section[{d) What are the main privacy concerns?}]{d) What are the main privacy concerns?}\par
The privacy threats of which people are concerned include;\par
i. Visit to the websites will be tracked secretly without informing the user \hyperref[b15]{[16]} . ii. E-mail Id`s and other official information will be stored and used for marketing, publicity and other similar purpose without permission of the user [16]. iii. Personal information will be sold to third parties without getting permission from user \hyperref[b15]{[16]} . The advances of internet \& database technologies increase information privacy threats. Data entered into forms or contained in existing databases, can be combined almost effortlessly with banking transaction records, and records of a user's every click of a mouse on internet. Privacy concerns increase further as data mining tools and services become more widely available \hyperref[b16]{[17]} . There is a potential for fraudulent activities on the internet, as few regulatory standards exist \hyperref[b17]{[18]} . The security of banking card information for online purchase is also incorporated with the privacy concerns. Amazon.com admitted that hackers undetected over four months have stolen about 98,000 bank card numbers. Hackers from time to time publish a list of stolen card numbers and related information over the internet \hyperref[b17]{[18]} . The information without permission may lead to a fraud, which has very serious consequences \hyperref[b16]{[17]} . Although personal information may not be used after collecting them, it must be noticed that keeping information is a liability for a website when it meets some good consumers or some old users that take the safeguard of their privacy seriously. The Internet based businesses should take good care of the privacy concerns because the common consumer does not really care about going through every line of policy context. Surveys show that people are more comfortable if they see privacy statement has been approved by a third party, such as Trust-E  {\ref [19]}, \hyperref[b19]{[20]} . 
\section[{e) How client`s trust on security policies?}]{e) How client`s trust on security policies?}\par
Just like other studies have discussed on users` trust on privacy statements, a study conducted by \hyperref[b20]{[21]} also discovered that respondents were most willing to provide information with a strong privacy statement. Based on the responses for providing personal information, it appeared that many Internet users would be unwilling to provide personal information online, except when offered a strong policy statement. In this context, the importance of the privacy policy becomes apparent. It is the only way a website can communicate privacy issues with the users. The article \hyperref[b20]{[21]} concludes by showing strong concern for the low percentage of policy readers, given the impact that such statements would purportedly have on consumer trust. It has however been found that consumer trust relies on other aspects than the privacy policy. Studies have found that users tend to not read the whole privacy policy because they gained trust to the company through previous experience \hyperref[b21]{[22]} . Almost half of the respondents in the study by \hyperref[b10]{[11]} agreed or strongly agreed; when asked if they did not read the privacy policy because of pervious offline experience with a company and just 25 \% disagreed. Similarly in the same study 45\% agreed that they do not read the policy contents if it belongs to a well known organization or by a well repudiated service provider. In a 2000 survey, about 66\% responded that they got increased confidence in a site if a privacy policy was present [23]. In other words, by just seeing a privacy policy posted some users may believe that the sites they are visiting are safe in terms of privacy. They may also naively believe that "a security policy exposes a website to 
\section[{Global Journal of C omp uter S cience and T echnology}]{Global Journal of C omp uter S cience and T echnology}\par
Volume XV Issue I Version I Year ( ) H potential legal action; a website will always adhere to its policy" \hyperref[b22]{[23]} . These findings can be related to that some users believe policies are all the same, look like and have same context and that just by seeing it posted could make them believe its content is similar to other polices. 
\section[{III.}]{III.} 
\section[{Primary Privacy Principles}]{Primary Privacy Principles}\par
We will see that different approaches to regulate privacy protection has led to a global patchwork of privacy laws, regulations and enforcement mechanisms which vary greatly from state to state, region to region , adding complexity to the privacy landscape. Many of the laws and regulations enforced today do however have something in common which is that they are based on privacy principles and guidelines developed over past 40 years. a) Fairness and lawfulness: This principle implies that personal information should be handled fairly and lawfully. Behind this important principle is a requirement that the data controller should respect and take into consideration the data subject's interests and reasonable expectations. The data subject should not be forced to submit personal information or to accept that this information is used to other specific purposes \hyperref[b23]{[24]} . 
\section[{b) Limitations on collection:}]{b) Limitations on collection:}\par
The basic purpose of this principle is to limit the amount of data collected to what is necessary to carry out further processing of the data which corresponds with OECD's collection limitation principle. In \hyperref[b23]{[24]} the authors mention that there is not enough reason that the information is useful, the information must be necessary. The further processing of data should correspond with the purpose of which the data was collected for \hyperref[b23]{[24]} . c) Purpose binding: This principle means that personal information should be handled to a stated, legitimate purpose and should be handled to this purpose only. The purpose should be stated in a reasonable accurate way not later than at the time the information is collected, which complies with the purpose specification principle and the use limitation principle of OECD \hyperref[b23]{[24]} . d) Quality of the information: This principle is concerning the quality of the information. The information should be correct compared to what the information is supposed to represent \hyperref[b23]{[24]} . The information should also be relevant, adequate and complete based on the purpose of which the information is to be used, and to be up to date, which correspond with the data quality principle of OECD \hyperref[b23]{[24]} . e) The co-determination: This principle implies that the data subject should to a certain degree be able to participate and influence other`s processing of information concerning it \hyperref[b23]{[24]} . Persons can decide themselves if personal information about them is to be collected by others and for what purpose, unless the collection is done by the legal authority. This implies that persons can oppose to some types of processing of personal data, such as personal marketing etc \hyperref[b23]{[24]} .\par
f) Security safeguards: The confidentiality and integrity of personal data should be protected by reasonable security safeguards. Confidentiality here means protection of personal data from unauthorized access or disclosure, and protection of integrity means protection against unauthorized destruction, use and modification of personal data \hyperref[b23]{[24]} . g) Data sensitivity: Certain types of personal information are more sensitive for the data subject than other personal information. This is mostly information concerning the data subject's health, sexuality, race or ethnical background, political, religious or philosophical opinions, or memberships in certain type of organizations (e.g. Trade agreements, unions, joint business strategies etc). 
\section[{IV. Methodology and Evaluating Results}]{IV. Methodology and Evaluating Results}\par
We circulated a questionnaire to the peoples that are working \& living in Norway. This response was collected by sending 4 times reminder on different working days via email and messages to fill out the survey. Approximately, 81 percent incorporate their opinions about the privacy and security issues that have risen in this research. About 19 percent rejected or did not try to record their response.  Around 30\% of the respondents don`t read the context because they don`t understand them or has no time to read the policy before getting registered. Only 20\% of the respondents have voted that they read the contents of the privacy policy when they are registered as a new subscriber. The basic purpose of this question was to analyze how important a privacy policy for a subscriber, whenever they register and give their personal information to the service provider. In this question we have asked from our survey participants how difficult they feel when they read the policy content. By looking at fig 5, shockingly majority (46\%) of the total respondents are feeling problem in understanding the content of the privacy policy. 19\% of the respondents have informed us that they have not ever read \& understand the privacy context before using the services. Lastly, just 35\% of the respondents do not feel any difficulty in understanding the context of the privacy policy. 
\section[{Global Journal of C omp uter S cience and T echnology}]{Global Journal of C omp uter S cience and T echnology}\par
Volume XV Issue I Version I Year ( )  of the respondents agreed that they are not at all relevant from them. Around 30\% of the respondents says that policy contents are useful whenever they registered and relevant for them. Finally we can see that round about 28\% of the survey respondents has no any idea about the relevancy of these privacy policies from the subscriber point of view. We have asked from our participants to what extent they are confident enough to give their personal information to a service provider. We analyzed the results as shown in fig 7 that 81 percent of the respondents are not confident to give their personal information to the service provider and just 19\% of the respondents are confident to give their personal information to the service provider. Finally, we have asked from our participants that whether they are aware whenever their service operator amends the privacy policy on website or on any other platform of communication.\par
The results are given in fig  {\ref 8}. It was shocking that majority of the respondents (81\%) are not aware when there is any amendments performed by their service provider. According to our research survey just 19\% of the respondents are aware when there are any amendments from the service provider.\par
V. 
\section[{Limitations \& Trends}]{Limitations \& Trends}\par
As seen from our evaluations, future approaches to alternative ways of presenting privacy policy are quite limited. While the idea of a unified policy and regulation on the topic of privacy and is unlikely to ever happen. The development of data protection laws throughout the globe is promising, and could create a better foundation of taking the user into confidence, and creating innovative ways of presenting privacy policies in the future. There have, however, emerged several interesting topics regarding privacy policies through this online web survey, and especially the different aspects that defines user confidence in sharing online information seems fruitful to base future research on. Further analysis in modifying the version of privacy seals could also be interesting to investigate further. Being a self-regulatory approach, the idea of how this approach could effectively work in the context of defined legislation can be a positive aspect for further study. \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :H}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-6.png}
\caption{\label{fig_4}Figure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{7}\includegraphics[]{image-7.png}
\caption{\label{fig_5}Figure 7 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{6}\includegraphics[]{image-8.png}
\caption{\label{fig_6}GlobalFigure 6 :}\end{figure}
 			\footnote{© 2015 Global Journals Inc. (US) 1} 			\footnote{© 2015 Global Journals Inc. (US)} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Brodie et al. ()]{b4}\label{b4} 	 		‘A case study of developing privacy management tools’.  		 			C Brodie 		,  		 			C M Karat 		,  		 			J Karat 		,  		 			J Feng 		.  	 	 		\textit{SOUPS `05: proceeding of the 2005 .Symposium on usable privacy and security ACM},  				 (New York)  		2006.  	 	 (Usable Security and Privacy) 
\bibitem[Kelley et al. (2009)]{b14}\label{b14} 	 		‘A nutrition label for Privacy’.  		 			P G Kelley 		,  		 			J Bresee 		,  		 			L F Cranor 		,  		 			R Reeser 		.  		 \url{http://www.portal.acm.org/citation.cfm?doid=1572532}  	 	 		\textit{proceedings of the 5 th Symposium on usable privacy and security SOUPS},  				 (the 5 th Symposium on usable privacy and security SOUPS)  		2009. May 27 th , 2010. p. .  	 
\bibitem[Wikipedia The Free and Encyclopedia ()]{b5}\label{b5} 	 		‘Available online \& accessed on Spetember, 26th’.  		 			Wikipedia The Free 		,  		 			Encyclopedia 		.  		 \url{http://www.wikipedia.org}  	 	 		\textit{Privacy Policy}  		2010.  	 
\bibitem[Truste ()]{b19}\label{b19} 	 		\textit{Available online at},  		 			Truste 		.  		 \url{http://www.truste.org}  		2007.  	 
\bibitem[Bishop (2002)]{b15}\label{b15} 	 		\textit{Computer security: art and science},  		 			Matt Bishop 		.  		2002. December 12 th , 2002. USA: Addison-Wesley Professional Publication.  	 
\bibitem[Hancock (1997)]{b17}\label{b17} 	 		‘Cookies on your hard-drive’.  		 			W Hancock 		.  	 	 		\textit{American Agent \& Broker}  		1997. June 1997. 69  (6)  p. .  	 
\bibitem[Krauss (2000)]{b18}\label{b18} 	 		‘Don't kid yourselfconsumers do pay attention to privacy’.  		 			M Krauss 		.  	 	 		\textit{Marketing News}  		2000. February 28 th. 2000. 34  (5) .  	 
\bibitem[Anton et al. ()]{b11}\label{b11} 	 		\textit{Financial privacy policies and the need for Standardization},  		 			A Anton 		,  		 			J Earp 		,  		 			Q He 		,  		 			W Stufflebeam 		,  		 			D Blochini 		,  		 			C Jensen 		.  		2004. 2 p. .  	 	 (IEEE Security \& privacy) 
\bibitem[Bolchini et al. ()]{b12}\label{b12} 	 		‘I need it now ! Improving Websites usability by contextualization privacy policies’.  		 			D Bolchini 		,  		 			Q He 		,  		 			Anton A L Stufflebeam 		,  		 			W 		.  	 	 		\textit{ICWE},  				2004. p. .  	 
\bibitem[Interactive ()]{b9}\label{b9} 	 		 			Harris Interactive 		.  		 \url{http://identitytheft.lifetips.com/cat/65329/identity-theft-statistics/index.html}  		\textit{Identity Theft: New Survey \& Trend Report},  				2001.  	 
\bibitem[Lov om behandlig av personopplysninger The Norwegian Personal Data Act POL ()]{b25}\label{b25} 	 		‘Lov om behandlig av personopplysninger’.  		 LOV- 2000-04-14-31 Norway.  	 	 		\textit{The Norwegian Personal Data Act POL}  		2000.  	 
\bibitem[Cao and Iverson ()]{b3}\label{b3} 	 		‘Making access control usable for End-users’.  		 			X Cao 		,  		 			L : Iverson 		.  	 	 		\textit{Proceedings of the Second Symposium on Usable Privacy and Security (SOUPS 2006)},  				 (the Second Symposium on Usable Privacy and Security (SOUPS 2006)New York, NY; New York)  		2006. ACM Press. p. .  	 	 (Intentional access management) 
\bibitem[Simth et al. ()]{b7}\label{b7} 	 		‘Measuring individuals concerns about organization practice’.  		 			. H Simth 		,  		 			S Milberg 		,  		 			S ( Burke 		.  	 	 		\textit{MIS Quarterly}  		1996. 20  (2)  p. .  	 	 (Information privacy) 
\bibitem[Schartum and Bygrave ()]{b23}\label{b23} 	 		\textit{Personvern i informasjonssamfunnet. En innføring i vern av personopplysninger},  		 			D W Schartum 		,  		 			L A Bygrave 		.  		2004. Fagbokforlaget, Norway.  	 
\bibitem[Karat et al. ()]{b2}\label{b2} 	 		‘Privacy in information technology: Designing to enable privacy policy management in organizations’.  		 			J Karat 		,  		 			C.-M Karat 		,  		 			C Brodie 		,  		 			J ( Feng 		.  	 	 		\textit{International Journal of Human-Computer Studies}  		2011. 2011.  	 
\bibitem[Chung and Paynter ()]{b16}\label{b16} 	 		‘Privacy Issues on the Internet’.  		 			W Chung 		,  		 			Paynter 		.  	 	 		\textit{35 th Hawaii International Conference on System Sciences},  				 (USA)  		2002. 2002.  	 
\bibitem[Meinert et al. ()]{b20}\label{b20} 	 		‘privacy policy statements and consumer willingness to provide personal information’.  		 			D Meinert 		,  		 			D Peterson 		,  		 			J Criswell 		,  		 			M ( Crossland 		.  	 	 		\textit{Journal of Electronic Commerce in Organizations}  		2006. 4 p. .  	 
\bibitem[David ()]{b1}\label{b1} 	 		‘Privacy, trust and policy-making: Challenges \& Responses’.  		 			Serge W G David 		,  		 			Michael 		.  	 	 		\textit{Computer Law \& Security Review}  		2009. Elsevier Ltd Publication. p. .  	 
\bibitem[Piero et al. ()]{b6}\label{b6} 	 		\textit{Rulebased policy representations and reasoning},  		 			A Piero 		,  		 			L Juri 		,  		 			O Daniel 		,  		 			S Luigi 		.  		2007. Springer. USA.  	 
\bibitem[Milne and Culnan ()]{b21}\label{b21} 	 		‘Strategies for reducing online privacy risks. Why consumers read, online privacy notices’.  		 			G Milne 		,  		 			M Culnan 		.  	 	 		\textit{Journal of Interactive Marketing}  		2004. 18  (3) .  	 
\bibitem[Milne ()]{b10}\label{b10} 	 		‘The Culnan-Milne Survey on consumers \& online privacy notices: Summary of Responses’.  		 			M Milne 		.  	 	 		\textit{Interagency Public Workshop: Get Noticed: Effective Financial Privacy Notices},  				2001. p. .  	 
\bibitem[Eudpd ()]{b24}\label{b24} 	 		\textit{The EU directive on the protection of individuals with regard to the Processing of personal data and on the free movement of such data},  		 			Eudpd 		.  		1995. 95.  	 
\bibitem[Bonneau and Preibusch ()]{b13}\label{b13} 	 		\textit{The privacy jungle: On the market for data protection in social networks},  		 			J Bonneau 		,  		 			S Preibusch 		.  		2009.  	 	 (In the Eight Workshop on the Economics of Information Security (WEIS-2009) 
\bibitem[Warren and Brandeis]{b0}\label{b0} 	 		‘The Right to Privacy’.  		 			Samuel Warren 		,  		 			Louis D Brandeis 		.  	 	 		\textit{Harvard Law Review Association}  		IV  (5) .  	 
\bibitem[Wham ()]{b8}\label{b8} 	 		\textit{Transcript of the Federal Trade Commission USA Workshop on Information Privacy},  		 			Wham 		.  		 \url{http://www.ftc.gov/bcp/workshops/infomktplace/transcript.htm}  		2001.  	 	 (Measuring individuals Concerns about Organization Practices) 
\bibitem[Belanger et al. ()]{b22}\label{b22} 	 		‘Trustworthiness in electronic commerce. The role of privacy, security and site attributes’.  		 			F Belanger 		,  		 			J Hiller 		,  		 			Smith 		.  	 	 		\textit{The journal of strategic Information Systems}  		2002. 11  (3-4)  p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
