Jack of all (it-)trades

Sebas Visser

Tech Professional
Data Engineer | Full Stack Developer | iOS App Developer | Educational Scientist
Currently: Manager Data Team

Connect via LinkedIn, explore code on GitHub, download apps from App Store.

No data collected.

To summarize in 1 sentence: none of your data is collected, not now, not tomorrow, never.
But appearantly these days we need more sentences to describe these things..so below you can find the full privacy policy.

Last Updated: January 2, 2026This Privacy Policy applies to all iOS applications developed and published by Sebas Visser, including:- WhatsThatGift - Gift tracking and scanning
- DailyRewind - Daily reflection and journaling
- BabyTimeTable - Baby schedule tracking
- FOODiary - Food and meal tracking
- ADHDiary - ADHD-focused journalingThis policy also applies to any future applications published by Sebas Visser.---## The Short VersionI do not collect any of your data. Period.Your data stays on your devices and in your personal iCloud account. I have no servers, no analytics, no tracking, and no way to access your information. I will never collect your data—not now, not in the future, never.---## 1. Data CollectionI collect nothing.My apps do not collect, transmit, or store any of your personal information on external servers. I do not use:- Analytics services
- Crash reporting tools
- Advertising networks
- Third-party tracking
- Any external data services---## 2. Data StorageAll data you enter into my apps is stored:- Locally on your device
- In your personal iCloud account (if you have iCloud enabled)This data is controlled entirely by you through your Apple Account. I cannot access it.### What My Apps May Store LocallyDepending on the app, this may include:
- Photos and images you add
- Text entries, notes, and descriptions
- Dates, times, and schedules
- Preferences and settings
- Any other content you create within the appAll of this stays on your devices and in your personal iCloud.---## 3. iCloud SyncMy apps use Apple's CloudKit to sync your data across your devices. This means:- Your data is stored in your personal iCloud account
- Apple encrypts your data in transit and at rest
- I have no access to your iCloud data
- You control sync through your device Settings
- You can delete iCloud data through your Apple Account settingsFor details on iCloud security, see Apple's Privacy Policy.---## 4. PermissionsMy apps may request the following permissions:| Permission | Purpose |
|------------|---------|
| Camera | To take photos within the app (processed on-device only) |
| Photo Library | To select existing photos (only photos you choose) |
| Notifications | To send you local reminders (generated on-device) |These permissions are used solely for app functionality. No data from these features is ever transmitted externally.---## 5. Sharing FeaturesSome apps allow you to share data with family or others via iCloud sharing:- Sharing is initiated only by you
- Only people you explicitly invite can see shared data
- You can revoke access at any time
- I cannot see shared data or participants---## 6. Third-Party ServicesI do not use any third-party services.My apps contain no:
- Google Analytics or Firebase
- Facebook SDK
- Advertising frameworks
- Crash reporting tools
- Any external APIs or servicesThe only external service is Apple's iCloud, which you control.---## 7. Data Retention- I retain no data because I never receive your data
- Local data is deleted when you delete the app
- iCloud data follows Apple's retention policies and can be managed in your Apple Account settings---## 8. Your RightsYou have complete control over your data:| Right | How to Exercise |
|-------|-----------------|
| Access | View all your data in the app |
| Delete | Delete items in-app, or delete the app entirely |
| Export | Your data is in your iCloud account |
| Correction | Edit any information directly in the app |---## 9. Children's PrivacyMy apps do not collect data from anyone, including children. Since no personal information is collected or transmitted, my apps comply with COPPA and other children's privacy regulations.---## 10. International Users### European Economic Area (GDPR)
I do not process your personal data. Your data remains in your control via your Apple iCloud account.### California (CCPA/CPRA)
I do not sell or share your personal information. I do not collect personal information as defined by CCPA.### Other Jurisdictions
Regardless of where you are located, I do not collect, process, or store any of your personal data.---## 11. Changes to This PolicyIf this policy is updated:
- The "Last Updated" date will change
- Significant changes may be noted in app update release notes
- The policy will always be available at sebasvisser.nl/#privacyMy commitment to not collecting your data will never change.---## 12. App Store Privacy LabelsAll my apps display "Data Not Collected" in the App Store because:- No data is collected
- No data is linked to your identity
- No tracking occurs---## 13. ContactQuestions about this privacy policy?Email: [email protected]
Website: https://sebasvisser.nl---## 14. Summary| Question | Answer |
|----------|--------|
| Do you collect my data? | No |
| Do you sell my data? | No |
| Do you share my data? | No |
| Do you track me? | No |
| Do you use analytics? | No |
| Where is my data stored? | On your device and your personal iCloud |
| Can you see my data? | No |
| Will this ever change? | No |---Sebas Visser
Independent iOS Developer
sebasvisser.nl

