Drawel

Drawel Privacy Policy

Effective 20 November 2026 · Version 1.2 · Previous version 1.1

This policy explains what personal data the Drawel app, web app and server process, why, for how long, and what rights you have. Drawel is a tool for electricians to produce as-built drawings, circuit schedules and commissioning inspection protocols on site.

1. Who is responsible for your data

The service provider is IoTera Oy, business ID 3454475-1, Tanhuankatu 63b, 33560 Tampere, Finland. For privacy and support matters, contact tuki@drawel.io. The person responsible is Janne Kaikkonen.

We process personal data in two roles:

Situation Controller Processor
User accounts and service security: email, name, sign-in, sessions, security logs, feedback, invitations IoTera Oy –
Data entered about sites and protocols: site address, customer name, photos, measurements, signatures, the electrician's company details The electrical contractor using Drawel (the customer) IoTera Oy

In the second case, the customer decides what data is collected and why. IoTera Oy processes it only on the customer's instructions. The processing terms (GDPR Article 28) are part of the Terms of Service, which you accept when creating an account. If you are a customer of an electrician or a signatory of a protocol and want to exercise your rights, contact the electrician's company first. We help them handle your request.

2. What data we process

Data Content Whose data
User account Email, name, password (stored only as a hash), acceptance of the Terms of Service (version and time) User
Organisation and members Organisation name, members (name, email, role: administrator or installer). The member list is visible to all members of the same organisation User
Invitations Invitee's email address, role, invitation status and expiry, and the name of the inviting administrator. The address is provided by the organisation's administrator, not by the invitee Invitee, inviter
Session data Sign-in session, the session's IP address and device or browser identifier (user agent) User
Contractor company details Company name, business ID, address, phone, email, Tukes registration, name of the electrical work manager, logo, and up to three contact persons (name, phone, email). These appear in the protocol PDF The contractor and its contacts
Site Site name and address, customer name (free text) The contractor's customer
Drawings and inspection data Background images, imported PDF backgrounds, drawings, distribution boards, circuits, measurements Site owner, indirectly (via the address)
Photos Photos, captions, timestamp and, if you grant location permission and take the photo with the app's camera, the GPS location of the shot Photographed site, photographer
Protocol Checklist answers, signatory name and role, signing time, optional signature image, the finished PDF Installer, electrical work manager, customer
Saved personal signature A signature image you drew or scanned. Visible only to you. The original scan is not stored User
Change log A record of who (name at the time of writing, and user ID) changed what. Visible to the other members of the organisation User
Feedback The text and type (bug, request, question, other) you send through the in-app feedback form, up to three screenshots or images, and device information: app and update version, platform, operating system, device model, screen, theme, language, the screen that was open, ID and name of the open site and drawing, sync status, and your name and organisation name. Device information does not include your email address, passwords, tokens or location. A screenshot may show customer data, so do not attach any unless needed The sender; possibly a customer shown in images
App updates When the app starts, it asks Expo's update service (u.expo.dev) whether a new version of the app's JavaScript code is available. The request carries the app's update identifier, platform (iOS or Android), runtime version and update channel. Because of the network connection, the service also sees the device's IP address. No account data, sites, photos or other content User
Technical logs API request logs (method, path, status, duration) without IP addresses or content. The reverse proxy has no access log, but its error log may contain an IP address. Sync service logs do not contain client IP addresses. Logs contain no passwords or file contents User

The app does not use advertising, analytics, tracking or third-party error reporting. Data is used only to run the service.

We do not knowingly process special categories of personal data (such as health data). Photos may incidentally show people; electricians are instructed to avoid photographing people. Location and device metadata (EXIF, including GPS) is removed from photo files in the app before upload. In addition, the server checks JPEG and PNG images uploaded by current app versions: an image containing location, device or free-text metadata is rejected and removed from storage, and only minor technical metadata (orientation, resolution, colour space, size) is allowed. The GPS location of a photo is kept only on the photo's data record for use in the app, not in the image file.

We receive data mostly from you or from the electrician who enters the site and protocol data. We receive an invitee's email address from the organisation's administrator. We do not obtain data from external registers.

