Privacy Policy

This policy explains what MACRILON collects, why, and your choices. We design for data minimization: your network plats and designs are your data; we process them only to produce your deliverables.

What we collect

• Account data — username/email, role, tenant, hashed password (PBKDF2; never plaintext).
• Customer content — KMZ/plat/roster files you upload and the design packages generated from them.
• Usage + security logs — login events, actions, timestamps (the append-only audit log), IP for abuse prevention.
• A session cookie (macrilon_sess) strictly to keep you signed in (expires in 12 hours). No third-party ad/tracking cookies.

How we use it

To authenticate you, generate and store your design deliverables, maintain security/audit, and provide support. We do not sell your data or use customer content to train models for other customers.

Tenant isolation & sharing

Each customer's data is isolated to its tenant. We share data only with subprocessors strictly required to operate the service — cloud infrastructure hosting and email delivery — under contract; a current list is available on request, or where disclosure is legally required.

Retention & your rights

We retain customer content for the life of your account plus 30 days, then delete on request. For Field app captures, the project-record retention terms in the Macrilon Field app section below apply instead of this account-based period. You may request access, export, correction, or deletion of your data (GDPR/CCPA) through our contact form.

Security

Encryption in transit (TLS). A SOC 2 readiness program is underway (we are not yet SOC 2 certified and do not claim to be), and managed-cloud hosting with encryption at rest is on our roadmap. For current posture see our Security & Trust page.

Macrilon Field app

The Macrilon Field App (“the app”) is operated and published on the App Store by TEAM Corp (Telecommunications Engineering And Architecture Management, LLC; “we”, “us”). It is the field app for the Macrilon platform, used by crews working on utility pole and fiber construction projects. This section is the app’s privacy policy; the rest of this page covers the Macrilon website and platform. The app also shows its policy inside the app; an older app version may show older wording, and this page is the current one.

The app is for people who already have a Macrilon account. We or your organization create accounts; you cannot sign up in the app.

What the app collects

