Information for Authors

Quick Links

Useful Files
Submission Guidelines
Resubmission - Summary of Changes
Copyright and Licensing
Camera Ready Instructions

Useful Files

Sciendo (LaTeX template)
License Agreement

Submission Guidelines

Papers not following these instructions risk being rejected without consideration of their merits!

All papers must be submitted using the submission server! See the current CFP for the correct link for the current volume and issue.

Submitted papers must be at most 15 pages excluding bibliography and appendices and 20 pages total in Sciendo format (LaTeX template). PC members are not required to read the appendices, which should only be used to provide additional supporting information. Additional pages in the appendices may be allowed in some cases (for example, long security proofs, or long user questionnaires). Authors should contact the chairs in advance to request an exception to the page limit, justifying the need for additional pages.

Unlike journals that publish extended versions of conference papers, PoPETs seeks to publish original, previously unpublished work. Submitted papers must not substantially overlap with papers that have been published or that are simultaneously submitted to a journal or a conference with proceedings. The paper should start with the title and an abstract. The introduction should give some background and summarize the contributions of the paper at a level appropriate for a non-specialist reader.

Anonymization of Submissions
All submitted papers will be judged based on their quality and relevance through double-blind reviewing, where the identities of the authors are withheld from the reviewers. As an author, you are required to make a good-faith effort to preserve the anonymity of your submission, while at the same time allowing the reader to fully grasp the context of related past work, including your own. It is recognized that, at times, information regarding the identities of authors may become public outside the submission process (e.g., if a pre-print is published as a technical report or on a pre-print server) – the PC will ignore this external information. Minimally, please take the following steps when preparing your submission:

• Remove the names and affiliations of authors from the title page.
• Remove acknowledgment of identifying names and funding sources.
• Use care in referring to related work, particularly your own. Do not omit references to provide anonymity, as this leaves the reviewer unable to grasp the context. Instead, reference your past work in the third person, just as you would any other piece of related work by another author.

Ethics
Papers should follow the basic principles of ethical research. These principles include, but are not limited to, beneficence (maximizing the benefits to an individual or to society while minimizing harm to the individual), minimal risk (appropriateness of the risk versus benefit ratio), informed consent, respect for privacy, and limited deception. Consider especially the ethical implications of research involving human subjects, user data (e.g. network traffic, passwords, and social network data), and system vulnerabilities (e.g. cryptographic weaknesses, software exploits, and privacy attacks). See the Menlo Report for detailed guidelines on ethical research.

Authors are encouraged to include a subsection on Ethical Principles, and such a discussion may be required if deemed necessary during the review process. This section should include a justification of the ethics of the work and information about whether the work was submitted to an external ethics panel such as an IRB or the Tor Research Safety Board. Research that is deemed to not have met adequate ethical standards may be rejected on those grounds. Authors are encouraged to contact PC chairs before submitting to clarify any doubts.

Security Proofs
Some papers require lengthy security proofs to support the technical validity of the contribution. These papers should indicate this in the body of the paper and include the proof in the appendix. The acceptance or rejection notification for these papers may be delayed to allow for the proof to be reviewed, meaning that the paper may appear in the issue following the one to which it was submitted. A paper submitted to the February deadline may or may not be reviewed in time for the paper to be presented at that year’s symposium. If this occurs the paper will be published in Issue 1 of the following year and presented at that year’s symposium.

Resubmission - Summary of Changes

There is no specific template for the summary of changes, so you should feel free to draft it in a way that presents your revisions and responses to review points in a clear and concise manner.

Suggestions on what to include in your summary:

1. Include a paragraph or two summarising the main changes you have made in the revision and how they address the main concerns raised by the reviewers.
2. Respond point by point to the issues mentioned in the meta-review. Be clear and explicit in explaining what concern(s) the reviewer(s) raised in the meta-review, and how you have addressed them. Also, please point to the section(s) of the paper where the changes can be found.
3. Mention whether/how you have addressed the other issues raised in the individual reviews (not included in the meta-review.)
4. If there are points in the reviews you disagree with, and have thus not addressed, make sure you make a convincing case providing your reasons.
5. Provide info on other changes you might have made to the paper (not necessarily raised in the reviews).
6. Refrain from listing very minor changes (e.g., typos), it’s assumed that you have corrected them.
7. You can also attach a latex diff, if that helps understanding how you have updated your paper (though this is not useful if you have done very heaving editing all over the place.)

You are advised to put some effort in drafting a summary that makes it easy for reviewers to understand how the new version compares to the old one, and how you have addressed their comments and improved the paper. Expect reviewers to read your summary of changes before they read the new version of the paper, so you should see it as an opportunity to present the improvements you’ve made during the revision of the paper.

Copyright and Licensing

Copyright
Accepted papers will be published as an open access journal by Sciendo, part of De Gruyter, which has over 260 years of publishing history. Authors retain copyright of their work. Papers will be published under an open access policy using a Creative Commons Attribution-NonCommercial-NoDerivs license.

