Agency said: 'the account is ours, you have read-only access'. But we paid for it, we should be able to talk. What happens to the data when the contract ends?
What are our legal rights?
Agency said: 'the account is ours, you have read-only access'. But we paid for it, we should be able to talk. What happens to the data when the contract ends?
What are our legal rights?
If the Google Ads account was opened in the client's name, the client owns it. If it was opened in the agency's name, the agency controls it. Legal status: it must be written in the contract.
Typical problem: agency opens the account and gives the client 'read-only' access. When the contract ends, the client can't access the data. Solution: make a written request, the agency has to hand it over (data ownership).
Doki · Infrastructure migration · 2023
same thing happened to me then i told the agency: 'I need to transfer the data to the new agency'. anyway the agency said 'it stays with this agency'. i consulted a lawyer they confirmed in writing that the data is yours. they gave it up.
Access Control Models: - Client account: You open it, give agency access (owner) - Agency account: Agency opens it, you get read-only (risk) - Transfer: Right to transfer data to new agency Best: client opens it, gives agency 'Admin' access (you control)
Check + protect: 1) Is there a 'data ownership' clause in the contract? 2) If not, email the agency (request data handover). 3) If no reply, lawyer. 4) In the new agency, you open the account, give agency access (full control).
Doki · Corporate website · 2024
If I understood correctly, you're saying: Access credentials should be opened in the company's name not personal accounts.
Good luck with that.
Doki · Vulnerability scanning · 2024
You're right. The real issue isn't the number, but what it's based on.
Everyone rushing into access details not handed over gets stuck at the same point. If you have questions, write them; I'll answer as best I can.
Let me summarize the topic, since several different answers were given. In legacy systems, the most expensive thing is unknown dependencies.
Good luck with that.
Let me summarize what's been said so far. Processes without records never improve, because you don't know what to fix.
If you have questions, write them; I'll answer as best I can.
Let me write how it's done in practice. Mistakes made on the access details not handed over side are usually reversible but expensive.
That's all, sorry if I went on too long.
I feel the same way. If scope grows, either time or budget must grow. tbh there is no third option.
I didn't know that. When making decisions, write down the worst-case scenario too, not just the best.
Proven by experience.
The discussion got scattered, let me summarize. btw when making decisions write down the worst-case scenario too, not just the best.
Proven by experience.
i completely agree and if it's your first time start small; scaling comes later.
if scope grows, either time or budget must grow then honestly there is no third option.
Let me share what happened to me; it might be useful. Mistakes made on the access details not handed over side are usually reversible but expensive.
The cheapest quote is usually the least thought-out one.