Privacy
Privacy policy
This policy describes how CommonSilo LLC ("CommonSilo") handles information when a shipyard uses the subscription. The service stores dock records: the berth a ship occupies, the dock-in and undock hours, the work still open on that ship when she leaves, the disputes about those hours, and the names of the people who sign the record. It is written for shipyard planners and the yard desks that keep those records. It is not a general notice about an unrelated product.
Who we are
CommonSilo provides subscription software for planning dry-dock stays. The company was founded in 2026. This policy does not describe a place of business, and it does not ask you to send paper to an office. Questions about privacy go only to support@commonsilo.com. There is no second address.
When this policy says "the yard," it means the shipyard that holds the subscription. When it says "the planner," it means a person the yard allows to open and revise dock records. Workshop leads, dockmasters, and owners' superintendents appear because the yard puts them on a signature row or a dispute line.
Dock records we store
The body of the service is the dock record. A record may contain a vessel name, a berth identifier, dock-in and undock times, a list of work that is still open at undock, margin notes, and the history of changes to that window. Workshop users write unfinished items back onto the same record. Those items may describe equipment, frame ranges, surveys, and coatings. They are yard operational records. They may name a ship or a person responsible for the job.
A worked record such as DS-184 for M/V Harting on Berth 2 shows the kind of fields involved: a dock-in hour, a revised undock hour, an earlier hour someone asked for, and open items such as sea chest grids, a rudder stock survey, and a boot-top coating. Those names in our public pages are illustrations. A live yard's records contain that yard's own ships and jobs.
We store the record as one slip. We do not split the unfinished work onto a separate master list that the workshop can edit without the planner. If an export is made, the export is a copy. The copy is not a second system of record inside CommonSilo.
Dispute timeline
When someone contests an hour, we store the earlier hour, the hour they asked for, the reason they gave, the time of the entry, and the name and role of the person who wrote it. We keep rejected hours as well as accepted ones, because the record is meant to show the argument, not only the final tide. Deleting an asked hour would hide the dispute the signature table is there to show.
A dispute entry is part of the dock record. It is not a private message channel. People the yard has allowed onto that record can read it. People at another yard cannot.
Accounts and signatures
When a yard opens a planner account, we collect the planner's name, the yard name the planner gives us, the email address used to sign in, a password the account holder sets, and the role they use on a docking. Roles we store are planner, workshop lead, dockmaster, and superintendent. We do not ask for a home address.
A signature row stores the name, the role, what was signed, the time, and whether the row is signed, unsigned, or limited to the dispute. What was signed may be the dock window, the dock-in, the open items, the flood-up, or only the dispute. We do not collect a handwritten biometric template. A signature in this service is an authenticated action by a logged-in person, stored as a row on the record.
The yard decides who receives an account. A shared password on a shop-floor terminal is information the yard has chosen to expose. Actions taken with that account are stored on the timeline under that account until the yard asks us to close it.
Record count and billing
We store the monthly count of dock records that were opened, revised, signed, or closed, the identifiers of those records, the rate applied, the floor of eight records, and the resulting amount. A record edited several times in one month is stored once on that month's count. A long stay may appear on more than one month if a qualifying action happens in each of those months.
Payment card numbers are handled by the payment provider we use. We store a provider reference, the last four digits if the provider returns them, the billing name the yard submits, and the status of the invoice. We do not store a full card number on the dock record, and we do not place card data in the margin of a slip.
Yard desk messages
If you write to the yard desk through the site, we keep the planner name, the yard name, the berth you mention, the reply address, and the note you send. That note is correspondence with support@commonsilo.com. It is not added to a dock record unless a planner later puts it there. If you apply for a role, we keep the message long enough to read it and reply.
Technical logs
Servers that host the service record IP address, browser type, time, and the page or API path requested. API logs may include the record identifier and the action, such as a window change, an open item, a signature, an export, or a record-count read. Logs are used to keep the service reliable and to investigate misuse. They are not a product we sell, and they are not attached to the undock packet.
Cookies and similar storage
The public pages of this site do not set an advertising cookie and do not run a third-party advertising tag. They do load typefaces from a font provider and a styling script from a content delivery network. Those providers receive the technical data their networks normally log, including IP address and user agent, when your browser requests the file.
When a planner uses the subscription itself, the service keeps the session with a strictly necessary cookie or an equivalent bearer token stored by the browser. That storage exists so the account stays signed in and so a signature can be tied to the person who made it. You can clear cookies in the browser. Clearing them will sign the account out. It will not delete the dock record.
We do not use cookies to build a profile of ships for anyone other than the yard that owns the records.
How we use information
We use dock records to show the planner, the workshop, the dockmaster, and the superintendent the same slip. We use them to show the dispute timeline and the signature table, and to export the berth copy, the undock packet, the ledger line, and the machine-readable copy. We use the record count to invoice the subscription. We use yard-desk messages to answer the note. We use account data to authenticate users, to reset access when the account holder asks, and to prevent an unsigned flood-up from being marked signed by the wrong role.
We use logs to debug a failed export or a disputed count. We use billing records to collect the monthly amount and to correct an invoice that names the wrong record. We do not use dock records to train a public model. We do not sell yard records. We do not use them to advertise a third party's product.
Who can see a record
Inside a yard, visibility follows the accounts the yard has opened. A workshop lead who can write an open item can read the ship that item belongs to. A superintendent who has signed a dispute can read the timeline of that dispute. We do not operate a directory of ships that other yards can search. Access by someone outside the yard happens only when the yard exports a copy and sends it themselves, or when applicable law requires a disclosure as described below.
Sharing with providers
We share information with infrastructure providers that host the application, the database, and backups, in the regions where those providers operate. We share payment data needed to collect the subscription with a payment provider. We share the contents of a message with an email provider that delivers mail from support@commonsilo.com. We may share a specific invoice or a specific record with a professional adviser when we need accounting or legal advice about that invoice or record, and only to the extent of that advice.
We may disclose a record to a public authority when applicable law requires it, and only to the extent required. We do not volunteer a yard's open items because another yard asked. If we receive such a request and the law does not require disclosure, we refuse it and, where we are allowed to, we tell the yard.
Regions and providers
Providers we use may store or process information in more than one region. When that happens, we use contracts with those providers that require them to protect the information and to use it only to provide the service. We do not describe those regions as our place of business. A yard that needs the current list of subprocessors can ask support@commonsilo.com. We will send the list that is current at the time of the request.
How long we keep it
We keep a dock record for as long as the yard's subscription is active, and for an export window afterward so the yard can take a final copy. Open items, dispute lines, and signature rows stay on the record during that time. They are not peeled off into a side archive the workshop can edit alone. Billing records are kept for the period accounting rules that apply to the subscription require. Server logs are kept for a shorter operational period and are then deleted or reduced to counts that do not name a ship.
Yard-desk email is kept long enough to finish the correspondence and to show what we replied. Role applications are kept long enough to decide whether to continue the conversation, and then deleted if we are not proceeding, unless the sender asks us to keep a note of the refusal.
When a yard closes the subscription, we provide a final export of dock records still on the ledger. After the export window we delete the records or irreversibly remove the names and vessel details from them, except where a billing record must be kept. A deleted record cannot be restored from the product. A yard that needs the history should export it before the window ends.
Security
Access to a dock record requires an authenticated account. Actions that change a window, add an open item, or sign a row are written to the timeline with the account that performed them. We use encryption in transit between the planner's browser and the service. Backups are restricted to the operators and providers that store them. No method of storage is perfect. A yard that believes a record was changed by the wrong person should write to support@commonsilo.com and name the record identifier. We will say what the timeline shows.
We will not send a password by email. A reset is a new credential issued after we confirm the request comes from the address on the account, as the login page describes.
Your rights
Depending on applicable law, a person whose name appears on a dock record or on an account may ask us to confirm whether we hold information about them, to provide a copy, to correct a name or role that is wrong, to delete an account, to object to a use that applicable law allows them to object to, or to ask us to limit a use while a dispute about the information is unresolved.
A dock record is the yard's operational record of a ship. Correcting or deleting a name on a historical signature row can erase the history the other signers rely on. Where the yard must keep that history, we may limit the change to future displays of the account and leave the signed row intact, and we will explain that limit. The unsigned or signed standing of flood-up will not be rewritten merely because a name on an older row is being corrected.
Requests go to support@commonsilo.com. We may need to confirm that the requester is the person named, or that the requester speaks for the yard that owns the record. We will respond within the time applicable law sets. If we refuse a request, we will say why, including where the reason is the integrity of a signed hour.
Children
The service is for shipyard staff planning dock windows. It is not directed at children, and we do not knowingly open planner accounts for children. If you believe a child's information was placed on a signature row by mistake, write to support@commonsilo.com and name the record.
Changes to this policy
We may update this policy when the product changes, for example if a new export is added or the record-count rule changes. The date at the top will show the first day of the month in which we publish the change. If a change alters what we count toward the subscription, we will also describe it in the terms and tell current yards from support@commonsilo.com before the change applies to a new month. Continued use of the subscription after the effective date is the yard's acceptance of the update, except where applicable law requires a different form of notice or consent.
How to reach us
Privacy questions, copy requests, correction requests, and complaints go only to support@commonsilo.com. Please name the yard and, if you have it, the dock record identifier. You may also start from the yard desk on the main page. That form reaches the same address. There is no second mailbox.