Privacy Policy | Manor

Manor (“Manor,” “we,” “us”) is a voice-first expense journal for Morocco, offered as an Android app and website. It is built and operated by Rida Lamhadri, an independent developer in Morocco. This policy explains the data handled on this website and in the Manor app, and the choices available to you.

Questions or requests: support@talktomanor.com.

Data collected on this website

The Android test form collects the first name and Gmail address you provide, plus the consent-notice version and registration time. We use this data to operate the test and related launch communications. The Gmail address is normalized to prevent duplicate registrations.

The registration and deletion forms use Cloudflare Turnstile. We do not store the Turnstile token or IP address with requests. Cloudflare Web Analytics measures aggregate, cookieless website visits and performance. We do not use Google Analytics or advertising cookies.

Android beta test emails

To send the Android beta invitation and the necessary test communications, Manor uses Resend as its email-delivery and contact-list service provider and processor. Resend receives only your first name and Gmail address. Resend processes the beta invitation and the necessary delivery, subscription, and unsubscribe information. Open tracking and click tracking are disabled.

You can unsubscribe at any time using the unsubscribe link in the email or by contacting support@talktomanor.com. Your contacts are kept during the test and launch program, or until you unsubscribe or are removed; they are then removed from active lists and deleted where applicable.

Data in the Manor app

Google account and Manor profile

To use the app, you choose Continue with Google. Google confirms your identity and gives Manor your name, verified email address, and provider identifier. Manor then creates a profile linked to that account. You can edit the name shown in Manor, but not the verified address supplied by Google.

Better Auth runs inside Convex and manages the account, Google provider link, and sign-in sessions. Manor stores internal profile and session identifiers, associated dates, and the data needed to authenticate you and assign each record to the correct account. Manor requests only standard Google identity information: profile, name, and email. It does not request offline access or access to Gmail, Drive, Contacts, or other Google products.

• Expense entries: amount, category, date, note, and the original transcript of what you said or typed.
• Budgets and fixed expenses that you enter.
• Voice recordings you choose to make when capturing an expense.
• Account-specific local data: pending captures, files, cache, onboarding progress, and scheduled reminders.

The app contains no advertising and connects to no bank account. We never sell this or any other personal information.

Mobile product analytics

Manor uses limited mobile product analytics to understand completed feature usage and service reliability. Analytics is enabled by default only after a Manor account is authenticated. The account owner can disable it at any time in Settings. The choice is account-scoped and synchronizes across that account’s devices. When analytics is disabled, Manor stops collecting these events for that account.

PostHog is our service provider and processor for this analytics. Manor uses PostHog Cloud US and sends events to https://us.i.posthog.com. Manor identifies the account only with its pseudonymous internal appUserId, never with a name, email address, Google or provider identity, or Better Auth identity. On sign-out or account switch, Manor clears the old identity from the on-device analytics client and stops capture for the old account.

Manor records only allowlisted completed feature milestones: sign-in and setup completed; capture started, queued, or resolved; first expense saved; month view opened; search used; month exported; fixed-expense proposal resolved; quick capture opened; and post-save context shown. Depending on the milestone, properties are limited to voice or text mode, a normalized capture outcome, the offline reason, export format, or normalized proposal outcome. They do not contain the content used in the feature.

For Gemini reliability, Manor records one content-free event containing only voice or text mode, the fixed model, a normalized outcome and error class, processing latency, and a bounded retry count. After authentication, and only while analytics is enabled, Manor may also record sanitized JavaScript errors: error type, a fixed label, generated-code locations, and the app surface. A crash report may include a short technical error message produced by the app’s own runtime; such a message names a programming identifier, never anything from your journal. All other error text is replaced with a general category label before it is sent.

Manor does not send PostHog names, email addresses, Google or provider identities, Better Auth identities, amounts, budgets, currency, categories, merchants, notes, transcripts, typed capture content, voice recordings, recording metadata, search text, export content, error text other than the short runtime messages described above, console or log output, or network request or response bodies.

Manor does not use Session Replay, screenshots, automatic screen capture, touch or text autocapture, native crash capture in this workstream, console capture, advertising profiling, or remote analytics experiments, surveys, or feature flags. GeoIP and location enrichment are disabled for these events; this does not mean network services cannot receive an IP address while routing a request. Mobile and server collection each have an independent production kill switch.

How voice and text are understood

When you record or type an expense, Manor securely sends the recording or text to Google Gemini. Gemini returns the structured amount, category, date, note, and transcript, which Manor stores in Convex. Gemini processing is separate from Google sign-in.

A voice recording is uploaded for this processing, and Google’s Gemini performs the parsing. Once the expense is saved, the recording is deleted. A recording attached to a capture that still needs your attention is kept only until you resolve or discard that capture.

Why we use this data

• To sign you in and maintain the security of your session.
• To operate your journal, budget, and account synchronization.
• To turn your voice or text into an expense.
• To understand completed feature usage and service reliability without financial, voice, or typed content.
• To run the Android test and prevent abuse of public forms.
• To measure aggregate website traffic and performance.

Service providers we use

• PostHog : mobile product analytics and reliability processor, used through PostHog Cloud US with the pseudonymous appUserId and limited events described above.
• Convex : database, file storage, server functions, and Better Auth hosting. Convex stores the profile, account and session data, expenses, budgets, fixed expenses, transcripts, voice files, and public requests.
• Google : Google OAuth confirms your identity; the Gemini API processes voice and typed captures. These services apply their own terms and privacy policies.
• Cloudflare : website hosting, Turnstile form protection, and aggregate cookieless website analytics.
• Resend : email-delivery and contact-list service provider and processor for the Android beta test. Resend receives only your first name and Gmail address, with open tracking and click tracking disabled.

We share only the data these providers need to operate Manor. We do not share data for advertising and never sell personal information. We may disclose data if required by law or to protect the rights and safety of the service and its users.

Security

Data is sent over encrypted HTTPS connections. Sign-in secrets remain on the server, and local session material uses the device’s secure storage. No method is completely secure; we nevertheless take reasonable steps to protect your information.

Retention

We keep account, session, and app data while your Manor account exists or until it is deleted. Test registrations remain during the test and launch program or until you ask us to remove them. We target completion of a verified external deletion request within seven calendar days; after completion, its email is removed and only minimal non-personal completion status and dates remain.

Your beta-test email contacts held in Resend are kept during the test and launch program, or until you unsubscribe or are removed; they are then removed from active lists and deleted where applicable.

PostHog retains analytics events according to the retention plan and settings that apply to Manor’s project; we do not promise a fixed duration. After account deletion, Manor asynchronously requests deletion of the PostHog person identified by the pseudonymous appUserId and associated events. Some aggregate or already de-identified information may no longer be linkable to the account.

Google, Convex, PostHog, Cloudflare, and Resend may retain some information under their own terms, security backups, and legal obligations. We do not promise to delete information those providers must retain independently of Manor.

Delete your account and data

Full instructions and the public request form are on our Data deletion page.

• In Account, choose Delete account and all data. After confirmation and, when required, signing in again with the same Google account, Manor deletes your product data, files, profile, provider link, sessions, and account-specific local data.
• Without the app, submit the public form with the exact Google-account address. Rida Lamhadri emails that address and requires a reply from the same address before deletion. The receipt never reveals whether an account exists.

If you later return with the same Google account, Manor creates a new empty account. Deleted expenses, budgets, files, and other data do not reappear.

Children

Manor is intended only for adults aged 18 or older. If you believe a child has provided information, contact support@talktomanor.com.

Changes to this policy

We may update this policy as Manor evolves. When we do, we will change the effective date at the top of this page.