Support for iOs apps

Question? Feedback?

Every app here started the same way: I had a problem, couldn't find a good solution, so I build these apps for myself and share them for free..I'm happy to hear about bugs or ideas - though fair warning, I only add features that solve problems I actually have. These apps aren't my job; they're my tools that I'm sharing with you.No ads. No data collection. Just apps that work.

No data collected.

This privacy policy applies to all plugins and apps, including Work Timer for JiraEffective date: june 30th 2026
Provider: Sebas Visser ("we", "us")
Contact: [email protected]Work Timer is an app for Jira Cloud that lets you run a per-issue stopwatch and log the
elapsed time as a native Jira worklog. This policy explains what data the app processes,
where it is stored, and your choices.## Runs on AtlassianWork Timer is built on Atlassian Forge and runs entirely within Atlassian's
infrastructure. It makes no calls to any servers outside Atlassian, uses no
third-party processors, and includes no analytics, advertising, or tracking. All
data the app stores stays inside the Atlassian Forge platform under your site's data
boundary.## What data we processThe app processes only the minimum needed to run a timer and create worklogs:| Data | Why | Where it's stored |
|---|---|---|
| Your Atlassian account ID | To associate your timers with you (each user's timers are private to them) | Forge storage |
| Jira issue ID / key | To attach a timer to the correct issue and to show you where a timer is running | Forge storage |
| Timer state — start/pause timestamps, accumulated durations, a session identifier, and the auto-stop flag | To keep the stopwatch running across sessions and to compute the time to log | Forge storage |
| The worklog you create — duration, an optional description you type, and the estimate-adjustment choice | To create a standard Jira worklog on your behalf | Sent to your Jira site as a worklog (see below) |We do not collect your name, email address, IP address, location, device
identifiers, or any browsing/behavioral data.## How worklogs are handledWhen you press Log work, the app creates a normal Jira worklog as you (using your
own Jira permissions). That worklog is regular Jira data managed by your organization and
your Jira administrators — it is not stored or controlled by the app, and it remains
in Jira even if the app is uninstalled. App-created worklogs are intentionally
indistinguishable from worklogs entered manually.## How we use the dataThe data is used solely to provide the timer feature and to create the worklogs you
request. It is never sold, shared, or used for any other purpose.## Storage, isolation, and data residency- Timer data is held in the Forge Key-Value Store, hosted by Atlassian.
- Each installation's data is isolated by the Forge platform; one customer's data is
never accessible to another.
- Because storage is provided by Forge, Atlassian's data residency controls apply.## Retention and deletion- A timer's data persists until you Stop & log it, Discard it, or it is closed by
the app (e.g. the 8-hour auto-stop, or eviction of your oldest timer beyond the
per-user limit).
- Uninstalling the app removes the app's stored data in accordance with Atlassian's
data lifecycle for Forge apps.
- Worklogs already written to Jira are not removed by uninstalling — they are Jira data
managed by your administrators.## Legal basis and roles (GDPR)For customers in scope of the GDPR, the Jira site's organization is the data
controller and we act as a data processor for the limited data above. Your Atlassian
account ID is personal data, but it remains within Atlassian's infrastructure and is used
only to scope your timers to you.## Your rights and requestsTo request access to or deletion of data the app holds about you, contact
[email protected]. You can also remove all app-stored data yourself at any time by
discarding your timers or by having an administrator uninstall the app.## Changes to this policyWe may update this policy from time to time. Material changes will be reflected by a new
Effective date at the top of this page.## ContactSebas Visser
[email protected]
https://sebasvisser.nl

