Privacy notice

Accounts and sign-in

We store your account email, display name, profile description and account identifiers. Password sign-in stores a password hash rather than your readable password. Browser and app session identifiers keep you signed in. When an available Apple, Google or X option is used, we receive the provider's account identifier and, when supplied, your name and verified email. We use this information to create or connect your account and authenticate you. Your provider-derived display name can appear publicly with your contributions; you can edit it. Your email is not displayed on your public profile. We do not receive your Apple, Google or X password.

The current Google integration requests basic sign-in, email and profile information. It does not request Gmail, Drive or contacts access. Social-sign-in credentials are used for authentication, not to publish to your social accounts. We store the provider identifier linked to your DigiGraf account; temporary authorization information is used only to finish sign-in.

Posts, places and activity

We store the content and photos you publish, Digi locations and settings, comments, likes, reposts, follows, saved Digis and alert preferences. Public posts and profile details can be seen by other people and shared outside DigiGraf. Restricted content follows the Digi's access rules. Anonymous contributions hide the author from other viewers but remain associated with the account in our records. Curators can manage content in their communities. Reports and moderation actions are recorded.

Location, scans and measurement

Find sends your current or chosen search area and radius to DigiGraf. Manual area search is available without location permission. Every new post requires a fresh precise device location; creating a Digi and location-restricted actions also use location checks. The app does not continuously track your location in the background. DigiGraf records place access and nearby contribution activity. Signed-in token scans record the account, Digi, token and scan time for access and your Vault. A token link is not certified proof of physical attendance. Visible feed views, saves, scans and drop interactions can contribute to activity counts. These are distinct from radar impressions.

Device storage and service providers

Drafts, saved local places and some public feed content can remain on your device. Signed-in data such as account saves and Vault history is stored by DigiGraf. Post photos are resized and re-encoded without their original EXIF location metadata. The photo picker provides only the image you select.

Web maps load tiles from OpenStreetMap. Web place searches send the text you submit to OpenStreetMap’s Nominatim service; ZIP searches use Zippopotam.us. Native maps and place searches use Apple Maps. These services receive the requests needed to display maps or search places. Optional push notifications use Apple Push Notification service, and we store the device token and delivery status. Hosting and network services process requests needed to run DigiGraf, including technical connection information. Links to other sites use those sites' own practices.

Cash drops and Wallet

Live cash funding and bank payouts are not enabled in this beta. Authorized sandbox tests can store campaign content, task answers, playback progress, claim records and transaction identifiers. Stripe handles hosted test checkout and payout setup. DigiGraf sends the account details needed for that setup and keeps provider identifiers and payment status; its forms do not collect raw card or bank account details.

Your choices and retention

You can edit your profile, manage your own content where controls are available, change saved-Digi alerts, decline push notifications, change device location permissions and sign out. Removing the app does not delete your server account or published content. The beta has no self-service account deletion or general automatic deletion schedule. Records can remain for service operation, abuse investigation and transaction reconciliation; backups and audit records can outlast removal from normal views.

Contact tony@cewebdev.com to request access, correction or deletion, or help with a linked sign-in provider. We may need to verify that a request concerns your account. Revoking a provider's access does not itself delete your DigiGraf account. Changes to these practices will be reflected in this notice with an updated effective date.