3. Purposes and legal bases

Purpose Legal basis (GDPR Article 6)
Providing the service: sign-in, organisation memberships and invitations, syncing between devices and the server, producing images and PDFs Contract (1 b). For customer data, the customer's instructions to us as processor
Service emails: password reset and organisation invitations (section 5) Contract (1 b). For invitees, legitimate interest (1 f): an organisation administrator wants to invite a colleague to use the service
Storing inspection documentation (protocols, drawings, photos) for the customer The customer (controller) decides the basis. We process the data as processor on the customer's instructions
Handling feedback and improving the service based on it Contract (1 b) and legitimate interest (1 f)
Security, abuse prevention, rate limiting and troubleshooting (logs) Legitimate interest (1 f): security and reliability of the service
Contacting you about support requests Contract (1 b) or legitimate interest (1 f)
Proving acceptance of the Terms of Service Legitimate interest (1 f)

We do not make automated decisions or profile users. The electrician is responsible for the contents of the protocol and for interpreting measurement results.

4. Where data is stored

Data Location
Database, application server and sync service Amazon Web Services (AWS), region eu-north-1, Stockholm, Sweden
Photos, background images, PDFs, logos, feedback images AWS S3, eu-north-1, Sweden. Private: files are reachable only through short-lived signed links
Database backups AWS S3, eu-north-1, Sweden, in separate storage. Encrypted before upload
Your device Local database and files on the device (offline use). Cleared when you sign out or delete your account

Pilot exception. Drawel is in a pilot phase. During the pilot, all data and backups are in Sweden, within the EU, but not in Finland. We intend to move production to Finland before the service is sold to paying customers. This policy will then be updated, and old pilot data will be moved or deleted.

5. Recipients and sub-processors

We do not sell data or disclose it for marketing. We use the following providers:

Provider Purpose Data
Amazon Web Services EMEA SARL (Luxembourg, EU) Server (EC2), file storage and backups (S3), region eu-north-1, Sweden All data stored on the server
Amazon Web Services EMEA SARL (Luxembourg, EU) Email delivery (Amazon SES), region eu-north-1, Stockholm. The sender address is noreply@drawel.io Recipient email address and message content (see below)
Let's Encrypt (Internet Security Research Group) TLS certificates Only the service's domain names, no personal data
Expo (650 Industries, Inc., USA) App updates (u.expo.dev) Only the update-check data described in section 2, and the IP address. No user content
Apple (App Store Connect, TestFlight) and Google (Google Play) Distributing the app to testers and users App store account data is processed under Apple's and Google's own terms, and they are independent controllers for it

Emails the service sends

The server sends email through Amazon SES from noreply@drawel.io. Emails are sent only to operate the service:

The data used for these messages is the recipient's email address and name (if known) and the message content. AWS acts as processor and delivers the message. We send no marketing or newsletter emails, and messages contain no tracking pixels.

In addition, for each feedback submission the server sends a notification to IoTera Oy's own mailbox (feedback text, type, device information, sender and organisation name, number of images). The notification contains no images or image links.

No other third-party services are used: the app and the server do not send data to analytics, advertising or error-tracking services. If external uptime monitoring (e.g. Healthchecks.io) is used, it only learns that a backup or check succeeded, not any personal data.

A protocol PDF, a quantity CSV or a shopping-cart Excel file is passed on only when the electrician shares it through the phone's share menu (e.g. by email to a customer or a wholesaler). The recipient and channel are then the electrician's choice.

The AWS Data Processing Addendum (DPA) is part of the AWS service terms.

6. Transfers outside the EU/EEA

User account and site data is not stored outside the EU or EEA. Any transfers outside the EU rely on a transfer mechanism under Chapter V of the GDPR, such as the EU Standard Contractual Clauses (SCC).

AWS's service provider in the EU is Amazon Web Services EMEA SARL, but its parent company, Amazon.com, Inc., is a US company. For that reason, a US authority could in theory be entitled under US law (e.g. the CLOUD Act) to demand access to data located in the EU. We have knowingly accepted this risk for the pilot phase.