• Account details. Your account email address or username, your role, and the organization your account belongs to. These are used to sign you in and to show you only your organization's jobs.
• Photos you take. Photos of poles and work sites that you take in the app for a job you select, along with technical details stored in the photo file (for example camera settings and the location where the photo was taken). Photos can show whatever is in view, so please avoid photographing people or private property you don't need.
• Precise location. Your device's GPS position and its accuracy when you take a photo and when you save a capture. If you move a pin by hand, we keep both the pin and the GPS position.
• LiDAR ruler measurements (from version 1.0.1). On iPhone and iPad models with a LiDAR sensor, the Ruler uses the camera, the motion sensors and the depth sensor on your device to place height reference marks on a pole. When you save a photo taken with the Ruler, we receive and store with that photo: the reference marks' heights and their positions in the photo, the direction to the pole, and the phone-to-pole distance measured with the depth sensor. Ruler 1.1 (from version 1.0.2, only on accounts where we have turned it on) also sends a measurement record with that photo: the depth map and depth-confidence map of the one camera frame taken when you tapped the base of the pole (about 0.35 MB), small photos of the ground where you tapped (up to 384 x 384 pixels each), the camera's position and direction for the views the Ruler used (relative to the phone's starting point, not a map position), how accurate iOS reported your location to be (not the location itself), your device model, your answer to the Ruler's question about the ground, and the Ruler's results for that photo, such as where it placed the marks. We use them to check and calibrate Ruler measurements. From web version v117 (app build 94), with a photo taken with the Ruler we also store how the Ruler judged the base reading it used: its straight-line distance from the phone, the phone's height above it, how many depth readings around the tap supported it and how many of those the iPhone rated high confidence, which limits were applied, and how many base taps it refused on that screen (the reasons for the last ten), plus how many base taps had no depth reading and how many lean taps it refused. These are kept with the photo like the rest of the capture and are used only to check whether Ruler heights can be trusted; nothing from a Ruler screen you cancel is kept or sent. From app version 1.0.6 (build 113), a Ruler photo (not Ruler 1.1) also carries a record of the base taps you made on that Ruler screen, whether the Ruler accepted them or not. For each of the last ten base taps it records where you tapped and when (counted from when the Ruler opened), what the depth sensor saw there (how many readings, their distances and how confident the iPhone was in them), the Ruler's own checks of the tap, the camera's position, direction and lens settings when you tapped and when you took the photo (positions are measured from where the Ruler started, not a map position), the shape of the ground the phone measured near the tap, and, where the phone detected a level surface under the tap, that surface's position, size, how long it had been tracked and the type iOS gave it (floor, table, seat or other). The record also says how many base taps you made in all, your phone model, when the phone's tracking was lost or reset, and how hard the phone was working (its heat level and the Ruler's processing times). For up to four of these taps (the one that placed the base and the latest ones) it can also include a small patch of the depth map and depth-confidence map around the point you tapped (64 x 64 readings, about 20 KB) and a small photo of the ground there (up to about 320 x 320 pixels), but only as many as keep the whole record within 100 KB; the rest are left out. The record is sent only as part of the photo's own upload (it waits with the photo if you are offline); if you cancel the Ruler screen, or discard the photo instead of saving it, the record is not sent. We use it only to check and improve how the Ruler finds the base of a pole; it does not change the heights shown to you, and the rest of the depth map of these taps is not sent. Also from app version 1.0.6 (build 113), after one of these Ruler photos where you placed the base, the app may ask you to tap the photo where the pole meets the ground. With that photo we store your answer (where you tapped, or that you chose Base hidden or Skip, that the question closed by itself, or that you left the app), how long the question was on screen, where the Ruler's own base is in the photo and, if you tapped, how it compared with your tap. If the question is not shown (for example, for a photo taken sideways), we store that it was not asked and why. No extra image is sent for this. We use it only to check and improve height accuracy; it does not change the heights shown to you. We do not upload continuous depth streams or 3D meshes. Apart from the ground shape and detected-surface information described above for each base tap kept in the record, we do not upload planes or scene classifications, and we do not use depth data to identify you or anyone else. The Sensor check shows depth readings on your device without sending them.
• Camera geometry of photos (from web version v112; the iPhone values need an iPhone app version that supports them). Where your phone supports it, the app stores with a photo the camera and motion geometry that is available for it: the phone's tilt and orientation, the camera's lens parameters (such as its focal length in pixels, the image size and the zoom) and the phone model; and, for a photo taken with the Ruler on an iPhone with LiDAR, the estimated distance to the base of the pole you placed. From web version v113, on supported iPhone app versions and iPhones, eligible whole-pole photos may be taken with Apple's ARKit camera. When available, we store with the photo an estimated horizontal distance and range from the phone to a candidate point on the ground near the bottom of the frame guide, how it was found and the camera's tracking status, with the camera geometry described here; this is not the distance to the pole. From web version v124 (app build 100), the GROUND mark of the whole-pole frame guide is where you line up the base of the pole: we also store the ground point the AR camera measured under that mark (its position in the saved photo and relative to the camera, its horizontal distance from the phone, how it was found, the depth confidence, the tracking status and whether the GROUND mark showed green when you pressed), or that no ground was found there and why. The AR camera's view of the surroundings (detected surfaces, feature points and depth) is used on the phone to find that point and is not uploaded (from web version v116, on an iPhone with LiDAR, the depth of the one measured frame is stored as described below). From web version v114, on supported iPhones with LiDAR and only once we turn it on, a whole-pole photo may be taken by the regular full-size camera right after the AR camera measured the ground on the same press; we then store with the photo the phone's estimated height above that ground (not a distance), timing and motion summaries used to check the phone was held still (such as how long the hand-off took, how far and how fast the phone turned, its peak acceleration and its estimated vertical speed), and the camera geometry described here. The AR camera's images and the individual motion samples behind those summaries stay on the phone and are discarded (from web version v116, the depth of the one measured frame is stored as described next). From web version v116, on supported iPhone app versions, the app also stores with a photo the camera settings the phone recorded for it (exposure time, ISO sensitivity, exposure adjustment, white balance, focus setting and lens position, whether distortion correction was on, and the camera's type and identifier, which identifies the camera, not you), the iPhone model and its iOS version, the app's build number and web version (from web version v117), the compass direction iPhone reports for the phone (true and magnetic, with iPhone's own accuracy estimate; it is the direction of a fixed axis of the phone, not necessarily the direction the camera was pointing, and it is a note for the office, not a measurement of the pole), and, only if you have already allowed the app to use your location, the phone's own location reading at that moment with its accuracy, altitude, course and speed, and whether iPhone marked that reading as simulated by software or as coming from an external accessory (the app never asks for location for this). For a photo taken with the AR camera or the Pro camera on an iPhone with LiDAR, we also store the depth map and depth-confidence map of the one camera frame used for the measurement (a 256 x 192 grid of distances, no colour), with that frame's camera position and lens parameters, as a separate record linked to the photo (about 330 KB, sent with the photo, also when iPhone's Low Data Mode is on); people, vehicles or buildings in view appear in it as distances, as they do in the photo. For the phone's estimated height above the ground we also store a summary of the readings behind that estimate (how many ground readings were combined and how much they varied, a LiDAR cross-check and how steady the phone was). RAW copies. On web version v116 (app build 93) a tester could turn RAW on for one photo in Sensor check, and the app saved a RAW (DNG) copy of that photo on the phone; web version v117 (app build 94) saved none. From web version v118 (app build 95) a tester could turn RAW on for one full-size or Pro photo. From web version v121 (app build 98) a tester's full-size and Pro photos include a RAW copy by default, while we have RAW switched on for the service; the tester can turn this off (and on again) in Sensor check, and signing out turns it back on for the next sign-in (if the phone cannot save that change, the off setting can come back after the app is restarted; Sensor check always shows the current setting). From web version v124 (app build 100) this applies to every field account we have turned full-size photos and RAW on for (not only testers): its full-size and Pro photos include a RAW copy by default, and the account can turn it off (and on again) in Sensor check in the same way. The app skips the RAW copy, and still saves the photo, when the phone is hot or short of memory, when iOS reports less than about 2 GB of storage available for important data (if the phone does not report it, this check does not stop the RAW copy), or when more than 10 RAW copies are already held on the phone as the camera opens. When we switch it off, our server refuses new RAW uploads straight away; a phone may still take a RAW copy until it receives the updated setting or its current permission expires, and an upload already in progress may still complete. A RAW copy is the camera sensor's less-processed image of the same photo (about 25 to 75 MB), so it shows what the photo shows. It is kept inside the app's own storage on the phone for the account that took the photo, and is uploaded to us, for that account and job, after that photo's full-size copy has been sent (or after our server refused the full-size copy), never on an iPhone Low Data Mode network; from web version v124 (app build 100) it is also never sent over mobile (cellular) data or over a network the iPhone marks as expensive (which can include a personal hotspot), so it usually waits for Wi-Fi. The app deletes the copy from the phone once our server confirms it has stored exactly that file. A copy not yet sent is deleted from the phone when you sign out or another account signs in, when the photo it belongs to is discarded without being saved, and once it is 7 days old; the 7-day deletion happens the next time the app is opened after that, so a copy can stay longer if the app is not opened, and a copy deleted this way is not sent. Signing out asks iOS to cancel RAW uploads; an upload already in progress may still reach us. The app checks that each deletion actually removed the file and tries again on a later launch if it did not. Copies saved by app build 93 are never uploaded; they are only deleted as described above. Uploaded RAW copies are stored with the job like full-size photos, are available to our staff and service providers as needed to run the service, and are not included in customer-facing views, exports or reports. When available, the iPhone app uses a motion reading matched to the photo's capture time. Some values are approximate (for example, lens parameters worked out from the camera's field of view), and the regular camera does not measure any distance. A value that is not available is recorded as unavailable: in a web browser or on Android none of these iPhone camera and sensor readings are taken (photos, location and job details are still collected as described in this policy), and older app versions send none. These values are linked to your account and the job like the rest of the capture. We use them only to estimate pole heights for the job. Camera geometry is available to our staff and service providers as needed to run the service, but is not exposed in customer-facing views, exports or reports. The app asks for no extra permission for this. On accounts we use for testing, the Sensor check also shows the last photo's values on the phone; that display is not sent anywhere itself, but the same values are stored with the photo as described here.
• Job and pole details you enter. The job, pole number, pole tag, height, equipment, companies attached to the pole, flags, notes, and the reason a pole could not be reached. From web version v116 this includes the pole length and class you read off the pole's birthmark (the stamp on the pole), or that it could not be read. That length is the nominal length of the whole pole as made, not its height above the ground.
• Reports you send to the office. When your organization has field reports turned on, you can report a pole that is not in the job ("Add a pole here"), a pole that is somewhere else than recorded, a flag on a pole, or that your own work on the job is done. A report includes your account, the job, the pole it is about, your note and, for a new pole or a pole that is somewhere else, your location at that moment with its accuracy and a link to your saved photo of the pole. The office reviews each report; a report never changes the job's plan by itself.
• Times. When a photo was captured and when it was uploaded.
• Security and service records. Our servers record sign-ins and actions with your username and the time, and may record your IP address, to keep the service secure and to fix problems.

