Information for Authors

Note: This information applies to PoPETs 2023 and later.

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.

In general, submitted papers must be at most 12 pages, excluding bibliography and clearly-marked appendices, using this template (see LaTeX instructions for more information). However, PoPETs papers given a decision of Major Revision or Accept with Shepherding (aka Minor Revision) may revise their paper with 13 main-body pages, excluding bibliography and clearly-marked appendices. In either case, there is no page limit for references, acknowledgement, and clearly-marked appendices. PC members are not required to read the appendices, which should only be used to provide additional supporting information.

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. Papers that have previously been submitted to PoPETs must include a document summarizing the changes (see the guidelines for this document). 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.

LaTeX Template Instructions

As specified above, you must use this template.

• There is no need to fill in the values in the Copyright and Issue info sections of the .tex file for submission.
• Teaser figures are allowed, but definitely not required (we expect these to be exceedingly rare).
• Make sure you check the LaTeX output to see if it reports that you are missing packages. (Hint: You may be missing a package called texlive-fonts-extra or similar.)

Example conforming main.tex and submission-template.pdf files are included in the template zip file.

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.
• Remove references to your institution, for example in survey materials or in git repositories.
• 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.

Conflicts of Interest

Authors are asked to indicate conflicts of interest with PC members as part of the online submission process. We consider the following to be clear cases of a conflict:

1. Sharing an institutional affiliation with an author at the time of submission
2. The advisor or advisee of an author at any time in the past
3. A co-author of the author within the past two years or a current collaborator

For other forms of conflict, authors must contact the chairs and explain the perceived conflict. If the chairs do not receive a rationale for the conflict, they will remove this conflict when making reviewing assignments.

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.

Release of Code and Data (New for 2024)

To encourage reproducibility, this year PETS will ask the authors to indicate at the time of submission whether the authors plan to release code and data upon acceptance of the paper. If the authors respond no then they have to provide a brief explanation. A 'no' answer is not a ground for rejection as long as the authors provide a reasonable explanation. Note that this is distinct from the artifact review that takes place after a paper is accepted.

Claims of Benefits to Particular Populations

Authors should make clear whether their claims about benefits to a particular user population have been validated in some way (e.g. interviews, literature review, discussions with experts etc.). If authors can't offer such support or validation for their claims about that target community, this should be clearly acknowledged in a limitations section.

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.

Resubmission - Summary of Changes

A document summarizing changes is required for all resubmissions, regardless of the decision received. A resubmission is any paper with content substantially shared by a previous submission to PoPETs that received any reviews, and this includes a minor revision sent to a shepherd. There is no specific template for the summary of changes, and 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. The document must be a PDF.

Suggestions on what to include in your summary:

1. Include a paragraph or two summarizing 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 the concerns of the meta-review and how you have addressed them. Also, please point to the sections of the paper where the changes can be found.
3. Mention whether and how you have addressed the other issues raised in the individual reviews (and not included in the meta-review)
4. If there are points in the reviews (and especially the meta-review) that you disagree with, and thus have not addressed, make sure you make a convincing case providing your reasons.
5. Provide information on any other changes you have made to the paper (and not 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 heavy editing all over the place).

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

Copyright and Licensing

Copyright

Papers will be self-published on the PETS/PoPETs website under the Creative Commons Attribution 4.0 International license. Authors retain copyright of their work.

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 4.0 International license. One co-author needs to sign and send this on behalf of all of the authors.

Note: If some, but not all, of the authors are employees of the U.S. federal government, the form must be signed by one of the authors who is not an employee of the U.S. federal government.

Camera-ready Instructions for Accepted Papers

Author responsibilities

Authors are responsible for submitting a zip file that compiles correctly in our environment and follows all of the guidelines on this page. We strongly encourage you to use the Docker image we provide to test your source before submitting your camera-ready zip file. Instructions for using the Docker image are included in README.md in the image zip file. You can use the image on Linux and MacOS, and on Windows with Windows Subsystem for Linux (WSL).

Note that it is not sufficient for your source to compile in Overleaf, where errors are ignored!

Dealing with submissions that don't compile in our environment or that otherwise do not comply with the guidelines stated here slows down our publishing process and delays the entire issue.

Authors should watch for emails from the publication chairs following the camera-ready deadline and respond promptly. If you do not respond to the publication chairs, or if you fail to to provide an error-free zip file that follows the guidelines stated here on time your paper will be pushed to the next issue (or, if necessary, the next volume) of PoPETs.