License Agreement
Authors of accepted papers must sign the license agreement. This allows us to distribute your work under the terms of the Creative Commons Attribution-NonCommercial-NoDerivs license, and grants Sciendo exclusive commercial use of the article. (This allows Sciendo to sell subscriptions to the journal.) One co-author needs to send this on behalf of all of the authors.

Note: The Journal Owner in the license agreement is listed as The Tor Project, Inc. This is because PoPETs is not currently a legal entity and The Tor Project, Inc. has agreed to enter into this agreement on behalf of PoPETs. The Tor Project, Inc. does not exercise any editorial control over PoPETs or PETs.

For US government employees: If one or more of the authors is a US federal government employee, you can sign the license as it is, because of the note “for U.S. government employees: to the extent transferable” in Clause 1.

For UK government employees and employees of other Commonwealth country governments: Each author that is an employee of a government agency must sign a copy of the license, along with an authorized representative of the government agency. If the agency does not sign the license, UK government employees should submit a signed declaration form. The paper should include an acknowledgement of Crown copyright of the form: © Crown copyright YYYY.

Camera-ready Instructions for Accepted Papers

What to submit for the camera-ready version

Email the following files to publication19@petsymposium.org:

• An archive of your source (zip, tar, etc). This must contain all of your source files so that we can build your pdf.
  • Our compiled version is the one that we will publish.
  • We will insert the correct page numbers.
  • Ensure that the correct fonts are embedded.
  • Ensure that an images, graphs, and figures have the correct fonts embedded.
  • Prefix the file name with paperXX-YYYY-Z-source, where XX is your paper ID, YYYY is the year, and Z is the issue number.
• A completed and signed license agreement (details here).
• Read and print the license agreement.
• Initial page 1, sign page 2, and scan the document.
• Prefix the file name with paperXX-YYYY-Z-license, where XX is your paper ID, YYYY is the year, and Z is the issue number.
• One co-author must sign this agreement on behalf of all authors of the paper.

Funding Source Acknowledgements

All papers must include an acknowledgement section that lists, for all authors, the names of the bodies that funded the research. If no funding supported the research, the section should include the sentence "This research received no specific grant from any funding agency in the public, commercial, or not-for-profit sectors.".

Paper Formatting

Help with fonts

• Please use the following LaTeX template: https://www.petsymposium.org/files/popets.zip
• The page limit is 16 pages for the main body and up to 5 additional pages for the references and appendices. The total page limit is thus 21 pages (16 + 5 = 21 pages).
• Make sure that your main .tex file is named "main.tex".
• Make sure that the following tags are in main.tex (and not in an external .tex file.) Do not modify these tags.

  	\journalname{Proceedings on Privacy Enhancing Technologies}
  	\DOI{Editor to enter DOI}
  	\startpage{1}
   	\received{..}
  	\revised{..}
  	\accepted{..}
  
  	\journalyear{..}
  	\journalvolume{..}
  	\journalissue{..}
  	

• Do NOT use the \subtitle{} tag; indexing services will drop the subtitle.
• Do NOT remove the \huge format in the \title{} tag.
• Make sure all fonts are Type 1 or TrueType, and embedded and subset. (Help with fonts).
• Be sure to use the fonts included in the LaTeX template. Do NOT import packages (such as "times") that may change the fonts.
• Avoid margin overflows: text and figures should be confined to the double column margins.
• Be consistent in how you capitalize titles and section titles. Either always use sentence case or always use title case:
• Sentence case: This is a section title about the European Union and GPUs
• Title case: This Is a Section Title About the European Union and GPUs
• DO NOT USE ALL CAPS for titles and section titles.
• Bad breaks: Fix any widows or orphans. (See http://en.wikipedia.org/wiki/Widows_and_orphans) Subsection/Section headings should have at least 2 lines of text under them before spilling over to the next column.
• PoPETs does not provide any editorial services. We recommend you thoroughly proofread your document and consider engaging your own copy editing service.

Help with fonts

PDF fonts

• Make sure that all of the pdf fonts are TrueType or Type1 and that they are all Embedded and Subset. You can confirm this using one of the following methods:
• Open your pdf in Abobe Reader and go to File > Properties > Fonts and check the listed fonts.

  

• With xpdf installed, run the following command: pdffonts your_pdf_filename

  

Embedding fonts in figures and graphs
The following script embeds and subsets fonts for figures and graphs. (We provided as-is, without support or warranty.)

Create a script called "embedfont" with the following contents:

# Usage: ./embedfont file.pdf
# Outputs file.pdf_embed. Make sure it looks good before overwriting original file.pdf
#
gs -sDEVICE=pdfwrite -q -dBATCH -dNOPAUSE -dSAFER -dPDFX \
-dPDFSETTINGS=/prepress -sOutputFile=$1_embed -f $1 \
-c quit

Error: variable ngerman
When using the template "dgruyter_NEW.sty", you may get an error: variable ngerman wasn't defined To solve this issue, install "lineno.sty" and comment out the lines related to that in dgruyter_NEW.sty