Cookie Policy of Accord.ia
Last updated: 8 July 2026 Version: 1.0
1. Controller
The controller is Accord.ia.
- Website: https://accordia.tech
- Privacy and cookie contact: support@accordia.tech, using the subject line "Privacy Request"
- General contact: support@accordia.tech
2. What cookies and similar technologies are
Cookies are small files or data portions stored in the user's browser. Similar technologies include local storage, session storage, pixels, mobile SDKs, device identifiers, push tokens, analytics tools, session replay, technical logs, limited security fingerprinting and other identifiers.
Accord.ia uses these technologies to operate the Platform, maintain sessions, protect accounts and payments, remember preferences, measure performance, improve the product, display maps, send communications, prevent abuse and, only where permitted, carry out analytics, marketing or personalisation.
3. Scope of this policy
This policy applies to the public Accord.ia website, authenticated web app, mobile app, legal pages, pricing, waitlist, newsletter and contact forms, marketplace features, chat, Orders, payments, notifications, maps, ranking and support, and SDKs or libraries integrated in browser or mobile app environments.
4. Categories of technologies used
4.1 Technical or strictly necessary technologies
These are needed to provide a service requested by the user or protect the Platform. They may include session and authentication cookies, tokens for login, role and security state, storage for essential preferences such as language, theme or cookie choices, anti-CSRF tokens, rate limits, bot protection and security, technical checkout and payment redirects, essential diagnostics, real-time room tokens, mobile device permissions and secure local storage for session or app settings.
These technologies do not require consent where strictly necessary. Blocking them may prevent some functions from working.
4.2 Preferences and functionality
These technologies remember user choices or improve experience, such as language, theme, layout, filters, notification preferences, dashboard preferences or app settings. Where they are not strictly necessary, they may be activated on consent or another valid basis.
4.3 Analytics and product measurement
These technologies help understand how users use the website, web app and mobile app and improve funnels, performance, conversions, stability and UX. The technical documentation indicates possible tools such as Amplitude and experiment/analytics tools. Non-essential analytics must only be activated after consent unless the configuration is genuinely anonymous, aggregated or exempt under applicable law.
4.4 Diagnostics, crash reporting and observability
These technologies identify errors, crashes, degraded performance and security issues. The technical documentation indicates tools such as Sentry. Strictly technical diagnostics may rely on legitimate interest where minimised and necessary for security or stability. Invasive features such as session replay or detailed session recording must be enabled only after consent where required and with masking of sensitive fields.
4.5 Session replay
Session replay may reconstruct user interactions with pages or apps to understand bugs and UX issues. It is potentially intrusive and must be configured with masking, exclusion of sensitive fields, limited retention and activation only after consent unless a different legal basis is expressly validated.
4.6 Marketing, newsletter and CRM
These technologies support newsletters, waitlists, campaigns, segments, preferences, contact forms and promotional communications. The technical documentation indicates possible integrations with Brevo. They are activated only after consent or another legal basis allowed by law.
4.7 Maps and location
The Platform may use Mapbox or equivalent services to display maps, places, distance, service areas and location. The mobile app or browser may request geolocation permissions. Precise location is used only where the user grants permission and can be revoked from browser or device settings.
4.8 Payments and checkout
The Payment Provider, for example Stripe where active, may use cookies and similar technologies to complete payments, prevent fraud, manage payment methods, checkout, strong customer authentication and security. These technologies may be necessary for the payment function requested by the user.
4.9 Bot protection and security
Accord.ia may use services such as Cloudflare Turnstile or equivalent tools to distinguish real users from bots and prevent spam, abuse, attacks and fraud. These technologies may process IP address, user agent, technical signals and verification tokens. Where used exclusively for security and abuse prevention, they may be considered necessary.
4.10 Mobile SDKs, notifications and device identifiers
In the mobile app, Accord.ia may use SDKs, secure storage, push tokens, app identifiers, device permissions, crash reporting, analytics, app updates, maps, document scanning, payments and real-time communication.
Operational notifications, such as security, Order, chat and payment notifications, are functional to the service. Promotional notifications require consent or equivalent settings. Users may manage authorisations, tracking, notifications, location, camera, microphone and files from operating-system settings.
4.11 AI, real-time communication and transcription
Call, transcription, analysis and reporting features may use technical tokens, room identifiers, quality logs, microphone, camera, audio, transcripts and AI systems. These are not always cookies, but they are similar technologies relevant to transparency. Transcripts, recordings or call analysis must be activated only with clear information and, where necessary, participant consent.
5. Inventory of cookie and technology categories
The Platform keeps the operational list of cookies and technologies updated in the banner or preference centre available on the site or in app settings. The categories currently expected are:
| Category | Purpose | Examples of providers or technology | Consent |
|---|---|---|---|
| Necessary | security, page loading, essential preferences, forms, session and abuse prevention | Accord.ia, Cloudflare, Turnstile, Supabase/Auth, session tools | No, if strictly necessary |
| Payments | checkout, payment authentication, fraud prevention, reconciliation and refunds | Stripe or equivalent provider | No, if necessary for the payment requested |
| Preferences | language, country, displayed currency, theme, cookie choices and account preferences | Accord.ia and preference centre | No when needed to remember a requested choice; otherwise yes |
| Analytics | measurement of pages, funnels, events and product performance | Amplitude or equivalent tools | Yes, unless a genuinely exempt configuration applies |
| Diagnostics | errors, crashes, security, performance and stability | Sentry or equivalent tools | No for minimised essential diagnostics; yes for session replay or invasive functions |
| Marketing and CRM | newsletter, waiting list, campaigns, segments and promotional communications | Brevo or equivalent tools | Yes, unless another legal basis is permitted by law |
| Maps and location | maps, geocoding, distance and service areas | Mapbox or equivalent tools | Depends on the function; precise location requires browser or device permission |
| Realtime and AI | calls, audio/video quality, transcripts, summaries and AI assistance | LiveKit, Cloudflare AI or equivalent services | Depends on the function; recording, transcription or analysis requires specific information and consent where necessary |
The list may change according to environment, geographic area, device, consent choices and features used.
6. Consent management
Where the website or app uses cookies or technologies that are not strictly necessary, Accord.ia must collect consent before activation.
The banner or consent-management platform must allow the user to accept all non-essential cookies, reject all non-essential cookies, manage preferences by category, read this Cookie Policy and the Privacy Policy, and easily change or withdraw consent through the footer, privacy settings or a dedicated panel.
Refusing non-essential cookies must not block essential features, except where a technology is necessary for the specific feature requested by the user.
7. Public website
The public website may use technical cookies for security, language, preferences, banner and forms, anti-bot tools for waitlist, newsletter or contact forms, CRM/newsletter tools to collect leads and consent, analytics and session replay only if consented, Sentry or equivalent tools for errors and performance, and links to legal pages, pricing, FAQs and marketing content. Non-essential technologies must be blocked until valid consent is obtained.
8. Authenticated web app
The web app may use session cookies or tokens, user preferences, security and rate-limit tools, logout controls, payment integrations, chat, attachments, notifications and Orders, product analytics and session replay only if consented or genuinely exempt, maps and location where requested, and AI or real-time tools according to the feature used. Authentication does not remove the need to obtain consent for non-essential trackers.
9. Mobile app
In the mobile app, technologies similar to cookies include SDKs, secure storage, push tokens, app identifiers, device permissions, analytics, crash reporting and update tools. Accord.ia must provide privacy settings or consent for non-essential analytics, marketing and promotional notifications, session replay or invasive technical recordings, advertising tracking or identifiers if ever activated, precise location under operating-system permissions, and call transcription, recording or reports where required.
10. Changing preferences
Users may change cookie preferences through the "Cookie preferences" link in the website footer, privacy settings in the web app, mobile app settings, browser deletion of cookies and site data, or device settings for permissions, notifications, tracking and location. Withdrawal of consent does not affect processing lawfully carried out before withdrawal.
11. Disabling cookies in the browser
Users can configure their browser to block or delete cookies. Settings vary by browser. Blocking technical cookies may prevent login, security, checkout, preferences or other essential functions. For mobile technologies, users should use device and app settings.
12. Updates to this Cookie Policy
Accord.ia may update this Cookie Policy when technologies, providers, purposes, legal requirements or consent mechanisms change. In case of material changes to non-essential cookies, Accord.ia must update the banner/CMP and, where necessary, request consent again.
13. Contact
For questions about cookies and similar technologies, write to support@accordia.tech. For privacy requests, use the subject line "Privacy Request".