Skip to content
D. Arts Creative Tech

Rungboard

Rungboard Support

hi fallback-source-locale

Use this page for public support information for Rungboard.

Start here

Use this page for public support information for Rungboard.

Contact

  • Product support: `support@dartscreative.com`
  • Privacy questions: `privacy@dartscreative.com`

Metadata

  • App: `Rungboard`
  • Locale: `en-US`
  • Purpose: canonical source Help front door for future localization
  • Status: `draft-source`
  • Source of truth owner: Portfolio Core
  • Last updated: 2026-04-21

1. Start here

Save one role first.

The app is designed to keep the next action attached to the role so your search stays visible, local, and calm instead of turning into a career-suite workflow.

2. Keep the next step attached

After you save a role, add the next follow-up, interview, or task that belongs to it.

If the next step matters, set the reminder at the same time instead of trusting memory.

3. Review the pipeline regularly

Use the pipeline view to see which roles are active, which are stalled, and which still need a follow-up.

Archive completed or paused roles when you want the active board to stay focused without losing the record.

4. Read reminders and export honestly

Reminders help you remember the next step. They do not turn the app into a recruiter tool, a job board, or an ATS integration.

Export is for your own records or spreadsheet fallback. It is not cloud backup and it does not imply employer-system sync.

5. Contact support when

Contact support if:

  • reminders do not match the next step you saved
  • archive, restore, or delete behavior feels unclear
  • export looks incomplete or misleading
  • the wording feels unnatural in your locale

Include:

  • the stage or action you were trying to track
  • whether reminders were allowed or denied
  • the locale you selected
  • what looked wrong
  • whether the issue was reminders, wording, archive/delete behavior, or export

Metadata

  • App: `Rungboard`
  • Locale: `en-US`
  • Purpose: canonical source FAQ for future localization
  • Status: `draft-source`
  • Source of truth owner: Portfolio Core
  • Last updated: 2026-04-21

1. What is Rungboard?

`Rungboard` is a calm, local-first job application tracker.

It helps you save roles, track stages, keep follow-ups attached to the right application, log interviews or tasks, and export your search history without turning the process into a career-suite subscription workflow.

2. Does Rungboard need an account?

No.

The current product posture is local-only. The app does not require sign-in, sync, or a backend to do the core job.

3. Where is my data stored?

The current build keeps roles, notes, reminder state, and related tracker data on the current device.

If that storage posture changes later, the support and privacy surfaces should say so explicitly.

4. Does Rungboard scrape job boards or write resumes for me?

No.

`Rungboard` is intentionally narrow. It is not a job board, AI resume writer, recruiter marketplace, coaching service, or employer ATS tool.

5. How do reminders work?

Reminders are tied to the next step you save for a role.

You can still track roles without notification permission, but reminder alerts require iPhone notification permission to be allowed.

6. What is the difference between archive and delete?

Archive hides a completed or paused role from the active list while keeping the local record available.

Delete removes the local record from the current device.

7. What does export mean?

Export means a CSV history export for your own records, handoff, or spreadsheet fallback.

It does not mean recruiter integration, ATS sync, or cloud backup.

8. What should I do if the wording, reminders, or export look wrong?

Use the Help front door first to confirm the intended product boundary.

If the issue still looks wrong, contact support and include:

  • the role or stage involved
  • the next step you expected
  • whether notification permission was allowed or denied
  • the locale you selected
  • what looked wrong
  • whether the issue was reminders, wording, archive/delete behavior, or export