What to submit for the camera-ready version

Email the following files to publication24@petsymposium.org:

An archive of your source (zip). This must contain all your source files so we can build your pdf. Our compiled version is the one that we will publish. We will insert the correct page numbers and DOI.

• Make sure that the correct fonts are embedded.
• Make sure that images, graphs, and figures have the correct fonts embedded.
• Make sure that there is no extra dot in any of your filenames (That is, instead of naming your file image.1.png, name it image_1.png.).
• Make sure the metadata.json is correctly completed, its correctness attested to, and included in the final .zip file.
• 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 agreement.
• Sign 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 the authors of the paper.

Funding Source Acknowledgements

All papers must include an acknowledgment 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.".

metadata.json

The data provided in this file creates the metadata used for indexing your paper. Note: The json file should be included in the final zip file you submit. Please do not submit it separately.

• The metadata.json file is in the camera-ready zip file.
• Make sure all the required information is provided, and is consistent with the accompanying source file.
• Make sure the abstract in the file does not contain any LaTeX commands or formatting.
• Make sure all the authors’ first names and last names are correct. The JSON file uses UTF-8 encoding to support Unicode characters. Please do not change the encoding.
• Attest to the correctness of the provided information. Put the following sentence in the "attestation" field if everything is correct.
  • I attest that the values in this file are correct and exactly match those in the accompanying pdf file.
• The file needs to be in the same directory as main.tex.

Artifact Submission

Authors of accepted papers will receive an invitation to submit a corresponding artifact. The deadline for artifact submission is about 3 weeks after the notification of paper acceptance. Artifact reviews are released about 3 weeks after submission. The anticipated finalization of artifacts is before the author notification date for the following issue.

See the artifacts page for more info.

Paper Formatting

You are strongly encouraged to use our Docker image to test your source. This will help you confirm that your source is free from compilation errors. You are also responsible for following all of the other guidelines on this page. More info

• Please use this LaTeX template.
• The page limit is 13 pages for the main body and unlimited additional pages for the references and appendices. Note that these page limits apply only to the camera-ready version, and they are an increase over the 12-page limit during submission. Acknowledgments may appear outside of the main-body pages (that is, they can be considered an appendix).
• We use TeX Live 2020/dev/Debian for compilation. If you are using Overleaf for your camera-ready, please make sure to set the Tex Live version to 2020 (Menu > Tex Live version > 2020 (Legacy)).
• Make sure that your main .tex file is named main.tex.
• Make sure that your main.tex file starts with \documentclass[sigconf,balance=false]{acmart}.
• Make sure that the following tags and macros are in main.tex (and not in an external .tex file.) Do not modify these tags.

  	\usepackage{popets}
  	% Copyright
  	\setcopyright{popets}
  	\copyrightyear{YYYY}
  	% Issue info
  	\acmYear{YYYY}
  	\acmVolume{YYYY}
  	\acmNumber{X}
  	\acmDOI{XXXXXXX.XXXXXXX}
  	\acmISBN{}
  	\acmConference{Proceedings on Privacy Enhancing Technologies}
  	\settopmatter{printacmref=false,printccs=false,printfolios=true}
  

• Do NOT use the \subtitle{} tag; indexing services will drop the subtitle.
• You do not need to provide values for the \city{}, \state{}, and \country{} commands within the \author{} commands, but YOU MUST leave the blank commands in the file.
• The CCS concept tags ( \begin{CCSXML}... ) should be omitted.
• Make sure to include an Acknowledgment section. The Acknowledgment section should be included using \begin{acks}...\end{acks}.
• Make sure all fonts are Type 1 or TrueType, and embedded and subset. (See PDF fonts for help).
• 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, figures, algorithms, and equations should be confined to double-column margins.
• Be consistent in capitalizing paper titles, section titles, subsection titles, and paragraph 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 your \title{}, \section{}, \subsection{}, etc. commands. Do note, however, that the template will render section (but not subsection) headings in full caps.
• Bad breaks: Fix any widows or orphans. (See https://en.wikipedia.org/wiki/Widows_and_orphans) Section and subsection headings should have at least 2 lines of text under them before spilling over to the next column.
• PoPETs does not provide editorial services. We recommend you thoroughly proofread your document and consider engaging your own copy editing service.

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 Adobe 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