Digital × Design help centre

Start with a clear, useful answer.

These guides cover confirmed product behaviour and the details that make a support request easier to investigate.

Before you contact us

Include the evidence that matters.

For a technical issue, tell us the product version, device or browser, what you expected, what happened instead, and the shortest steps that reproduce it.

Please keep sensitive information out of requests. Never send passwords, API keys, payment details, or private documents. A screenshot is often enough; if diagnostics are needed, support will explain a safe way to share them.

Product guides

What we can confirm today.

If your situation is not covered, use the support form and choose “Something may be broken.” We will investigate rather than ask you to work around an unconfirmed problem.

ParkShelf

Window control and permissions

  • ParkShelf needs macOS window-control permission to move and manage other app windows. If it cannot act on a window, confirm that Accessibility access is enabled for ParkShelf.
  • If drag-to-park is the specific problem, include whether Input Monitoring is enabled as well as Accessibility.
  • Tell us whether you use one display or more than one. The available parking behaviour can differ on a single-display setup.
Get ParkShelf support →

aud-io

Music, purchases, and optional AI

  • Use Library ▸ Add Music to choose music you own from the Files picker. aud-io does not provide a streaming catalogue.
  • For a previous Pro purchase with the same Apple Account, use Restore Purchases in the app. Apple manages payments and refunds.
  • Never email an API key. Optional AI features should only be connected through the app’s settings.
Get aud-io support →

Cunei

Documents, beta testing, and files

  • For a document issue, include the file type, the action you took, whether the document came from a cloud provider, and whether the same file opens correctly elsewhere.
  • When testing a cloud-backed document, allow the provider download to complete before editing or saving. Report any stalled open, save, conflict, or missing-file state.
  • For formatting or Word-compatibility reports, attach a screenshot and describe the exact document feature involved rather than sending a private document.
Get Cunei support →

MacToiPhone, headphoneify & smartphoneify

Corrections, sources, and attribution

  • For an incorrect product image, model name, score, source link, or attribution, include the page URL and the specific issue.
  • For a review-link concern, include the publisher or original source that should be checked. Evidence and product identity take priority over a general disagreement.
  • Questions about privacy, advertising, affiliate links, or disclosure are welcome through the same route.
Report a guide-site issue →

Potential bugs

When it looks like a product bug.

Choose “Something may be broken” in the support form. We will first check whether it is a known limitation or configuration issue, then reproduce it. If it is confirmed, it is recorded against the relevant product and tracked through a fix or a clear status update.

Report a potential bug