Privacy Policy

Who we are

AZZOUNIVENTURES LTD ("Tendly", "we", "us"), a company registered in England and Wales, company number 17394168, registered office Office 20580, 182-184 High Street North, London, E6 2JA. We are the data controller for the personal data described in this policy. We are registered with the UK Information Commissioner's Office, registration number ZC228944.

Questions about this policy or how we handle data: support@tendlyhq.com.

What Tendly does

Tendly is a relationship-reminder app. You add contacts, tag them by relationship type, and Tendly reminds you to stay in touch on a schedule, tracks birthdays and anniversaries, and tracks a simple streak of how consistently you've kept in touch.

An important note about whose data this is

Most privacy policies describe data about you, the user. Tendly is unusual: to work at all, it also stores personal data about the people you add as contacts — most of whom are not Tendly users and have never agreed to anything.

When you add a contact, you may enter their name, phone number, email, birthday, anniversary date, a photograph, and free-text notes. You may also record their employer/organisation, school, and role or job title — particularly for professional or education-related relationship tags.

You are responsible for the information you record about other people. Tendly does not verify who your contacts are, whether they know you're recording this information, or whether they're an adult. A contact tagged Classmate, for example, may be a minor — Tendly does not check this, and by using the app you accept responsibility for what you choose to record about a third party.

The free-text notes field and custom special-date titles can, depending on what you write, capture sensitive categories of information about a third party — for example their health, religion, or your opinions about them. We do not review or moderate this content beyond storing and displaying it back to you; use judgement about what you record.

Data we hold about you (the account holder)

• Email address
• Password (stored as a hash by our authentication provider — we never see or store it in plain text)
• Sign-in method (email, or Sign in with Apple)
• The category you select during onboarding (student, professional, founder, or personal) — used only to tailor default settings
• Notification preferences
• Trial start date, onboarding completion status, and subscription status
• Your referral code, who referred you (if anyone), and your referral count
• Pseudonymised usage events (see "Where your data is processed" below for exactly what this does and doesn't include)

Data we hold about your contacts (third parties)

• Name
• Phone number and/or email, if provided
• Birthday and/or anniversary date
• A photograph, if added
• Free-text notes
• Employer/organisation name, school name, and role or job title, if provided
• Relationship tag, and a more specific sub-type where relevant (for example "Brother" under a Family Member tag)
• Check-in cadence, check-in history, and a simple streak figure showing how consistently you've kept in touch — all derived automatically, never separately entered

Lawful basis for processing

• Your account data: performance of our contract with you, and our legitimate interest in operating and improving the service.
• Your contacts' data: processed on the basis of your own legitimate interest in maintaining your personal and professional relationships. We have no direct relationship with your contacts and use their data for no purpose beyond displaying it back to you and generating reminders.

Who can see this data

Access is restricted at the database level so one user's account cannot read another's. We're honest about the limit of this: our hosting provider's administrative dashboard operates above those restrictions, so it would be inaccurate to claim your data is technically inaccessible to us as the operator. We don't access individual accounts except to provide support you've requested, investigate abuse, or comply with a legal obligation. As a matter of internal policy, we do not browse individual accounts out of curiosity — there is no legitimate reason to look at someone's contact list, and we don't.

Where your data is processed (sub-processors)

• Supabase (database, authentication, file storage) — EU region
• RevenueCat (subscription and purchase management) — United States
• Apple (App Store, in-app purchases, Sign in with Apple) / Google, if you sign in with Google
• Brevo (transactional email — account confirmation, password reset)
• PostHog EU Cloud (product analytics) — EU region. Only a fixed, pre-approved set of pseudonymised events and properties is sent — things like which relationship tag you used, how many days a check-in was overdue, or whether the paywall was viewed. We never send PostHog your contacts' names, phone numbers, emails, photographs, free-text notes, custom tag labels, or special-date titles. Your identity on PostHog's side is an anonymous account ID, never your email. Session recording is permanently disabled — we do not and will not record your screen.
• Sentry (error and crash monitoring) — EU region, Frankfurt. Sentry receives only an anonymous internal ID, never your name, email, or location.

Reminders are scheduled and delivered locally on your device, not through Apple, Google, or any other third-party push service — reminder content (contact names, dates, notes) is never transmitted off your device for delivery purposes.

Because RevenueCat and the app stores sit outside the UK/EEA, data needed to process a purchase is transferred internationally as a necessary part of that transaction.

We may, in future, share aggregated and pseudonymised usage data — with identifying information already removed — with contractors or collaborators for internal analysis, under a written data processing agreement. This would never include your contacts' personal information or anything that identifies you individually.

Security

• Row-level security on every database table restricts each account to its own data.
• Database permissions are additionally limited to the minimum each part of the app actually needs, as a second layer behind row-level security.
• Photographs are stored in a private file bucket, accessible only via short-lived signed links, not a public URL.
• Passwords are hashed by our authentication provider.
• Data in transit is encrypted (HTTPS/TLS).
• We never receive or store your payment card details — purchases are handled entirely by Apple's or Google's own billing systems.

How long we keep data

Deleting a contact: removed from view immediately; the record is retained for 30 days in case of accidental deletion, then permanently removed.

Deleting your account: deactivated and hidden immediately. Sign back in within 30 days and your account, including your contacts, is fully restored. After 30 days, the account cannot be restored and complete removal of your stored data occurs within a reasonable period thereafter. Residual copies may also persist for a limited period in routine infrastructure backups, after which they are automatically overwritten along with all other backup data.

The 30 days above is a restore guarantee, not a fixed erasure date — we do not promise permanent deletion on a specific schedule beyond it.

Your rights

Under UK GDPR you can: access the personal data we hold about you, correct inaccurate data, request erasure, request a portable copy, and object to certain processing. Email support@tendlyhq.com to exercise any of these. You can also complain to the Information Commissioner's Office ( ico.org.uk) if you believe we've mishandled your data.

Children

Tendly is not directed at, and is not intended for use by, anyone under 13. We do not knowingly collect account data from children. (This is distinct from the fact that a user's recorded contacts may include minors — see above.)

Changes to this policy

We'll update the date at the top when we make material changes, and notify you in-app where required.