The provider of the update service, 650 Industries, Inc. (Expo), is a US company, so update-check data (section 2) is transferred outside the EU. Apple and Google may process app store account data outside the EU under their own terms.

7. How long data is kept

Data Retention
User account, organisation, sites, drawings, photos, protocols Until the account is deleted (section 9) or the customer deletes the data. The customer can delete individual photos and sites in the app
Archived site On the server for 2 years from archiving, then deleted (manually during the pilot)
Signed protocol As part of the site until the site or the account is deleted. A signed protocol cannot be changed; a change is made as a new version. We do not retain protocols on the electrician's behalf to meet their own statutory retention duties: the electrician is responsible for their own archiving and can export the PDFs from the app before the site or account is archived or deleted. Deleting the account also deletes the protocols
When a member leaves an organisation The member's account, sessions and saved signature are removed from the organisation, but the organisation's data stays with the organisation. In protocols that are already signed, the signatory's name and signature remain as part of the immutable document
Invitations A used, cancelled or expired invitation is kept as a record until the organisation or the inviting administrator's account is deleted
Feedback and its images Until the sender's account is deleted. Deleting the account deletes the sender's feedback and its images. The email notification about the feedback (section 5) sits in IoTera Oy's mailbox and is not deleted automatically when an account is deleted
Deleted photo or background image From the server right after syncing (usually within seconds). Image files are not backed up
Session data (IP address, device) A session is valid for 7 days and renews while you use the app. It is removed on sign-out and on account deletion; expired sessions are deleted daily. The sync access token is valid for 15 minutes
Service logs Short: logs are rotated automatically, so retention depends on traffic. Logs are not sent to any external service
Database backups Full backup weekly, differential backup on weekdays, and continuous change log. Expired versions are removed within 30 days. After an account is deleted, the deleted data may remain in backups for up to about 2 months and is used only to restore the service after a failure. If the service is restored, deleted accounts are deleted again
PDFs exported or shared outside the app These are not on our servers and cannot be deleted when an account is deleted

8. Your rights

You have the right to:

Requests:

9. Deleting your account

In the app: Settings, Delete account. You enter your password and confirm. Deleting the account requires a network connection.

The server immediately and irreversibly deletes your account, sessions, saved signature, and your feedback with its images. If you are the only member of your organisation, it also deletes the organisation, all sites, drawings, photos, measurements and signed protocols, and all stored files. There is no grace period and deletion cannot be undone. Export the PDFs you need before deleting. PDFs exported or shared outside the app are not affected. A local copy on your other devices is removed when you sign out there. Deleted data remains in backups for the period described in section 7.

If the organisation has other members, its data stays with them. The last administrator cannot delete their account until they name another administrator or remove the other members.

Deletion request without the app

If you cannot use the app (you have not installed it, have removed it, or cannot sign in), you can request deletion of your account and related data by email to tuki@drawel.io. Use the subject "Account deletion" and tell us the email address of the account. We may ask you to verify your identity (e.g. by replying from the account's email address) so that an account is not deleted at a third party's request. We delete the data to the same extent as in the app within 14 days and confirm by email.

10. Security

We notify customers of a personal data breach without undue delay and within 48 hours of detecting it, so that they can meet their own 72-hour duty to notify the supervisory authority. Where we are the controller (user accounts), we notify the supervisory authority within 72 hours of becoming aware of the breach, unless it is unlikely to result in a risk to individuals' rights. If a breach is likely to result in a high risk to users, we notify them without undue delay.

11. Cookies and tracking

The app stores your sign-in session in the device's secure storage. The web app (app.drawel.io) uses a session cookie needed for sign-in and the browser's local storage (e.g. an unsent feedback draft). These are strictly necessary for the service. We use no advertising or analytics cookies and no other tracking. This website (drawel.io) sets no cookies. Permissions the app requests (camera, photos, location) are used only to take photos and attach them to a site.

12. Changes to this policy

We update this policy when processing changes (for example when production moves to Finland or sub-processors change). The current version and date are at the top of this page. We announce significant changes with a notice in the app.

13. Contact

IoTera Oy
Business ID: 3454475-1
Tanhuankatu 63b, 33560 Tampere, Finland
Email: tuki@drawel.io