What the app does not collect

The app does not use your microphone or contacts, does not browse your photo library, does not track your location in the background, does not use push notifications, and does not use your advertising identifier. It contains no advertising or third-party analytics software, and we do not track you across other companies' apps or websites.

Permissions

• Camera: to take photos for a job.
• Location while using the app: to record where each photo was taken and to show your position on the job map.

You can turn these off in iPhone Settings at any time. Turning off Camera prevents new camera captures. Turning off Location prevents new device-location readings, and the app needs a location to save a capture.

Stored on your iPhone

If you lose signal while the app is open, captures wait in a queue inside the app and upload when the app is open and connected again. Each capture is removed from the queue after it uploads. The app also remembers your sign-in, the job you last picked and the company names you recently entered. On accounts with Ruler 1.1, the app also keeps its last 30 Ruler 1.1 results, with their photos, in its private storage on the phone for testing; they are not uploaded, and they leave the phone only if you share them. So you can check what you already shot, the app also keeps a small, reduced-size copy of each photo you take (about 320 pixels on its longest side), with its pole, photo type, time and upload state, in its private storage on the phone. You see only your own copies, for the job you have open, under More > On this phone. A copy is kept while its photo waits to upload and for 14 days after it uploads; the copies together are limited in size (about 12 MB, oldest uploaded first). Signing out removes all of the copies; it does not remove captures still waiting to upload. The copies are not uploaded and are not shared. Deleting the app removes its local capture queue, including captures that have not uploaded yet, and the copies; it does not delete uploaded records or your account.