Jira Plugins

Worklog Timer

AMAZING

Work Timer (worktimer-sv)A per-user stopwatch on every Jira issue. Start it when you begin work; pause and
resume as you switch focus; stop it to review and log the elapsed time as a native Jira
worklog. Timer state lives server-side, so the clock keeps running even if you close the
panel or browser.Built on Atlassian Forge (UI Kit). It renders as a jira:issueContext module — an
always-visible, collapsible panel in the issue's right-hand context sidebar, so every user
sees it by default (no hunting in the ••• App-actions menu).

# Security Policy — Work Timer for JiraMaintainer: Sebas Visser
Security contact: [email protected]
Last updated: 1-7-2026## Reporting a vulnerabilityIf you believe you've found a security vulnerability in the Work Timer app, please email
[email protected] with:- a description of the issue and its potential impact,
- steps to reproduce (proof-of-concept if possible), and
- any relevant version or environment details.Please report privately and do not disclose the issue publicly until it has been
resolved. We aim to acknowledge reports within 5 business days and to remediate
confirmed vulnerabilities in line with the Atlassian Marketplace security bug-fix
policy
(critical issues prioritized).## Scope & architectureWork Timer is built entirely on Atlassian Forge and runs on Atlassian infrastructure
("Runs on Atlassian"):- No data egress — the app makes no calls to any host outside Atlassian and uses no
third-party services, analytics, or tracking.
- Least privilege — it requests only storage:app (per-user timer state) and
write:jira-work (creating worklogs).
- User-context actions — worklogs are created via asUser(), bound by each user's own
Jira permissions. All user/issue identifiers derive server-side from the Forge request
context, never from client input.
- Data storage — only per-user timer state in Forge's Key-Value Store, isolated per
installation. No secrets are stored or logged.## DependenciesRuntime dependencies are limited to Atlassian's official @forge/* packages. Third-party
dependencies are monitored with automated tooling (npm audit) and updated as fixes
become available.## DisclosureWe will coordinate disclosure with the reporter and, where required, notify affected
customers and Atlassian in line with Atlassian's incident and vulnerability notification
guidance.

