Contact Us

To help us resolve your request quickly, include the email address connected to your account, the note URL (if relevant), and a short description of what happened. If you are reporting a technical issue, list the device and browser you used, plus the exact time you noticed the problem. These details reduce back-and-forth and allow our team to reproduce the issue faster.

For billing questions, mention the plan name, renewal date, and the transaction reference from your receipt if available. For account access requests, provide enough detail to verify ownership safely without sharing sensitive passwords. For product feedback, include the workflow you are trying to complete so we can evaluate improvements in the right context.

ProNotepad support can help with editor behavior, account and login problems, password-protected note settings, public sharing controls, and general product guidance. If your request depends on a specific note, send only the minimum information needed for diagnosis. Do not include private credentials or full sensitive data in your message.

We review each request in the order it is received and prioritize issues that block access, affect data availability, or create security risk. If your request is urgent, mark the impact clearly in the message body. This page is intended to provide a direct, structured way to reach the team so users can get accurate help without searching through multiple channels.

The support team regularly helps with account access recovery, password-protected note behavior, unexpected sharing permission changes, and billing questions tied to subscription updates. If your request involves one of these areas, include the exact workflow step where the issue started so we can diagnose root cause without additional clarification cycles.

For collaboration issues, mention whether the note is public, private, or protected and whether the issue occurs for all recipients or a specific user. This context helps us separate permission configuration problems from browser, session, or link-handling problems. When available, include timestamps and screenshots to speed reproducibility on our side.

If your request is feature-oriented, explain the job you are trying to complete instead of only describing the interface change you want. Understanding the underlying workflow gives the product team better evidence for prioritization and helps ensure future improvements solve the real operational problem rather than only a surface symptom.

When possible, include the expected outcome as well as what happened instead. Comparing expected versus actual behavior helps support classify issues quickly and recommend the most accurate fix path on the first response.