SpecPour

SpecPour Privacy Policy

en-AE 2026-06-06

SpecPour keeps cocktail costing and staff-spec work on your device. It is built for venue-owned facts without a SpecPour account, ads, hosted sync, supplier catalog, POS integration, live vendor pricing, or remote AI pro

Overview

Information you enter

SpecPour can store ingredient names, bottle or package costs, package sizes, pour sizes, supplier notes, workspace currency code, custom unit labels, custom unit symbols, custom unit conversion factors, recipe ingredients, recipe amounts, method notes, glassware, garnish, reusable staff-spec options, prep notes, batch sizes, target pour-cost percentages, selected menu prices, stale-cost review dates, and staff spec fields that you choose to enter. Device language and region can seed formatting, but the editable workspace currency code controls money display for the venue.

Calculations, device language, and region

Device language and region can seed currency formatting, decimal separators, language, and unit defaults. The workspace currency code is editable because a venue may price in a different currency than the device region. Standard unit symbols are treated as symbols, while custom unit labels, custom symbols, method snippets, imported values, recipe names, supplier names, and venue notes are user-entered data. SpecPour does not use device language or region to look up local ingredient prices, distributor catalogs, tax rules, deposit rules, service-charge rules, alcohol-pricing rules, or legal menu-pricing requirements.

User-facing data inventory

Persisted records: Ingredient cost rows, supplier notes, workspace currency code, custom unit labels, custom symbols, conversion factors, recipe rows, method notes, glassware, garnish, reusable staff-spec options, batch sizes, target pour-cost percentages, menu prices, stale-cost review dates, and staff-spec fields stay on this device.
Transient search and filters: Ingredient, recipe, and staff-spec filters or editor drafts are workflow state; SpecPour does not store search-query history.
Generated exports: Cost-book share text and staff-spec output are generated from current venue data when you prepare or share them.
Cached or prepared exports: Prepared share/export text stays local until replaced, shared, hidden/restored, or reset; files saved or shared outside the app are controlled outside SpecPour.
Notification state: None. SpecPour does not schedule reminders or notification alerts.
Recent history: No separate recent-history list. Stale-cost review dates are saved ingredient records, not hidden usage history.
Clear or reset controls: Use edit, hide, restore, delete, custom unit controls, staff-spec option controls, and reset/export controls to manage local venue data.

Analytics, Logs, And Diagnostics

SpecPour 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 ingredient costs, supplier notes, workspace currency code, custom unit catalogs, recipes, menu prices, target pour-cost percentages, stale-cost warnings, cost-book share text, and staff spec content.

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. SpecPour 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 SpecPour'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 full vendor lists, private cost books, supplier prices, custom unit catalogs, recipes, target pour-cost percentages, menu prices, staff specs, invoices, exports, or screenshots that identify a venue unless support explicitly asks for a redacted example.

What SpecPour does not use

SpecPour does not use advertising SDKs, third-party analytics SDKs, account tracking, cross-app tracking, hosted sync, supplier-catalog lookup, POS data, ordering integrations, inventory variance reporting, market-price benchmarking, live vendor pricing, or remote AI processing.

Your choices

You control what you enter, keep, edit, hide, restore, delete, export, or share. Review cost-book share texts and staff specs before sending them to another person because they may include ingredient costs, recipes, supplier notes, workspace currency code, custom unit labels or symbols, target pour-cost percentages, menu prices, and stale-cost warnings.

Public routes

Privacy policy: https://apps.dartscreative.com/en-ae/apps/specpour/privacy/
Support page: https://apps.dartscreative.com/en-ae/apps/specpour/support/

Contact

Privacy requests: privacy@dartscreative.com
Product support: support@dartscreative.com