Privacy Policy

1. Who operates Dayverie

Abdirahman Areys operates Dayverie. This policy explains how information is handled when you use our day-planning app and related services. Contact us at admin@dayverie.com. The Service is for adults aged 18 or older. A statement of age is an eligibility requirement; it is not a guarantee that every user's age has been independently verified.

Acknowledging this policy does not waive your privacy rights or authorize every optional use of your information. Where consent is required, we seek it for the relevant purpose. Applicable privacy protections depend on your location, our activities and the law's scope.

2. Information and purposes

• Account information: Supabase handles account authentication, including email/password or information supplied by Apple or Google sign-in. We use account identifiers and any profile information you provide to operate and protect your account. Profile completion requires a name and date of birth; we derive your age to check eligibility and personalize plans. Older profiles can also contain gender information. You can request correction through the contact above.
• Planning and personalization: We process your selected city or destination, questionnaire answers, interests, mood, budgets and requests to generate suggestions. Saved plans may include answers, selected locations and coordinates, activities, feedback and outcomes. We use planning history and preference signals to avoid repetition and infer preferences. Free-text requests can contain personal or sensitive details; avoid including information unnecessary for planning.
• Dietary and venue preferences: You can choose dietary needs (for example allergies, vegetarian or halal food) and whether to avoid venues centred on alcohol. These choices are optional and are used only to filter and select places for your plans. They can reveal health information or religious beliefs, so we treat them as sensitive: they are not shared publicly, not used for advertising, and you can change or remove them in account settings at any time.
• Location: If you grant foreground location permission and have not selected a destination, the app can obtain device coordinates to plan nearby outings. Selected destination coordinates may represent where you intend to go rather than where you are. Coordinates and search queries support geocoding, place suggestions, maps and weather. Permission can be changed in device settings; you can choose a destination for planning.
• Saved and current outings: We retain plans and related progress, selections and feedback to show Saved and Now experiences and provide personalization.
• Optional archive and attachments: Automatic camera-roll reconstruction has been retired from the current app. Previously saved archive records, optional manual photo attachments, notes and export tools may remain available. Existing archive information can also contribute to your preferences. Photo permissions support these optional actions. Memory indexes and quality caches are stored on the device, rather than a cloud Memories backup. Historical versions could process image previews through Gemini for visual quality review; previews may reveal people or sensitive content. Older installed versions may continue to provide their earlier photo-processing features.
• Usage and reliability: Product events can include an account ID, event name, selected properties and timestamp. They support product measurement and operation and are not all anonymous. Sentry handles crash and error reports; default personal-information collection and session replay are disabled, but error messages, stacks or context can still contain personal information.
• AI assistant connectors and the Dayverie API: You can link your Dayverie account to a third-party AI assistant or connector platform (for example Muse) at our connection page. When you use Dayverie through a connector, we receive the planning request it sends on your behalf: coordinates, start time, duration, party size, company, budget, transport preference, short free-text "vibe" and "avoid" preferences, and the identifier of your linked account. Your saved dietary and venue preferences may also be applied. We use this information only to create, return and let you revise the requested outing. Connector access uses a scoped key that expires after 30 days and that you can revoke at any time on the connection page. The assistant platform handles your conversation under its own privacy policy; we receive only the requests it sends to our API.
• Purchases and support: RevenueCat processes purchase/subscription history, entitlements and an account-linked user identifier. The app store handles payment details for in-app purchases. Purchases made through a connector are paid with Stripe Checkout: Stripe collects your payment details, and we receive only the payment status, amount, currency and Stripe transaction identifiers. We process communications you send us to respond and resolve problems. Security and abuse controls may process technical identifiers, requests and logs.

3. Providers and AI

We use providers to deliver the Service. Supabase supplies authentication, database, storage and server functions; Google Gemini processes planning requests and preference-inference inputs; Google Places supplies place information; Mapbox processes location searches and route estimates; OpenWeather receives coordinates for weather; Cloudflare supports delivery, infrastructure and the hosting of our API; RevenueCat supports subscriptions; Stripe processes payments for connector purchases; and Sentry supports reliability. Providers may receive request metadata and technical information in addition to the information needed for their function. Our website and infrastructure may process IP addresses, browser information and request logs to deliver pages and prevent abuse.

