Effective

Ελληνικά

Privacy Policy

Daidra is engineering software for building systems, calculations, technical documents and project planning. We collect the data needed to run your account and your projects, we do not sell personal data, and we use Google user data only to provide the calendar features you turn on.

1.Who we are

Daidra ("we", "us") operates daidra.eu, app.daidra.eu (Studio), docs.daidra.eu, status.daidra.eu, the client portal and the Daidra Field mobile app (together, the "Service"). We are the controller of the personal data described in this policy, except where we process data on behalf of our customers (see "Data you enter about other people").

For any privacy question or request, contact us at privacy@daidra.eu.

2.Data we collect

Account data
Name, email address, password (stored only as a salted hash), profile photo, profession, organisation, language and display preferences. If you sign in with Google or GitHub, we receive your name, email address and profile image from that provider.
Workspace content
Everything you create or upload: projects, building models, engineering calculations, compliance and technical documents, files and photos, tasks, calendar events, equipment, finance records, and the clients, contacts, properties and staff you add.
Google Calendar data
Only if you connect Google Calendar. See "Google user data" below.
Device and usage data
IP address, browser and device type, pages requested, timestamps and error logs needed to operate and secure the Service. If you use Daidra Field, we store a push-notification token for your device.
Payment data
If you subscribe, payments are handled by Stripe. We receive the subscription status, plan and billing details Stripe returns; we never receive or store full card numbers.
Communications
Messages you send us and transactional emails we send you, such as verification, password reset, invitations and notifications.

3.How we use data

  • Provide the Service: accounts, projects, calculations, document generation, file storage, planning and the client portal.
  • Synchronise your planning with Google Calendar when you connect it.
  • Send transactional emails and, in Daidra Field, push notifications you have enabled.
  • Process subscriptions and invoices.
  • Keep the Service secure and reliable: authentication, abuse prevention, monitoring and troubleshooting.
  • Understand aggregate website usage, only within the consent limits described under "Cookies and analytics".
  • Meet legal, tax and accounting obligations.

We do not sell personal data and we do not use your workspace content or Google user data for advertising.

5.Google user data

Connecting Google Calendar is optional. When you connect it from your account settings, you grant access to the Google Calendar scope (https://www.googleapis.com/auth/calendar) together with your basic Google identity (openid, email).

What we access
Your calendar list and the events, times, attendees and responses, reminders, recurrence, descriptions, locations, visibility and colours on the calendars you select for synchronisation, plus your Google account email address to identify the connection.
How we use it
Only to provide two-way synchronisation between your Daidra planning and the calendars you choose: importing Google events, writing Daidra events and changes back to Google, detecting conflicts for your review, and receiving Google change notifications so that updates arrive promptly.
How we store it
Access and refresh tokens are encrypted at rest. Synchronised events are stored in your Daidra workspace, in the same database as the rest of your content.
Sharing
We do not sell Google user data, use it for advertising, or transfer it to third parties except to the infrastructure providers that host the Service, as necessary to provide the feature, or when required by law.
Human access
No person at Daidra reads your Google user data unless you ask us to for support, it is needed for security purposes such as investigating abuse, or it is required by law.
AI models
We do not use Google user data to develop, improve or train generalised artificial-intelligence or machine-learning models.
Disconnecting
You can disconnect Google Calendar at any time from your account settings, which stops synchronisation and removes the stored tokens. You can also revoke access from your Google Account under Security, Third-party apps with account access.

Daidra's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6.Data you enter about other people

When you add clients, property owners, contacts, staff or project participants, or share documents through the client portal, you decide what data is entered and why. For that data you act as the controller and we process it on your behalf to provide the Service. You are responsible for having a lawful basis and for informing those people where required.

7.Service providers

We use the following providers to run the Service. Each receives only the data it needs for its function:

Vercel
Website and application hosting, file delivery, privacy-friendly usage and performance measurement.
Supabase
Database and file storage.
Google
Optional sign-in, Google Calendar synchronisation, address geocoding and, where enabled, Google Analytics.
GitHub
Optional sign-in.
Stripe
Subscription payments and invoicing.
Resend
Transactional email delivery.
Expo
Push-notification delivery to the Daidra Field app.
Geoapify
Address search and geocoding for project locations.

Some background processing, such as calendar synchronisation and document preparation, runs on servers operated by Daidra. We may also disclose data when required by law or to protect the rights and safety of our users.

8.International transfers

Some providers process data outside the European Economic Area, for example in the United States. Where this happens we rely on an adequacy decision, such as the EU-U.S. Data Privacy Framework, or on Standard Contractual Clauses approved by the European Commission.

9.Retention

  • Account data and workspace content are kept while your account is active.
  • When you ask us to delete your account, we delete or anonymise your personal data within 30 days, except where we must keep it longer by law.
  • Invoices and accounting records are kept for the period required by applicable tax law.
  • Operational and security logs are kept for a limited period and then deleted.
  • Google tokens are deleted as soon as you disconnect Google Calendar.

10.Security

We protect data with encrypted connections (TLS), encryption of third-party access tokens, verified database connections, access controls and least-privilege infrastructure. No system is completely secure; if a breach affects your personal data, we will notify you and the competent authority as the law requires.

11.Cookies and analytics

  • Essential cookies keep you signed in, protect forms and remember client-portal access links. The Service cannot work without them.
  • Preference storage remembers choices such as the colour theme.
  • Vercel Web Analytics and Speed Insights measure aggregate usage and performance without cookies.
  • Google Analytics, where enabled, runs in Consent Mode with analytics and advertising storage denied by default. No analytics or advertising cookies are set unless you give consent.

12.Your rights

You have the right to access, correct, delete or export your personal data, to restrict or object to its processing, and to withdraw consent at any time without affecting earlier processing. To exercise these rights, email privacy@daidra.eu. We respond within one month.

You also have the right to lodge a complaint with a supervisory authority. In Greece this is the Hellenic Data Protection Authority (www.dpa.gr).

13.Children

The Service is intended for professionals and is not directed to children under 16. We do not knowingly collect their personal data.

14.Changes to this policy

We will update this page when our practices change and revise the effective date above. If a change is significant, we will notify signed-in users before it takes effect.