# Work Timer: Install and User GuideWork Timer adds a per-user stopwatch to every Jira issue. Start it when you begin work, pause and resume as you switch focus, then stop to review and log the elapsed time as a native Jira worklog, without leaving the issue. Timer state is stored on the server, so the clock keeps running even if you close the panel, the tab, or your browser.- Runs on Atlassian (Forge): no external servers, no data leaves your Atlassian site.
- Attributed to you: worklogs are created as the logged-in user, exactly like a manual worklog.
- Available in 10 languages: follows your Jira language setting.## 1. Where to find it (important)Work Timer appears as a panel called "Work Timer" in the right-hand context sidebar of the issue view, the same column as Details, Assignee, Labels, and so on.Important: It is not in the main content area and not hidden behind the ••• Apps menu. Open any issue and look at the right sidebar. If the panel is collapsed, click the "Work Timer" heading to expand it. Jira remembers your expand and collapse choice per user.Where it sits on the issue view: the main content area on the left holds the Description, Comments and Activity. The right sidebar holds Details, Assignee, Labels and the Work Timer panel. Inside the panel you see the elapsed time (for example 0:00:00) and a Start timer button.## 2. Install### For Jira administrators1. Go to the Atlassian Marketplace listing for Work Timer and click Get it now (or Try it free), or install it from Jira → Apps → Explore more apps and search for "Work Timer".
2. Choose the Jira site to install onto and confirm. Work Timer is a Forge app and runs on Atlassian's infrastructure, so there are no external URLs to allow-list.
3. That's it. The Work Timer panel now appears on every issue for every user, and there is nothing to configure per project.Permissions the app requests at install:- write:jira-work: create the worklog when a user logs time (as that user).
- storage:app: store each user's private timer state, keyed by their Atlassian account ID.The app requests no read scopes and declares no network egress.### First time you log work: one-time consentThe first time you (each user) log work, Jira shows a short one-time consent prompt, because the app writes the worklog as you. Click Allow / Accept, then click Log work again to complete it. You will not be asked again on that site.Tip: if you clicked Log work and nothing seemed to happen, look for this consent prompt, approve it, then retry. This is normal Forge behaviour on the very first worklog.## 3. Use it### Start a timerOpen an issue and, in the Work Timer panel (right sidebar), click Start timer. The clock begins counting up (H:MM:SS).### Pause and resume- Pause freezes the clock and banks the time so far.
- Resume continues from where you paused, so your banked time is preserved.Starting or resuming a timer on one issue automatically pauses any other running timer you have, so you only ever run one at a time. Your paused time is never lost.### Stop and log1. Click Stop & log. The timer freezes and a review dialog opens.
2. The dialog shows the tracked time and pre-fills a duration you can edit (Jira syntax, for example 1h 30m). Time is tracked to the second and logged rounded up to the next whole minute (minimum 1 minute, since Jira rejects shorter worklogs).
3. Optionally add a work description.
4. Choose Remaining estimate:
- Auto: reduce the remaining estimate by the logged time (default).
- Leave: don't change the estimate.
5. Click Log work. The worklog is written to the issue's native Work log and the timer clears.You can verify it under the issue's Activity → Work log (or the Time tracking section). Work Timer's entries look exactly like manually entered worklogs.### DiscardOn a paused timer, Discard deletes that timer without logging anything. This is the only destructive action and it asks for confirmation.### See your other timers at a glanceBecause the panel is on every issue, the top of the panel summarises your other timers:- Running: the one issue currently timing, with a live clock and a link to jump to it.
- Paused: links to your paused issues.The collapsed panel header also shows a "Running" badge on whichever issue is currently timing, so you can spot it while scanning.### Automatic safeguards- Auto-stop at 8 hours: if you forget a running timer, it stops itself at 8 hours so it can't inflate your logged time. You will see an "Auto-stopped after 8 hours" note when you next open it. Review and log or discard as usual.
- Up to 5 active timers per person: starting a 6th automatically logs and closes your oldest timer, and you get a note telling you which one and how much was logged.## 4. Troubleshooting- "I don't see Work Timer on the issue." Look in the right-hand sidebar (with Details), not the main content area. If the "Work Timer" heading is collapsed, click it to expand. Confirm an admin has installed the app on this site.
- "I clicked Log work and nothing happened." Approve the one-time consent prompt shown on your first worklog, then click Log work again.
- "You do not have permission to log work on this issue." Your Jira account lacks the Work on issues permission for that project. Ask your Jira admin to grant it.
- "Work cannot be logged here." Time tracking may be disabled for that project, the worklog field may be hidden, or the issue may be archived or closed to worklogs. Check the project's time-tracking settings.
- "The connection dropped while logging..." The worklog may already be saved. Open the issue's Work log and check: if it is there, discard the timer; if not, try again in a few minutes. The app is designed to never create a duplicate.
- The panel shows "Couldn't load your timer." Click Retry. If it persists, reload the issue.## 5. Privacy and dataWork Timer stores only your timer state (issue IDs, elapsed time, timer status), keyed by your Atlassian account ID, inside Forge storage on your Atlassian site. It does not collect your name, email, IP or location, and it sends nothing to any external service. Uninstalling the app removes its stored data. Full details are in the Privacy Policy.## 6. SupportQuestions, problems or feedback: [email protected].