How we use this information

• To add your photos, locations and pole details to your organization's job records, place them on the job map, and analyze the photos for the project (for example, whether the whole pole is in frame, what equipment is on the pole, and whether a pole needs work before new cables are attached). Photos are processed on computers we operate ourselves, and they are stored with our cloud hosting provider (Amazon Web Services, in the United States) as part of your organization's job records.
• To sign you in and keep each organization's data separate and secure.
• To support you, keep the service running and fix problems.

We do not sell your information and do not use it for advertising.

Where it is stored

Uploaded captures and account information are stored with Amazon Web Services in the United States, as part of your organization's job records.

Request access form

The sign-in page links to a Request access form. If you submit it, we store the information you enter to review and respond to your request. Submitting it does not create an account.

Who can see it

• Your organization. Authorized people on your organization's projects can see the captures you upload, including your username and the capture locations.
• Our team. Our staff and contractors who run, review and support the service.
• Service providers. Our cloud hosting and storage provider (Amazon Web Services) and our email delivery provider, used only to run the service and bound to protect the data at least as well as this policy does.
• Map imagery. When the job map or the pin map is open, your iPhone loads satellite imagery from Esri (ArcGIS Online), which receives your IP address and the map area being loaded.
• Navigate (Apple Maps or Google Maps). If you tap Navigate, we open your maps app (Apple Maps, or Google Maps if you chose it) with directions to the selected pole's coordinates. That app's provider receives those coordinates and network information such as your IP address, and handles your own location for the route under its own privacy policy. We do not send your pole label, job or account with it.
• Street View (Google Maps). If you tap Street View, we open Google Maps using the selected pole's coordinates, not your device's current GPS location. Google receives those coordinates and network information such as your IP address, and may associate the request with your Google account if you are signed in. Google's Privacy Policy applies.
• When the law requires it.

How long we keep it

Field captures (photos and everything stored with them, including Ruler measurements, Ruler 1.1 measurement records and camera geometry) are project records. We keep them for the life of your organization's project. Security and service records are kept only as long as needed to keep the service secure, fix problems and meet legal obligations, and are then deleted.

Deleting your account

You can ask us to delete your account from inside the app or by email. We process each request by hand and complete it within 30 days. Photos and pole details you uploaded stay with your organization's project records for the life of the project; we remove your name and account email from them, but the photos, locations and times remain. Details: Delete your account.

Your choices

You can ask us for a copy of your information, to correct it, or to delete your account. Email contact@macrilon.com from the address on your account.

Children

The app is a work tool for adults. It is not directed to children, and we do not knowingly collect information from children.

Contact

Privacy questions: reach us through our contact form or contact@macrilon.com.