AI personalization can use summaries of activity signals, feedback and recent or rated itineraries, rather than only your latest prompt. Google's Gemini API terms explain how AI inputs and outputs are handled. Those terms distinguish paid services, which exclude use of prompts and responses to improve Google products, from unpaid services, which permit that use and human review. The applicable treatment depends on the project and service configuration; safety and legal logging can still apply. Avoid including sensitive information that is unnecessary for your request. AI and infrastructure processing can occur outside your country.

Google Places use is subject to Google's Terms of Service and Google's Privacy Policy. Mapbox receives search text or selected stop coordinates through our server for geocoding and route estimates. Its Privacy Policy describes its processing. Third-party links and services have their own practices.

4. Sharing

When you create a public plan link, anyone who receives or obtains its token can view the shared plan while the link remains valid. Shared fields can include city, dates, weather, venue selections and venue coordinates, and optional display name or theme. Exact device GPS, private questionnaire/history and local photo paths are excluded from the public payload. A shared link is not limited to your account. Current links expire after 30 days; expired link records are scheduled for deletion seven days later. Others may retain copies they viewed or downloaded.

Dayverie does not currently offer a public community feed. Any editorial outing collections we make available are curated by us. We do not sell personal information or share it for advertising.

Legal and government requests. We disclose personal information to a government authority or other third party only when legally required to do so by a valid order or legal process, or where reasonably necessary to protect people's safety, rights or the security of the Service. We review each request for its legal basis and scope, disclose only the minimum information required, and notify the affected user unless we are legally prohibited from doing so. Requests and our responses are recorded.

5. Retention and deletion

We keep account, planning and personalization information while needed to provide the Service and for applicable security, dispute and legal purposes. Personalization may use recent activity, but this does not automatically delete older account records.

Account deletion removes the authentication account and purges associated application records, including saved itineraries, preference profiles, attributed product events and owned shared links. Limited subscription-revocation records can remain, including provider, transaction/subscription identifiers, original account UUID, optional RevenueCat original user identifier, revocation time and reason. These identifiers are not anonymous. We retain these limited records to prevent revoked purchases from being reused and to address billing, security and legal obligations.

For connectors and the Dayverie API: account deletion also deletes your connector connections and the outings created through them. Records of connector purchases are kept for tax and accounting, with the link to your account and your planning request removed. Connector outings expire and are deleted automatically by scheduled jobs, and disconnecting a connector revokes its access immediately.

Deletion does not itself cancel an app-store subscription, erase copies held by recipients or instantly remove provider logs/backups. Local archive records and caches may require device-level or in-app removal and are not a cloud memory backup. Provider retention and legal exceptions may affect deletion timing and scope. Contact us for help with a deletion request.

6. Choices and privacy requests

You can change device permissions, choose which optional information to provide, and request account deletion through account settings. To request access, correction, deletion or withdrawal of consent, contact admin@dayverie.com. We may need proportionate information to verify your identity. Withdrawal can affect features that require the information.

Depending on applicable law, you may also have rights to portability, restriction or objection, and to complain to a privacy regulator. We address requests within applicable legal deadlines and explain relevant limitations. The availability and scope of these rights depend on applicable law.

7. Security and international processing

We use measures designed to protect information, including authenticated access and secure transport. No system provides absolute security. Providers may process information in the United States and other countries with different privacy laws. A selected storage region does not mean all provider processing stays there. Applicable contractual and legal safeguards govern transfers; acknowledging this policy does not replace a legally required transfer mechanism.

8. Adults-only service and policy changes

People under 18 are not eligible to use the Service. If you believe an underage person has supplied information, contact us so we can investigate and take appropriate steps. Parental permission does not override the Service's adult eligibility requirement.

We update this policy when practices change and update its date/version. We provide appropriate notice of material changes and seek consent for new purposes where required. Continued use is not blanket consent to unrelated optional processing.