Sillkeep
Sillkeep Privacy Policy
Sillkeep is a local-first plant care scheduler. It works without an account, ads, backend, hosted sync, third-party analytics SDK, remote AI processing, plant identification, plant diagnosis, expert chat, marketplace, or
Overview
Sillkeep is a local-first plant care scheduler. It works without an account, ads, backend, hosted sync, third-party analytics SDK, remote AI processing, plant identification, plant diagnosis, expert chat, marketplace, or hardware sensor integration.
Information you enter
Sillkeep can store plant names, room or shelf notes, care tasks, care intervals, due dates, last-care dates, snooze or skip state, reminder state, reminder alert state, widget state, plant notes, photo references, photo counts, care history, and export summaries that you choose to create.
Storage and sharing
Sillkeep is designed to keep plant profiles on the device. Plant profiles, care schedules, notes, photos, reminder state, reminder alert state, widget state, and care history do not leave the device through Sillkeep unless you choose to export or share them. JSON and CSV exports include plant profiles, care history, and photo counts or photo log entries, not raw image files.
Notifications and widgets
Sillkeep can store local reminder, reminder alert, and widget state for due care tasks. Notification delivery depends on iOS notification settings and notification permission. Widget display depends on the device, operating system, and widget configuration. Sillkeep does not use notification or widget state as proof that plant care happened.
Photos and plant notes
If you add photos or notes, those files remain user-controlled files. Imported photo copies stay local until you delete or archive the plant, and JSON or CSV export does not include raw image files. Sillkeep does not verify plant identity, diagnose plant health, prescribe treatment, assess toxicity, evaluate pesticide use, or replace advice from a qualified local plant professional.
User-facing data inventory
- Persisted records: Plant profiles, archived plants, custom care tasks, care intervals, due dates, last-care dates, snooze or skip state, reminder state, reminder alert state, widget state, plant notes, imported photo files, photo counts, and care history stay on this device.
- Transient search and filters: Shelf filters and Today views are workflow state; Sillkeep does not store search-query history.
- Generated exports: JSON and CSV exports are generated from plant profiles, care tasks, care history, notes, and photo counts when you create them.
- Cached or prepared exports: No raw image files are included in export. Imported photo files stay local until removed with the plant/photo controls or app data reset.
- Notification state: Care reminders can keep opt-in state, task reminder state, reminder alert state, widget state, and pending notification requests. iOS notification permission controls alert delivery.
- Recent history: Care history is a saved plant record. Sillkeep does not keep a separate recent-history list.
- Clear or reset controls: Use plant archive/delete, task archive/delete, photo remove, reminder off, and app reset/removal controls to remove plant records, care history, imported photo files, reminders, widgets, and exports.
Analytics, Logs, And Diagnostics
Sillkeep includes a first-party local analytics wrapper for privacy-safe product event names. Those events do not leave the device, are not persisted by the app, and are not sent to a remote analytics service because the default analytics sink is empty.
The app's local event names are limited to workflow states such as create, update, archive, export, reminder, attachment, calculator, support, or screen events. They must not include plant profiles, plant names, room or location notes, care schedules, notes, photos, reminder state, widget state, care history, JSON exports, and CSV exports.
Debug builds used by developers may print the event name and analytics pipeline to the local debug console. Release builds do not write these analytics logs. Sillkeep does not include a third-party analytics SDK, advertising SDK, attribution SDK, third-party crash-reporting SDK, IDFA use, App Tracking Transparency prompt, account tracking, or cross-app tracking.
Apple may separately provide App Store, TestFlight, crash, diagnostic, or aggregate App Analytics reports through Apple-operated systems, App Store account controls, iOS privacy settings, or diagnostic settings. Those Apple-operated reports are separate from Sillkeep's local analytics wrapper. The App Store privacy label lists data Darts Creative collects through its own systems, such as user-initiated support emails, and does not treat local-only event names as uploaded analytics or tracking.
Support requests
If you contact product support at support@dartscreative.com, the email address and details you send are used to answer the support request.
Support screenshots, logs, and email attachments can include private app data if you include them. Do not send plant photos, room or home-location notes, care notes, household details, JSON exports, CSV exports, or screenshots that identify a home unless support explicitly asks for a redacted example.
What Sillkeep does not use
Sillkeep does not use advertising SDKs, third-party analytics SDKs, account tracking, cross-app tracking, hosted sync, remote AI processing, plant identification services, plant diagnosis services, expert chat, marketplace listings, lead generation, or hardware sensor integrations.
Your choices
You control what you enter, keep, edit, delete, export, or share. Review exported plant history before sending it to another person because exports may include plant names, locations inside the home, care notes, dates, photo counts, photo log entries, and other household details, but not raw photo files.
Public routes
- Privacy policy:
https://apps.dartscreative.com/en-in/apps/sillkeep/privacy/ - Support page:
https://apps.dartscreative.com/en-in/apps/sillkeep/support/
Contact
- Privacy requests:
privacy@dartscreative.com - Product support:
support@dartscreative.com